Linux Kernel 2.6.11 Released 312
Xpilot writes "Linus Torvalds has just announced the availability of the newest Linux kernel release, 2.6.11. The newest addition to Linux that's stirring up some excitement is the inclusion of Infiniband support. You can get it from the usual mirrors at http://kernel.org/mirrors."
To Infiniband (Score:4, Funny)
Inspiration from Red Dwarf: (Score:3, Funny)
Infiniband welcomes careful drivers.
:-D
infiniband..... (Score:4, Funny)
Re:infiniband..... (Score:5, Funny)
Interviewer: "I see. But why not just make 11 louder?"
Nigel: "But it goes to infinity."
Interviewer: "Yeah, but what if you just made 11 as loud as infinity?"
Nigel: "But...it goes to infinity."
Knoppix jumped the gun... (Score:2, Funny)
Re:Knoppix jumped the gun... (Score:5, Funny)
Re:Knoppix jumped the gun... (Score:2, Informative)
infiniband? (Score:4, Insightful)
Umm... I don't know about you... but that description didn't help me much... infinite bandwidth? What is this? How is this? How does linux get past physical hardware limitations that other os's can't?
Re:infiniband? (Score:5, Informative)
Intell talks about Infiniband Architecture [intel.com]
Initially InfiniBand Technology will be used to connect servers with remote storage and networking devices, and other servers. It will also be used inside servers for inter-processor communication (IPC) in parallel clusters. Customers requiring dense server deployments, such as ISPs, will also benefit from the small form factors being proposed. Other benefits include greater performance, lower latency, easier and faster sharing of data, built in security and quality of service, improved usability (the new form factor will be far easier to add/remove/upgrade than today's shared-bus I/O cards).
Additionally, InfiniBand Architecture reduces total cost of ownership by focusing on data center reliability and scalability. The technology addresses reliability by creating multiple redundant paths between nodes (reducing hardware that needs to be purchased). It also moves from the load-and-store-based communications methods used by shared local bus I/O to a more reliable message passing approach.
Scalability needs are addressed in two ways. First, the I/O fabric itself is designed to scale without encountering the latencies that some shared bus I/O architectures experience as workload increases. Second, the physical modularity of InfiniBand Technology will avoid the need for customers to buy excess capacity up-front in anticipation of future growth. Instead, they will be able to buy what they need at the outset and 'pay as they grow' to add capacity without impacting operations or installed systems.
Re:infiniband? (Score:5, Insightful)
Re:infiniband? (Score:5, Funny)
Re:infiniband? (Score:3, Funny)
Re:infiniband? (Score:5, Informative)
Re:infiniband? (Score:2, Funny)
Is that like Tolkien Elv-ish?
Re:infiniband? (Score:5, Informative)
You're welcome.
what it is (Score:5, Interesting)
You can use Infiniband as a LAN, for storage, or maybe for within a box. You could say that Infiniband starts where Hypertransport leaves off.
For the short-haul usage, Infiniband is kind of big in terms of chip real estate. You can't cram it into a corner of a little FPGA like you can with RapidIO. For the long-haul usage, 1 gig or 10 gig Ethernet might be a better choice.
Note that Intel, originally the primary sponsor behind Infiniband, no longer gives a damn. But hey, if you have money to burn...
Re:infiniband? (Score:3, Funny)
ahem.. (Score:3, Funny)
err...actually, google knows all who know all
Re:infiniband? (Score:2, Informative)
Re:infiniband? (Score:5, Insightful)
100Gb/s? Then they're almost there! I'm sure infinity isn't much bigger than that.
Re:infiniband? (Score:5, Funny)
Marketing. They transcend the physically possible on a regular basis. Though you missed the source. "How does [InfiniBand] get past physical hardware limitations that other [hardware] can't?" It is their marketing fluff, Linux merely supports the technology.
Kjella
Re:infiniband? (Score:2, Informative)
Infiniband (define)
Both an I/O architecture and a specification for the transmission of data between processors and I/O devices that has been gradually replacing the PCI bus in high-end servers and PCs. Instead of sending data in parallel, which is what PCI does, InfiniBand sends data in serial and can carry multiple channels of data at the same time in a multiplexing signal. The principles of InfiniBand mirror those of mainframe computer systems that are inherently channel-based s
Re:infiniband? (Score:3, Funny)
Agreed.
They should have called it "SynerBand" as in, "Synergized Bandwidth". Alternatively, eSynerBand-Numa.iFlex2@@@ would have been a good choice.
Re:infiniband:more connections, more bandwidth (Score:2)
It wouldn't be the first time: (Score:5, Funny)
The following packages contain magic:
libmagic1
libmagic1-devel
libmagic1-sta
magicdev
magicpoint
mirrormagic
php-
php-mime_magic
Article text (Score:5, Informative)
The Linux world is bracing for the final release of the new Linux 2.6.11 kernel, which will include a long list of driver updates and patches, with InfiniBand support perhaps being one of most interesting new additions.
Late last night, Linux creator Linus Torvalds issued the fifth release candidate for the 2.6.11 kernel. The first 2.6.11 RC was issued on Jan. 12; the second on Jan 21; the third on Feb. 2; and the fourth on Feb. 12.
In the RC5 posting, Torvalds indicated that it was likely the last RC before the final release.
"Hey, I hoped -- rc4 was the last one, but we had some laptop resource conflicts, various ppc TLB flush issues, some possible stack overflows in networking and a number of other details warranting a quick -- rc5 before the final 2.6.11," Torvalds wrote.
"This time it's really supposed to be a quickie, so people who can, please check it out, and we'll make the real 2.6.11 asap."
The long list of updates in the 2.6.11 kernel includes architecture updates for x86-64, ia64, ppc, arm and mips, as well as updates to ACPI (define), DRI (Direct Rendering Infrastructure, which permits direct access to graphics hardware for X Window System users), ALSA (Advanced Linux Sound Architecture, which provides MIDI and audio functionality to the Linux), SCSI (define) and the XFS high-performance journaling filesystem.
The 2.6.11 kernel will also be significant in that it includes driver support for the InfiniBand (define) interconnect architecture. InfiniBand, which is derived from its underlying concept of "infinite bandwidth," is a switched fabric interconnect technology for high-performance network devices that is common in a number of supercomputer clusters.
The upcoming inclusion of InfiniBand support in the Linux kernel is a major step according to the InfiniBand Trade Association.
"The inclusion of InfiniBand drivers in the upstream Linux kernel is a significant milestone," Ross Schibler, CTO of InfiniBand vendor Topspin Communications, told internetnews.com.
InfiniBand support was available previously in various Linux distributions, but it wasn't part of the mainstream kernel.org Linux.
"This now means that anyone that downloads a kernel will have automatic access to the software," explained Schibler. "It also means that any upcoming distributions (Red Hat, SUSE, etc.) will have the software included on their CDs. Previously SUSE had it on a distribution, but only in the 'unsupported' directory."
Schibler sees the inclusion of InfiniBand as a testament to the maturation of the technology.
"Now that the technology has matured to such a point that Linus has accepted it into the kernel, the way is paved for greater distribution of the code and accelerated deployment of the technology," Schibler said.
The previous Linux kernel.org release, version 2.6.10 was issued on Dec. 24 after two release candidates. Linux distribution began including the 2.6.10 thereafter with Red Hat's Fedora Project being one of the first.
Fedora Core 3 initially shipped with the 2.6.9 kernel and then upgraded to the 2.6.10 kernel on Jan 13. Mandrakelinux's 10.2 Beta 3 also includes the 2.6.10 release. SUSE Linux 9.2 currently includes the 2.6.8 kernel.
Including the most recent kernel into a distribution is not a particularly easy task. The upcoming Debian, code-named Sarge, will only ship with the 2.6.8 kernel. In a release update e-mail, Debian Sarge release manager Andreas Barth related that a meeting was recently held to review the status of which kernel they would include.
"The team leads involved eventually decided to stay with kernel 2.6.8 and 2.4.27, rather than bumping the 2.6 kernel to 2.6.10," Barth wrote. "This decision was made upon review of the known bugs in each of the 2.6 kernel versions; despite some significant bugs in the Debian 2.6.8 kernel tree, these bugs were weighed against the additional delays that a kernel version bump would introduce in t
Re:Article text (Score:2)
Re:Article text (Score:3, Insightful)
That makes for an interesting comment, previously people have been ignoring linux and gunning for windows.
Re:Article text (Score:2)
Windows is merely one of the possible options on a server. Linux and other Unix-likes are others.
Re:Article text (Score:2)
Mac laptops (Score:5, Informative)
(I know, "why would you want to run Linux on a Mac". Don't bother asking).
Re:Mac laptops (Score:2)
Re:Mac laptops (Score:2)
someone tell nvidia! (Score:2, Informative)
Re:someone tell nvidia! (Score:2)
Re:someone tell nvidia! (Score:2, Informative)
Re:someone tell nvidia! (Score:3, Insightful)
Re:someone tell nvidia! (Score:2, Interesting)
Re:someone tell nvidia! (Score:4, Interesting)
Which reminds me, when is Linus going to leave the 2.6x tree alone so we don't have to worry about so much broken shit all the time? Imagine if Windows changed it's kernel a couple times a year and broke the video drivers each time. People would bitch endlessly, but I guess as Linux users, we just have to put up with it.
Re:someone tell nvidia! (Score:2)
I had to do the same thing with Gentoo, but the stable drivers seem to be fixed now.
Re:someone tell nvidia! (Score:3, Insightful)
Re:someone tell nvidia! (Score:3, Interesting)
This is somewhat a Good Thing, and somewhat a Bad Thing. The latter is self explained, but the Good Thing about it is that the kernel developers are free to make not only good code, but gr
Re:someone tell nvidia! (Score:2)
Re:someone tell nvidia! (Score:2, Informative)
Re:someone tell nvidia! (Score:2)
Mirrors not caught up yet (Score:4, Informative)
nVidia drivers don't quite work out of the box (Score:4, Informative)
(yay, I actually got a story submission in...hi mom!)
ck, cko patchsets (Score:2)
If anyone knows how to donate small amounts of money to the developers, please let me know: both ck and cko are on my list of projects to eventually donate to (linked to from my URL).
ACPI suspend? (Score:5, Insightful)
Re:ACPI suspend? (Score:4, Informative)
Re:ACPI suspend? (Score:3, Informative)
Re:ACPI suspend? (Score:2, Informative)
Don't know about 'more laptops' but yes, as long as you compile your own kernel and put all USB, wireless card, agpgart, and related stuff in kernel modules. Unload these modules before suspend and reload them after. Of course, that also means that your USB stuff needs to be unplugged before you suspend. Works like a charm on Debian Sid and Ubuntu "Whory". No swsusp2 necessary for me.
--Thinkpad R40 on Ubuntu Hoary (or Debian Sid depending on the day of the week)
Re:ACPI suspend? (Score:3, Insightful)
Re:ACPI suspend? (Score:2)
Re:ACPI suspend? (Score:3, Informative)
Re:ACPI suspend? (Score:2)
Lotsa good stuff (Score:2, Informative)
Not -so-natural high (Score:4, Funny)
Re:Not -so-natural high (Score:2)
Lies, Danm lies and Changelogs (Score:5, Funny)
Torvalds, you scoundrel you!
Next you'll be telling us the kernel was made by the toothfairy for a lower TCO than windows...
Oh wait..
NVidia Driver patches for 6629 with 2.6.11 (Score:5, Informative)
http://www.nvnews.net/vbulletin/showthread.php?t=
This is the cumulative patch:
http://www.nvnews.net/vbulletin/attachment.php?at
Re:NVidia Driver patches for 6629 with 2.6.11 (Score:2)
Re:NVidia Driver patches for 6629 with 2.6.11 (Score:2, Informative)
A kernel patch for supercomputers ? (Score:5, Funny)
>InfiniBand, which is derived from its underlying concept of "infinite bandwidth," is a switched fabric interconnect technology for high-performance network devices that is common in a number of supercomputer clusters.
So that works only for supercomputer clusters ?.Interestingly, the ChangeLog has some very small number of entries. The one I found most fun was:-
I mean, other wise they would end up as "-1" or "0" (when you assume in code that "0" or "1" for 1 -bit fields). How did a sign-extension in the IDE (must be heavily used) be missed till version 2.6 ??. Typically, this looks like the average release - some bug fixes and a couple of big features which nobody (well almost nobody) would use on their boxes.Re:A kernel patch for supercomputers ? (Score:2)
it'd be fine if they've been using "eq 0" and "ne 0" as tests.
Re:A kernel patch for supercomputers ? (Score:2)
When I joined he'd been working with the company for 2 years and was their senior developer. You can imagine what a state the code was in... I basically deleted the lot and rewrote it (which pissed him off no end but pleased all the other developers).
Re:A kernel patch for supercomputers ? (Score:3, Informative)
Assuming you use the 1-bit fields with "if (field)" or "if (!field)", it doesn't matter if they're signed, except that you'll get a warning (but the desired effect) for "field = 1". Problems come up when you use the value as a larger type, but that's not a good idea for code clarity reasons anyway, when the field semantically stores either
An Introduction to the InfiniBand Architecture (Score:2)
http://www.oreillynet.com/pub/a/network/2002/02
Help? (Score:2)
Re:Help? Wikipedia to the rescue! (Score:5, Informative)
In general, the operating system is the first layer of software loaded into computer memory when it starts up. As the first software layer, all other software that gets loaded after it depends on this software to provide them with various common core services. These common core services include, but are not limited to: disk access, memory management, task scheduling, and user interfacing. Since these basic common services are assumed to be provided by the OS, there is no need to re-implement those same functions over and over again in every other piece of software that you may use. The portion of code that performs these core services is called the "kernel" of the operating system. Operating system kernels had been evolved from libraries that provided the core services into unending programs that control system resources because of the early needs of accounting for computer usage and then protecting those records.
So that is the OS and the kernel. A new kernel version is new drivers and updated system services, which is a good thing. This is not the same as upgrading Win2000 to winXP or changing Linux distros as those involve many many more programs, libraries, & systems as compared (what is collectively known as an Operating System) to a kernel.
Re:New to Linux? (Score:2)
Score thus far (Score:5, Funny)
Info for the masses (Score:5, Informative)
Infiniband is a high-speed, low-latency interconnect used heavily with beowulf clusters (currently). Infiniband, like Myrinet, addressed many of the problems that are inherent with using interconnects like ethernet.
The biggest problem with any TCP/IP based transport, in the world of supercomputing, is latency. The amount of error checking that is involved creates latencies that bring fine-grained (lots of memory reads/writes/swaps) calculations to their knees. As many clusters use MPI (Message Passing Interface) for sharing memory between nodes, a low-latency interconnect was needed to replace ethernet and TCP/IP. People have worked on reducing latencies over ethernet by designing raw transport stacks, relying on the switch and the quality/brevity of the ethernet connections (using short, shielded cables proved useful), to ensure accurate data transport, but none of these methods have proven viable.
Infiniband has also been used as an interconnect for network storage devices as there are obvious advantages to this; eliminating much of that latency makes reads and writes to a device much simpler thus reducing overhead and improving overall throughput.
More information on Infiniband can be found here [sourceforge.net] at the Infiniband sourceforge page. This should give a sufficiently technical overview of what it does without any of the marketing talk.
Don't forget OpenIB (Score:2)
Re:Info for the masses (Score:2)
It's been a couple of years since I looked at IB, but I thougt it used IPv6 addressing (or some close variant thereof).
Side note: when I worked at a Fibre Channel startup, some of our guys left to go work over at TopSpin.
Tracy, Meher, if you're reading this -- Hi!
psmouse.c (Score:3, Informative)
lost synchronisation, throwing [1|2|3] bytes away
Adding psmouse.proto=imps made the problem go away for most usage, but it still occurs under very heavy load, which makes mplaying UT impossible
Re:psmouse.c (Score:3, Interesting)
All in a
Re:psmouse.c (Score:3, Informative)
Input: psmouse - reset mouse before doing intellimouse/explorer probes in case it got confused by earlier probes; switch to streaming code before setting scale and resolution, otherwise some KVMs get confused.
There are a whole load of other relevant-sounding fixes in the input system listed as well; damnit, if only I'd found the full changelog earlier!
Time to... (Score:3, Funny)
Show of hands... (Score:3, Funny)
*rhand* *grouse*
Re:Show of hands... (Score:2)
Until recently, I was running, compiling 2.4.x kernels with no problem; I then moved to FC3, and for the first time, was using 2.6.x kernels, and first time using grub.
2.6.10 builds for me, and everything. I build the kernels, build and install the modules, and since I have SCSI, I run initrd; I add the kernel and initrd.img line to my grub.conf. However, I still get a kernel panic telling me that it can't find the system at boot..
Re:Show of hands... (Score:2)
If so, log in via rescue mode create a initrd directory in / . If not, well, dunno then.
ChangeLog (Score:3, Informative)
Also, does anyone know what the status of inotify support is? I think a lot of people would be glad to see it merged, as apps like Beagle require it and the new Gamin daemon (a FAM replacement) should work much better with it.
Still no PATA Support? (Score:2, Interesting)
This is frustrating. I had purchased an Ultra ATA Hard disk drive (which came bundled with a Serial/Parallel ATA controller), and I had it working fine under SUSE Linux 9.0. What I didn't realize at the time was, Promise made proprietary drivers for SuSE Linux, and no other distro.
I have wanted to switch over to
Re:Still no PATA Support? (Score:2)
So, apparantly, PATA is more of a "generic" term for IDE hard drives than I had realized
Yes, there is a Pro
Re:Still no PATA Support? (Score:3, Insightful)
You got it to work? With which vendor's card?? At this point, I am so frustrated, I'm willing to throw money at the solution and buy a new Serial/Parallel ATA controller, if it is affordable enough ($20-30). My understanding, however, was that libata itself (not just the individual drivers, like sata_promise) had no support yet for the PATA conn
Re:Still no PATA Support? (Score:2, Informative)
thinkpad? (Score:3, Interesting)
then again, X goofs up for me with the bios 'hybernation' feature too. though I think that's independent, as it still "works" - just with screen garbage on resume.
of course, first successful Gentoo instal yesterda (Score:2)
I just compiled the 2.6.10 kernel last night. I mean after several attempts over the past few years I finally got Gentoo installed (previous attempts had dependency clashes which I as a Gentoo newb didn't want to deal with). I must say that the documentation has improved though I still don't understand why the don't provide a few more scripts (hopefully cobining the partitioning, mounting, and chrooting phase --- I always seem to miss a step for forget to mount one of the partitions *GRR*).
I guess I could
Re:SCSI (Score:2)
you seem to have confused Voodoo , with buying supported hardware and installing kernel moduels
Yours sincerly
The president of Cbua
Re:Reiser4 (Score:2)
You pretty much answered your own question. I don't think anybody want extremely experimental kernel patches in the main kernel.
Re:Reiser4 (Score:4, Interesting)
Re:SCSI Permissions (Score:5, Informative)
Perhaps I'm being dense, but why go through the trouble of patching the kernel? Why not just set up sudo? Something like the following would allow anyone in the cdrom group to run 'sudo cdrecord
%cdrom ALL=NOPASSWD:
You could even set up an alias like this: alias cdrecord='sudo cdrecord' so that you don't have to remember the sudo bit.
Call me crazy, but patching your kernel every time just to be able to record CDRs seems silly. I can understand not wanting to be root to use cdrecord, though.
And actually, the more I think about it, why can't you just change the permissions on the devices(s) to be group-writable by some group (e.g. cdrom) and make your users part of that group? I feel like I must be missing something.
I dunno. Seems like there are two very easy solutions to your issue, but maybe I don't understand the scope of the problem.
Re:SCSI Permissions (Score:3, Informative)
ALL ALL=NOPASSWD:/usr/bin/xcdroast,
Re:SCSI Permissions (Score:2, Insightful)
I believe the patches allow trusted(?) applications to lock small amounts of this memory without requiring root.
Something like that, I follow along enough to know what's going on, but don't understand everything to it.
Re:SCSI Permissions (Score:3, Informative)
Hmm... I haven't heard anything about this, but my gut response is bafflement. What's wrong with setuid or sudo? Why reinvent the wheel? (no pun intended)
It sure is! (Score:2)
I want slashcode to have keyword filtering, you could take a quick glance, choose the top 3-4 keywords the (what is to anyone "you", your choice) drivel subthreads are in, the s
Re:great (Score:3, Informative)
Two things have really bothered me, one was the fact that framebuffer console support for ATI Radeon cards was horribly broken in kernel releases that were supposed to be "stable, tested, for production". This went on forever. It started working again in 2.6.8, I think. It should have been flagged as experimental, if it didn't work. Without the framebuffer device,
Re:great (Score:5, Informative)
But the whole CD Writing support treats IDE CD Writers like some kind of odd hardware from the top to the bottom,
because they are
Modern IDE ATAPI CD/DVD writers use the 'SCSI-3 mmc' command set. So basically they are SCSI Writers in IDE disguise. But internally they are not full SCSI devices, as they only support a small subset of all SCSI commands.
As a kernel hacker, what would you do?
1): write a SCSI Emulation layer that makes those IDE ATAPI devices act as full, real SCSI devices (from the software point of view). No redundant code, easier to maintain if done correctly.
2): write a specific IDE ATAPI driver and one specific driver for SCSI devices. Some redundant code, but more 'optimised' for each type of device
Linux has both.
1) was not maintained for quite a while, and obviously was badly written at first, thus nobody wanted to clean it up and it was maked 'deprecated'. But it still offers more features than 2).
OTOH 2) has DMA support which makes it attractive for many people, but is quite new and some app developers are afraid to support it, since the API might still change.
and the developer of the cdrecord client has been totally unprofessional about the whole thing.
Nobody has to love Joerg Schilling, and I often don't like his attitude either. However everybody is entitled to have his/her opinion, and in his case he thinks that everything except the SCSI way sucks (he loves Solaris and FreeBSD because they have good SCSI support). So naturally he despises 2), whereas the rest of the linux developer try to make it the default.
He produces the best CD/DVD writing application for linux, and he knows more that most other people when it comes to CD/DVD writing. And he has a point when he says that you should still use the ide-scsi driver whenever possible, because ide-cd driver is NOT complete and still lacks important features. The problem is that since he is quite a SCSI fanatic many people are not taking him seriously.
Re:great (Score:3, Informative)
USB 'plug and play' (USB hotplug) has been supported and has been working for years. I've never had a problem with USB devices where there's been a program to use them (or a driver, for example USB mass storage).