[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070108134147.GB5291@linuxtv.org>
Date: Mon, 8 Jan 2007 14:41:47 +0100
From: Johannes Stezenbach <js@...uxtv.org>
To: Theodore Tso <tytso@....edu>
Cc: Suparna Bhattacharya <suparna@...ibm.com>,
Andrew Morton <akpm@...l.org>, Willy Tarreau <w@....eu>,
Linus Torvalds <torvalds@...l.org>,
"H. Peter Anvin" <hpa@...or.com>, git@...r.kernel.org,
nigel@...el.suspend2.net, "J.H." <warthog9@...nel.org>,
Randy Dunlap <randy.dunlap@...cle.com>,
Pavel Machek <pavel@....cz>,
kernel list <linux-kernel@...r.kernel.org>,
webmaster@...nel.org,
"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: Re: How git affects kernel.org performance
On Mon, Jan 08, 2007 at 07:58:19AM -0500, Theodore Tso wrote:
>
> The fastest and probably most important thing to add is some readahead
> smarts to directories --- both to the htree and non-htree cases. If
> you're using some kind of b-tree structure, such as XFS does for
> directories, preallocation doesn't help you much. Delayed allocation
> can save you if your delayed allocator knows how to structure disk
> blocks so that a btree-traversal is efficient, but I'm guessing the
> biggest reason why we are losing is because we don't have sufficient
> readahead. This also has the advantage that it will help without
> needing to doing a backup/restore to improve layout.
Would e2fsck -D help? What kind of optimization
does it perform?
Thanks,
Johannes
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists