From: Andrew Morton <akpm@osdl.org>
To: Robin Holt <holt@sgi.com>
Cc: holt@sgi.com, linux-kernel@vger.kernel.org, dev@sw.ru,
wli@holomorphy.com, steiner@sgi.com, sandeen@sgi.com
Subject: Re: 21 million inodes is causing severe pauses.
Date: Tue, 16 Nov 2004 17:05:21 -0800 [thread overview]
Message-ID: <20041116170521.52d9bc6b.akpm@osdl.org> (raw)
In-Reply-To: <20041117005400.GA11322@lnx-holt.americas.sgi.com>
Robin Holt <holt@sgi.com> wrote:
>
> > > At this point, I have checked the entire code path and see no reason the
> > > BKL is held for the first call to invalidate_inodes.
> >
> > No, the above change looks fine. And I have no problem merging up
> > invalidate_inodes-speedup.patch, really - it's been in -mm for over a year.
> > I've just been waiting for a decent reason to merge it.
>
> I would strongly encourage merging the three patches we have talked about
> here. I understand you would typically keep my BKL patch in your tree for
> awhile and think that would be just fine. The changes only affect systems
> that have filesystems being unmounted with a large number of inodes.
>
> With the two patches already in your tree, the pauses are greatly reduced
> for the autofs case that originally got me looking.
OK. It's a bit late for 2.6.10 but I was planning on slurping the whole
lot into 2.6.11 anyway.
next prev parent reply other threads:[~2004-11-17 1:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 19:55 Robin Holt
2004-11-15 20:35 ` Norbert van Nobelen
2004-11-15 20:51 ` Robin Holt
2004-11-15 20:57 ` linux-os
2004-11-15 21:31 ` Robin Holt
2004-11-15 22:57 ` Andrew Morton
2004-11-16 16:28 ` Robin Holt
2004-11-16 19:13 ` Andrew Morton
2004-11-16 19:48 ` Robin Holt
2004-11-17 0:33 ` Andrew Morton
2004-11-17 0:54 ` Robin Holt
2004-11-17 1:05 ` Andrew Morton [this message]
2004-11-16 16:32 ` Robin Holt
2004-11-16 19:15 ` Andrew Morton
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=20041116170521.52d9bc6b.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=dev@sw.ru \
--cc=holt@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@sgi.com \
--cc=steiner@sgi.com \
--cc=wli@holomorphy.com \
/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
Powered by JetHome