Slashdot Log In
Linux Kernel 2.6.20 Released
Posted by
Zonk
on Sun Feb 04, 2007 05:03 PM
from the enjoy-your-new-penguin dept.
from the enjoy-your-new-penguin dept.
diegocgteleline.es writes "After two months of development, Linux 2.6.20 has been released. This release includes two different virtualization implementations: KVM: full-virtualization capabilities using Intel/AMD virtualization extensions and a paravirtualization implementation usable by different hypervisors. Additionally, 2.6.20 includes PS3 support, a fault injection debugging feature, UDP-lite support, better per-process IO accounting, relative atime, relocatable x86 kernel, some x86 microoptimizations, lockless radix-tree readside, shared pagetables for hugetbl, and many other things. Read the list of changes for more details."
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading... please wait.
so (Score:5, Funny)
Re:so (Score:5, Funny)
Parent
Re:so (Score:4, Funny)
Parent
6*9==42 (Score:5, Insightful)
6*9==42
"What do you get if you multiply six by nine?" Arthur then comments, "I've always said there was something fundamentally wrong with the universe."
(ironically, 6*9 does == 42 in base 13...)
Parent
Re:so (Score:4, Funny)
Parent
Pretty amusing superbowl announcement (Score:5, Funny)
the immediate availability of the most advanced Linux kernel to date,
version 2.6.20.
Before downloading the actual new kernel, most avid kernel hackers have
been involved in a 2-hour pre-kernel-compilation count-down, with some
even spending the preceding week doing typing exercises and reciting PI
to a thousand decimal places.
The half-time entertainment is provided by randomly inserted trivial
syntax errors that nerds are expected to fix at home before completing
the compile, but most people actually seem to mostly enjoy watching the
compile warnings, sponsored by Anheuser-Busch, scroll past.
As ICD head analyst Walter Dickweed put it: "Releasing a new kernel on
Superbowl Sunday means that the important 'pasty white nerd'
constituency finally has something to do while the rest of the country
sits comatose in front of their 65" plasma screens".
Walter was immediately attacked for his racist and insensitive remarks
by Geeks without Borders representative Marilyn vos Savant, who pointed
out that not all of their members are either pasty nor white. "Some of
them even shower!" she added, claiming that the constant stereotyping
hurts nerds' standing in society.
Geeks outside the US were just confused about the whole issue, and were
heard wondering what the big hoopla was all about. Some of the more
culturally aware of them were heard snickering about balls that weren't
even round.
Linus
Re: (Score:2)
Re: (Score:2, Informative)
Too many tlas? (Score:5, Funny)
Re: (Score:2, Informative)
Since I love the PHP and PERL implementations of associate arrays, I guess it's neat to have these data structures implemented directly in the kernel! Sounds like they might be using them as a sort of in-memory data store.
SixD
Re:Too many tlas? (Score:5, Informative)
Lockless means it's doing something without locking everyone else from the data. Sometimes this means optimistic resolution (everyone try, and if it looks like it screwed up, try again!), sometimes it means keeping local read copies, sometimes it means something new and/or crazy. Lockless approaches are used when you have data that lots of threads must share but efficiency concerns or non-blocking requirements force you away from simply using a lock and blocking when someone else is playing with the data.
A radix-tree [wikipedia.org], as opposed to "radix-free", is a data structure used in certain applications, with operations dependent on the length of the key rather than the amount of data stored. In 2.6.20 [kernel.org] (and others), it's used to organize some information about the page cache.
This code is associated with the RCU, which you may recall is part of an SCO lawsuit. If you're interested in any other feature or changes, the kernel newbies site is instrumental!
Parent
Relocatable on x86? (Score:4, Insightful)
What is the purpose of being relocatable on x86? I don't remember reading anything about that so what is the point? Is that already possible on other architectures or is x86 the first (as it often is)? I realize the point of making user programs relocatable, but the kernel? The only thing I can think of is that this either has to do with paravirtualization (to speed it up when the kernel isn't at the base of address space), or for replacing the kernel on a running system (can't remember the name, but the idea would be to load the new kernel, transfer into it, then copy it down to the base of memory as you're executing).
Can any explain this one to me?
Re:Relocatable on x86? (Score:5, Informative)
Parent
Re:Relocatable on x86? (Score:5, Informative)
Parent
Re:Relocatable on x86? (Score:5, Informative)
Relocatable kernel support for x86
This feature (enabled with CONFIG_RELOCATABLE) isn't very noticeable for end-users but it's quite interesting from a kernel POV. Until now, it was a requeriment that a i386 kernel was loaded at a fixed memory address in order to work, loading it in a different place wouldn't work. This feature allows to compile a kernel that can be loaded at different 4K-aligned addresses, but always below 1 GB, with no runtime overhead. Kdump users (a feature introduced in 2.6.13 that it triggers kexec in a kernel crash in order to boot a kernel that has been previously loaded at a 'empty' address, then runs that kernel, saves the memory where the crashed kernel was placed, dumps it in a file and continues booting the system) will benefit from this because until now the "rescue kernel" need to be compiled with different configuration options in order to make it bootable at a different address. With a relocatable kernel, the same kernel can be boot at different addresses.
Parent
Re: (Score:3, Insightful)
Since pointing people to the relevent document is apparently flamebait
No, but being rude and obnoxious can certainly qualify as flamebait. If you don't want to be modded down, learn some civility. And by the way, bitching about moderation is off-topic.
Re: (Score:3, Insightful)
Every time you say "RTFM n00b," God kills a prospective Linux switcher. Cheers.
Re: (Score:3, Insightful)
'Many other things' (Score:5, Funny)
Cropotactical callipygization, hoptic chamferbytes, chrome-plated floydbarbers, brillig/mimsy optimizations and full slithy tove support.
Cache of Changes (readable, not verbose log) (Score:2)
http://64.233.167.104/search?q=cache:DeB7M2cAS8gJ: kernelnewbies.org/Linux_2_6_20+http://kernelnewbie s.org/Linux_2_6_20&hl=en&ct=clnk&cd=1&gl=us&client =firefox-a [64.233.167.104]
OSX vs Vista vs Linux (Score:4, Insightful)
When Microsoft released Vista, they talked about all the pretty colors it has, and the cool music you can listen to.
The latest release of Linux is trumpeting virtualization, hypervisors, microoptimizations, and something about a lockless radix-tree.
Nuff said.
D
Re:OSX vs Vista vs Linux (Score:5, Funny)
Parent
Re:OSX vs Vista vs Linux (Score:5, Funny)
I am on LSD, you insensitive clod! And the colors are very pretty to listen to!
Parent
Re:OSX vs Vista vs Linux (Score:5, Funny)
Clearly, the Linux developers need to take a cue from Windows and put graphics drivers in the kernel, permitting a 3d-accelerated Tux at bootup, along with 64-voice software synthesized music. We're falling behind!
Parent
Re:Colourful linux kernel... (Score:5, Funny)
Parent
Re:OSX vs Vista vs Linux (Score:5, Informative)
Parent
Re: (Score:3, Insightful)
Do you think that might be because "linux" the kernel does not even have a user interface with or without pretty colors nor a music player?
Re: (Score:3, Informative)
Actually, that's a replacement for the Jell-o Tree, which had to be locked all the time to keep those darned kids out of it.
Come on, mod me Informative. I dare you.... 8^)
/. Groupthink? (Score:4, Insightful)
Parent
That's nice... (Score:5, Funny)
Re:That's nice... (Score:5, Funny)
and that is a FEATURE!
Parent
Kernel Newbie's Detailed 2.6.20 list. (Score:5, Informative)
Short overview (for news sites, etc)
2.6.20 makes linux join to the virtualization trends. This release adds two virtualization implementations: A full-virtualization implementation that uses Intel/AMD hardware virtualization capabilities called KVM (http://kvm.sourceforge.net) and a paravirtualization implementation (http://lwn.net/Articles/194543) that can be used by different hypervisors (Rusty's lguest; Xen and Vmware in the future, etc),. But this release also adds initial Sony Playstation 3 support, a fault injection debugging feature (http://lwn.net/Articles/209257), UDP-lite support, better per-process IO accounting, relative atime, support for using swap files for suspend users, relocatable x86 kernel support for kdump users, small microoptimizations in x86 (sleazy FPU, regparm, support for the Processor Data Area, optimizations for the Core 2 platform), a generic HID layer, DEEPNAP power savings for PPC970, lockless radix-tree readside, shared pagetables for hugetbl, ARM support for the AT91 and iop13xx processors, full NAT for nf_conntrack and many other things.
Important things (AKA: ''the cool stuff'')
Sony Playstation 3 support
You may like the Wii or the 360 more, but only the PS3 is gaining official Linux support, written by Sony engineers. Notice that the support at this time is incomplete (apparently enabling it will not boot on a stock PS3) and it doesn't support the devices included like the graphics card, etc. (commit 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12)
Virtualization support through KVM
KVM (project page) adds a driver for Intel's and AMD's hardware virtualization extensions to the x86 architecture (KVM will not work in CPUs without virtualization capabilities). See the Virtualization wiki for more information about virtualization in Linux
The driver adds a character device (/dev/kvm) that exposes the virtualization capabilities to userspace. Using this driver, a process can run a virtual machine (a "guest") in a fully virtualized PC containing its own virtual hard disks, network adapters, and display. Each virtual machine is a process on the host; a virtual cpu is a thread in that process. kill(1), nice(1), top(1) work as expected. In effect, the driver adds a third execution mode to the existing two: we now have kernel mode, user mode, and guest mode. Guest mode has its own address space mapping guest physical memory (which is accessible to user mode by mmap()ing
32 and 64 bits guests are supported (but not x86-64 guests on x86-32 hosts!). For i386 guests and hosts, both pae and non-pae paging modes are supported. SMP hosts and UP guests are supported, SMP guests aren't (support will be added in the future). You also can start multiple virtual machines in a host. Performance currently is non-stellar, it will be improved by a lot with the future inclusion of KVM paravirtualization KVM support.
The Windows install currently bluescreens due to a problem with the virtual APIC, a fix is being worked on and will be added in future releases. A temporary workaround is to use an existing image or install through qemu - Windows 64-bit does not work either (commit)
Paravirtualization support for i386
Paravirtualization is the act of running a guest operating system, under control of a host system, where the guest has been ported to a virtual architecture which is almost like the hardware it is actually running on. This technique allows full guest systems to be run in a relatively efficient manner (continue reading this LWN article for more information). This allows to link different hypervisors (lguest/lhype/rustyvisor implements a hypervisor in 6.000 lines; Xen and Vmware will be probably ported to th
Re: (Score:2)
I have no idea why it jumped out at me like that.
linux-wlan-ng injection (Score:4, Interesting)
Re:linux-wlan-ng injection (Score:5, Funny)
Parent
kvm versus vmware (Score:4, Interesting)
I've looked at a KVM whitepaper and it doesn't look like it's quite stable yet. The paper did however mention that it's usably fast on a current processor. (Given it requires the VT extensions, it's inevitable not to have a current processor!)
Can anyone comment on whether KVM is a reasonable alternative to the VMWare Server product?
Re: (Score:2)
It will be once the userspace management tools (e.g. virt-manager) catch up.
Re:kvm versus vmware (Score:5, Interesting)
Its biggest weakness is speed. VMware have had years of tweaking and finetuning, while kvm is very very new, and slow in certain areas. General desktop is fine, but network speed was painfully bad - for example - when I tried version 10. Plenty of work coming down the pipe, and it looks like it could be a powerful opensource virtualisation tool - in time. Right now, it is a bit fiddly to get running, and not quite ready for a production environment.
For now I'd stick to VMWare or virtualbox, but definitely have another look at KVM in say, 6 months time.
Parent
Re:kvm versus vmware (Score:5, Informative)
VMWare workstation actually does more than VMWare server, which is why it is not free. You can look up the comparison table on the VMWare site, but Workstation is usually more attractive to developers because it has (amongst other things):
- Multiple Snapshots - You can only take and rollback to one snapshot with the Server Product, Workstation allows you to go back to many different points in time.
- Shared folders - Not available with Server. Very handy for accessing the host filesystem when the networking setup of the guest does not allow connectivity to the host (think test LAN or similar)
The above features are "cream" on top of the core of virtualisation. If you just want to run a virtualized host, and things like snapshots or shared folders don't matter to you, use VMWare Server.My understanding is KVM provides the infrastructure for userland programs (such as VMWare, Xen) etc to access hardware virtualization services provided by late model Intel and AMD processors. Asking if KVM is a reasonable alternative to VMWare Server is not really a good way to frame the question - one day VMWare may use KVM for virtualisation. A better questions may be "which user-space virtualisation tool provides the best features for me as a user/developer/admin - Xen, VMWare, WidgetWorks" etc.
Parent
Lockless radix trees (Score:3, Funny)
Re: (Score:3, Funny)
PS3 support (Score:3, Informative)
PS3 support not complete (Score:3, Informative)
Things may have changed but I'm stucking with my hand-patched 2.6.17 with zd1211 support for usb wifi.
I use the PS3 Linux quite a bit as a family-room computer. Sound is limited to 2-channel, but good quality. Video has no acceleration, but is still fast and looks good on our 720p TV. Unfortunately, the built-in WIFI doesn't work with Linux, and the Sony-provided kernel seems to lack any support for USB WIFI.
Re: (Score:2)
No but the feature was a freebie not a manpower waste. Sony had their own coders write the PS3 support (which if you read the changes you will find doesn't actually provide support for the PS3).
Re:Amazing (Score:5, Informative)
The latest ubuntu pre-release has the 2.6.20rc kernel. This will be 2.6.20 final (+patches) in the final "Feisty Fawn" release in a couple of months.
Also, I believe (but I'm not 100% sure) that fedora 7 will ship 2.6.20. Current pre-release (test1) and rawhide have 2.6.19.
Parent
Re: (Score:3, Informative)
Re: (Score:2, Informative)
Re: (Score:2)
Re: (Score:3, Informative)
Re: (Score:3, Informative)
Zombie Processes are not a bad thing. They're not memory leaks.
If you have a lot of zombie processes hanging around it's because of a bug in a program. It's pretty unlikely that it's a kernel bug.