lkml.org 
[lkml]   [2003]   [Mar]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH] concurrent block allocation for ext2 against 2.5.64
From
Date
>>>>> Andreas Dilger (AD) writes:

AD> Could you make it a pre-requisite to the concurrent-alloc patch?
AD> That would make it a shoo-in to being accepted (cleans up code
AD> nicely).

Andrew already asked to wait until next -mm

AD> The point of having the reserved blocks is to reduce
AD> fragmentation in file allocation. Having per-group reserved
AD> blocks is a good idea, because it keeps the reserved "slack" per
AD> group, and helps file allocations within that group have a bit of
AD> free space in which to grow. If you are reserving all of the
AD> blocks at the end of the filesystem, then the earlier groups will
AD> become 100% allocated prematurely and lose any ability to keep
AD> files there contiguous.

well. looks like I miss something here. I thought reservation is not
allocation policy, but mechanism to protect some user (root, usually)
from fs overflow

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:33    [W:0.049 / U:0.404 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site