Ingo Molnar released a new patchset titled the 'Modular Scheduler Core and Completely Fair Scheduler'. He explained, "this project is a complete rewrite of the Linux task scheduler. My goal is to address various feature requests and to fix deficiencies in the vanilla scheduler that were suggested/found in the past few years, both for desktop scheduling and for server scheduling workloads."
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2006-03-14
Member since:2005-12-31
> Since there's no longer any distinction between stable and unstable,
> you really never know what you're going to get.
Here's a hint for you: It's the *KERNEL*. It is not meant to be a finished product. You can start worrying about kernel development when you have your own distro.
Member since:2005-07-24
Use your vendor provided kernel.
It's gone through more testing. Expecting the final QA to be done by the kernel devs is a layering violation.
Final QA is a responsibility that rests squarely on the vendors' shoulders. The developers excel at developing. Let them each do their jobs.
If the distributor does not fulfill their responsibility, then find another.
The landscape has changed, and I perceive that there are many who are unwilling to adapt to this new world in which the kernel developers are not responsible for final QA.
Get a kernel off the street, and the risk is entirely yours.
This does not mean that the distributors are not also responsible for feeding their patches back to LKML. And it does not absolve the kernel devs from the responsibility of taking those patches seriously.
Welcome to the year 2.6.x. :-)
Edited 2007-04-23 23:13
Member since:2006-01-02
No other project has this sort of nonsense. If KDE has a bug, then it is KDE's job to fix it, not Ubuntu's. It's great that distros try to fix some bugs, but this is more because they really need a polish product and don't have time to wait around for upstream to fix everything. That the kernel devs want to push everything off onto the distros is just laziness and arrogance. It's not a reasonable development model. For one, it's going to lead to splintering as each distro has it's own patchset and you are FORCED to use a distro's kernel since the vanilla kernels are unstable. This is not the optimal situation. If KDE or GNOME or Vi or any other project took this approach, people would be screaming about it. For some reason, when the kernel folks do stuff, everyone assumes that because it comes out of Linus's mouth, it's perfectly reasonable.
I, for one, am tired of the kernel dev's arrogance. It's producing a kernel that's getting less stable with time, even when the distros are maintaining it. There have been no real innovations for a while and the development process is a mess. I fear Linux will start to lose momentum in a few years, and it will be because of problems like this.
The Verge pointed me to a blog post by Leap Motion - which reveals how their Kinect-like motion control works with Windows 8. "From the second you plug in your Leap Motion Controller, you'll be able to browse the web and interact with your computer just by moving your hands and fingers in the air. With Leap Motion technology and Windows, you can do everything that's possible with multi-touch inputs - without actually touching anything. This also means that existing applications in Windows 7 and 8 will respond to your natural hand and finger movements. Soon, we'll show you how Leap Motion will work with Mac OS X." Quite cool.
PocketNow interviews Marc Dillon, and there's an interesting note about why Jolla is keeping the display properties under wraps: "We're leaving some of those details out because we do understand that there are a lot of really big players in the market and they tend to take certain components in the market and dominate them. We created the ability to actually be able to run Sailfish on multiple hardware displays and be able to swap components, so this is part of the demand and supply planning phase. We are committed to this industrial design which is a 4.5-inch display, an 8 megapixel camera on the back and a front-facing camera at the front, and the exact specs of the display we'll provide when we're close to delivery." Something you rarely hear anything about.
"This is my NeXTstation Turbo Color booting the Mac System 7.1 Operating System using a hardware add-on called 'Daydream'. The Daydream has a Mac ROM and a few custom ICs in it and hooked up to the NeXTs DSP port. Turns your NeXT into a full fledged 68k powered Mac." So cool.
"The NetBSD Project is pleased to announce NetBSD 6.1, the first feature update of the NetBSD 6 release branch. It represents a selected subset of fixes deemed important for security or stability reasons, as well as new features and enhancements. Please note that all fixes in the prior security/bugfix updates (NetBSD 6.0.1 and 6.0.2) are also in 6.1."
"At the end of a week in which Electronic Arts confirmed it wasn't developing a thing for the Wii U, one of the software engineers in EA Sports' Canada studio, in a series of since-deleted tweets, disparaged the console as 'crap' and suggested Nintendo should give up on hardware altogether. 'The Wii U is crap. Less powerful than an Xbox 360. Poor online/store. Weird tablet', tweeted Bob Summerwill, listed as a senior software engineer at EA Canada, in a reply to a tweet posting a link about EA's no-Wii U news. 'Nintendo are walking dead at this point'." The Wii U is turning into the 21st century's Virtual Boy."In NixOS, the entire operating system - the kernel, applications, system packages, configuration files, and so on - is built by the Nix package manager from a description in a purely functional build language. The fact that it's purely functional essentially means that building a new configuration cannot overwrite previous configurations. Most of the other features follow from this." Interesting approach. A Linux distribution, sure, but with some very refreshing ideas about system configuration.
Appfour added, among other features, C/C++ support to its new version of AIDE. From Android-IDE, "Now you can write parts of your app or your whole app in C/C++ on your device. AIDE supports the Standard Android NDK toolchain (GCC 4.6 + Bionic, STL, ...). No changes are necessary if you want to build an app developed on a PC with Eclipse. C/C++ development is fully integrated: Build errors appear in the error list and files can easily be navigated to with Go to file. The editor supports C/C++ syntax highlighting."
Ars nails it: "The answer is that Google did announce what amounts to a fairly substantial Android update yesterday. They simply did it without adding to the update fragmentation problems that continue to plague the platform. By focusing on these changes and not the apparently-waiting-in-the-wings update to the core software, Google is showing us one of the ways in which it's trying to fix the update problem."
"It is good for programmers to understand what goes on inside a processor. The CPU is at the heart of our career. What goes on inside the CPU? How long does it take for one instruction to run? What does it mean when a new CPU has a 12-stage pipeline, or 18-stage pipeline, or even a 'deep' 31-stage pipeline? Programs generally treat the CPU as a black box. Instructions go into the box in order, instructions come out of the box in order, and some processing magic happens inside. As a programmer, it is useful to learn what happens inside the box. This is especially true if you will be working on tasks like program optimization. If you don't know what is going on inside the CPU, how can you optimize for it? This article is about what goes on inside the x86 processor's deep pipeline."
"It was the only moment I heard regret slip into Otellini's voice during the several hours of conversations I had with him. 'The lesson I took away from that was, while we like to speak with data around here, so many times in my career I've ended up making decisions with my gut, and I should have followed my gut,' he said. 'My gut told me to say yes.'" The world would've been a much different place - Apple would have been less dependant on Samsung for its chips, which probably would've meant less money for Samsung to develop its Galaxy business.
Member since:
2006-01-02
I am getting more and more concerned with the development model of the Linux kernel and the arrogance and attitude of the developers. You can't trust Linux to be the rock-solid kernel it used to be. You have to hope and pray...and hope that they didn't add any new regressions or bugs in each release. Since there's no longer any distinction between stable and unstable, you really never know what you're going to get.