Linked by Kroc Camen on Thu 25th Dec 2008 07:50 UTC, submitted by diegocg
Linux Heise Open Source provides an extensive breakdown of the innovations present in the latest release of the Linux kernel, announced by Linus Torvalds. This version adds the first version of Ext4 as a stable filesystem, the much-anticipated GPU memory manager which will be the foundation of a renewed graphic stack, support for Ultra Wide Band (Wireless USB, UWB-IP), memory management scalability and performance improvements, a boot tracer, disk shock protection, the phonet network protocol, support of SSD discard requests, transparent proxy support, high-resolution poll()/select()... full Changelog here
Thread beginning with comment 341905
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[11]: the list is impressive
by abraxas on Tue 30th Dec 2008 16:10 UTC in reply to "RE[10]: the list is impressive"
Member since:

You clearly have no clue. We were talking about microkernels and monolithic kernels. Hybrid kernels are supposed to be an amalgam of those two concepts. The MIT exokernel is neither of those.

I didn't say they are the only two ways of doing things.

Actually you did. "According to me there are only two categories Monolithic or Microkernel."

Wrong! udev has nothing to do with device drivers or privileged code. First understand what udev does before you talk out of your nether regions.

I was pointing out that your examples are completely wrong. You are trying to convey a point but you don't even understand the examples you are using.

What are you talking about? Where did I mention device drivers in connection with udev? Maybe you haven't been around that long to remember devfs. Devfs was the precursor to udev and it was inside the kernel. The point I was trying to make is that when feasible Linux has moved things out of the kernel.

Therefore FUSE is a bad example because all of it is not in user space. It is a good abstraction but it doesn't make the OS, FUSE is running on any more of a microkernel. The reason being a kernel mode driver is need to make it work.

I never said Linux was a microkernel or was trying to be a microkernel. I just said that concepts from microkernels have entered into other kernels like Linux. The main concept behind microkernels is running as little code in kernelspace as possible. Linux is pushing code out to userspace when it is feasible. Microkernels have done it the other way around and starting pulling things into kernelspace when performance suffers dramatically in userspace.

One word, QNX. You really need to pay attention. QNX beats the pants off linux in scaling down, RT and latency. Got any more ignorance to spread?

It depends on architecture. Context switching on x86 is expensive. QNX and other microkernels don't perform well on x86.

Reply Parent Score: 2