On Sat, Aug 09, 2008 at 03:23:22AM +0200, Andi Kleen wrote:RAID is the big problem, yeah. In general, though, we are already making an assumption in the elevator code and in filesystem code that block numbers which are numerically closer together are "close" from the perspective of disks. There has been talk about trying to make filesystems smarter about allocating blocks by giving them visibility to the RAID parameters; in theory the elevator algorithm could also be made smarter as well using the same information. I'm really not sure if the complexity is worth it, though.... - Ted --
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 005/196] Chinese: add translation of SubmittingDrivers |
| Andrew Morton | Re: -mm merge plans for 2.6.23 -- sys_fallocate |
| Michael Opdenacker | [PATCH] x86: fix unconditional arch/x86/kernel/pcspeaker.c compiling |
git: | |
| David Miller | Re: [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Andrew Morton | Re: [BUG] New Kernel Bugs |
