Well when you benchmark the compile time bfs is usally a bit faster.
Announcement
Collapse
No announcement yet.
Linux 2.6.33-rc1 Kernel Released
Collapse
X
-
Originally posted by Kano View PostWell when you benchmark the compile time bfs is usally a bit faster.
Comment
-
Originally posted by hax0r View Post...Also where is reiser4 . I want to see Linus bitching for reiser4 inclusion on next widow merge like he did with nouveau...
Regarding reiser4. I used to use it. Very efficient and decent fs but since it's not developed anymore (?) and as far as I know it didn't approach the stage to be called stable, I don't think Linus would like to include that 'dead' project in the kernel.Last edited by trapDoor; 18 December 2009, 01:02 PM.
Comment
-
Originally posted by skirst View PostIt seems Con has made his point. I agree (based on my experience), there is no need for BFS in mainline at this point.
@Kano
Well when you benchmark the compile time bfs is usally a bit faster.
Comment
-
Originally posted by hmmm View PostI seem to get 2.6.33-rc1 from ubuntu's mainline kernel failing to boot into gdm ...
Comment
-
Did they fix the eternal low responsiveness when doing IO already?
I'm getting so fed up with it, and there's no kernel maintainer who's addressing this bug.
Binary package hint: linux-source-2.6.22 When compared with 2.6.15 in feisty, heavy disk I/O causes increased iowait times and affects desktop responsiveness in 2.6.22 this appears to be a regression from 2.6.15 where iowait is much lower and desktop responsiveness is unaffected with the same I/O load Easy to reproduce with tracker - index the same set of files with 2.6.15 kernel and 2.6.22 kernel and the difference in desktop responsiveness is massive I have not confirmed if a non-tracke...
Can someone with mainstream hardware (sata; dual-core, 2GB) perform a read test with tiobench 64MB and 32 threads, and still open iotop and use firefox in a usable manner?
Comment
-
All new microcode is going into the /lib/firmware folder for distribution rather than being built directly into the kernel. I believe the latest microcode file (rlc) needs to go into the initrd so that drm can find it at boot.
It is still possible to build the firmware into the kernel yourself (ie on your own system) but I think the overall direction for the kernel is increased use of lib/firmware and initrd.Last edited by bridgman; 18 December 2009, 04:28 PM.Test signature
Comment
Comment