Recent Features
| |||||||||||||
The 2.6.29 kernel is out
Linus has announced the release of the
2.6.29 kernel, code-named "Temporary Tasmanian Devil." For those just
tuning in, some of the most significant features of 2.6.29 include the
Btrfs filesystem (still very much in an experimental mode), the squashfs
filesystem, kernel mode setting for Intel graphics adapters, task credentials, WiMAX support,
the filesystem freeze
feature, and much more; see the KernelNewbies
2.6.29 page for all the details.
(Log in to post comments)
The 2.6.29 kernel is out Posted Mar 24, 2009 11:34 UTC (Tue) by ssam (subscriber, #46587) [Link]
Great to see the 'Ext4 no journal mode'.
I guess this is to guarantee data loss after hard crashes and power outages. POSIX FTW
The 2.6.29 kernel is out Posted Mar 24, 2009 11:40 UTC (Tue) by kragil (subscriber, #34373) [Link]
The patch is from Google (they still use EXT2) because they just reimage a machine when it crashes.
Sometimes you don't need a journal but you want the added speed and features.
The 2.6.29 kernel is out Posted Mar 24, 2009 12:21 UTC (Tue) by epa (subscriber, #39769) [Link]
Yes, obviously if your application requires the data to be stored permanently it should call fsync()!
The 2.6.29 kernel is out Posted Mar 24, 2009 13:04 UTC (Tue) by clugstj (subscriber, #4020) [Link]
Let's not start this again!
The 2.6.29 kernel is out Posted Mar 25, 2009 6:42 UTC (Wed) by bojan (subscriber, #14302) [Link]
But it was so much fun! ;-)
The 2.6.29 kernel is out Posted Mar 24, 2009 20:46 UTC (Tue) by muwlgr (guest, #35359) [Link]
Google do not use fsync. They use triple redundancy for their data and handle single storage node faults as usual in-process working events (i.e. bring the redundancy back to 3, and replace the failed node with a new empty operational one).
The 2.6.29 kernel is out Posted Mar 24, 2009 15:45 UTC (Tue) by nix (subscriber, #2304) [Link]
Journals only protect metadata, not data. Google don't care how long fsck takes (they never run it), but they *do* care about I/O rates. So they don't want to use a journal.
The 2.6.29 kernel is out Posted Mar 24, 2009 18:19 UTC (Tue) by tialaramex (subscriber, #21167) [Link]
The data=journal mode protected data, didn't it?
But yes, some people (and Google are apparently enough people to count) want the best possible FS features minus journalling.
Also fsck is probably /faster/ in ext4 than ext2, so Google would be wise to choose ext4 w/o journalling over ext2 even if they did care about fsck performance. Sparse inode structures iirc were a particularly big fsck win.
The 2.6.29 kernel is out Posted Mar 24, 2009 19:59 UTC (Tue) by cortana (subscriber, #24596) [Link]
Apparantly not. I think you want the 'sync' mount option in this case.
The 2.6.29 kernel is out Posted Mar 24, 2009 20:45 UTC (Tue) by tialaramex (subscriber, #21167) [Link]
Ted's talking about ext4 there, not ext3. Combining delayed allocation with data journalling clearly doesn't make much sense. But point taken.
The 2.6.29 kernel is out Posted Mar 24, 2009 14:02 UTC (Tue) by Tuxie (guest, #47191) [Link]
Btrfs is cool but I'm waiting for it to get Z-RAID equivalent functionality before I'll start playing with it.
The 2.6.29 kernel is out Posted Mar 25, 2009 6:28 UTC (Wed) by thedevil (subscriber, #32913) [Link]
I am confused by the excitement about kernel GPU modesetting.
Wasn't this exactly what the "use framebuffer for modesetting" option in the X server has done for many years now?
I am a very light user of graphics - 2D only, no games, etc. That may partly excuse my ignorance here :)
The 2.6.29 kernel is out Posted Mar 27, 2009 14:59 UTC (Fri) by Spudd86 (guest, #51683) [Link]
It moves responsability for large amounts of graphics hardware state out of X and into the kernel, this lets all kinds of things happen.
- Mode only gets set once as you boot (no flicker when X starts) - Kernel can display panic messages while X is running - X doesn't need to be root anymore
|
|||||||||||||