mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Robin Holt <holt@sgi.com>
Cc: 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: Mon, 15 Nov 2004 14:57:14 -0800	[thread overview]
Message-ID: <20041115145714.3f757012.akpm@osdl.org> (raw)
In-Reply-To: <20041115195551.GA15380@lnx-holt.americas.sgi.com>

Robin Holt <holt@sgi.com> wrote:
>
> One significant problem we are running into is autofs trying to umount the
> file systems.  This results in the umount grabbing the BKL and inode_lock,
> holding it while it scans through the inode_list and others looking for
> inodes used by this super block and attempting to free them.

You'll need invalidate_inodes-speedup.patch and
break-latency-in-invalidate_list.patch (or an equivalent).

That'll get you most of the way, but the BKL will still be a problem.

Removing lock_kernel() in the umount path is probably a major project so
for now, you can just drop and reacquire it by doing
release_kernel_lock()/reacquire_kernel_lock() around invalidate_inodes().

(You'll need to use that pair rather than unlock_kernel/lock_kernel because
it seems that invalidate_inodes can be called under various depths of
lock_kernel()).



  parent reply	other threads:[~2004-11-15 22:55 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 [this message]
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
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=20041115145714.3f757012.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