From: Linus Torvalds <torvalds@linux-foundation.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: mel@csn.ul.ie, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, linux-mm@vger.kernel.org
Subject: Re: Major mke2fs slowdown (reproducable, bisected)
Date: Mon, 12 Nov 2007 10:39:15 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.0.9999.0711121034220.30499@woody.linux-foundation.org> (raw)
In-Reply-To: <20071112182526.GC11244@martell.zuzino.mipt.ru>
On Mon, 12 Nov 2007, Alexey Dobriyan wrote:
>
> Cross-compile farm here migrated to .ccache and build dir on separate
> disks and now I have a way to blow up .ccache without waiting half an
> hour for rm(1) to finish. It's called mke2fs(8).
>
> However, in e.g 2.6.24-rc2 mke2fs is amazingly slow if done right after
> several fat cross-compile builds. Normally it takes ~11 seconds to
> finish. After commit 5adc5be7cd1bcef6bb64f5255d2a33f20a3cf5be aka
> "Bias the placement of kernel pages at lower PFNs" it takes several
> minutes. 2.6.24-rc2 without this patch also gives normal mkfs speeds.
> I'm pretty sure bisection wasn't screwed up.
Can you (just to make sure) do a "git revert" of this commit on top of the
current tree, and verify that that makes it all work fine again too? If
so, let's just revert it.
I just want to make sure that there isn't some subtle interaction with
anything else in there.
Linus
next prev parent reply other threads:[~2007-11-12 18:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 18:25 Alexey Dobriyan
2007-11-12 18:39 ` Linus Torvalds [this message]
2007-11-12 21:34 ` Alexey Dobriyan
2007-11-12 22:15 ` Linus Torvalds
2007-11-13 16:25 ` Andi Kleen
2007-11-14 11:25 ` Mel Gorman
2007-11-13 16:54 ` Mel Gorman
2007-11-14 11:17 ` Mel Gorman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.0.9999.0711121034220.30499@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@vger.kernel.org \
--cc=mel@csn.ul.ie \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®