All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kirill Korotaev <kk@sw.ru>
To: Nikita Danilov <Nikita@Namesys.COM>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Invalidate_inodes can be very slow
Date: Mon, 13 Oct 2003 17:08:02 +0400	[thread overview]
Message-ID: <200310131708.02348.kk@sw.ru> (raw)
In-Reply-To: <16266.39568.286607.206395@laputa.namesys.com>

>  > no, testcase is not available :( And it uses functionality
>  > not available in mainstream kernel. But the problem can be hit with
>  > very simple script instead:
>  >
>  > 1. mount N filesystems.
>  > 2. work on them, so that inode cache grows to its maximum
>  > possible size (it was 1,000,000 of inodes in our case).
>  > 3. umount these filesystems.
>  >
>  > During operation #3 node is very slow and it is quite noticable
>  > on ssh console when typing commands.
>
> This can be due to a number of reasons (worst case behavior of
> shrink_dcache_parent() for example). What /proc/profile shows?
I used cycles measuring patch. It showed that > 50% CPU during the test
was spent in invalidate_inodes().

Kirill


      reply	other threads:[~2003-10-13 13:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-13  9:18 [PATCH] Invalidate_inodes can be very slow Kirill Korotaev
2003-10-13  9:53 ` William Lee Irwin III
2003-10-13 10:46   ` Kirill Korotaev
2003-10-13 11:06     ` William Lee Irwin III
2003-10-13 11:08   ` Andrew Morton
2003-10-13 11:19     ` William Lee Irwin III
2003-10-13 11:45       ` Kirill Korotaev
2003-10-13 11:54         ` William Lee Irwin III
2003-10-13 12:02           ` Kirill Korotaev
2003-10-13 12:11             ` William Lee Irwin III
2003-10-13 12:21               ` Kirill Korotaev
2003-10-13 12:29                 ` Nikita Danilov
2003-10-13 13:08                   ` Kirill Korotaev [this message]

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=200310131708.02348.kk@sw.ru \
    --to=kk@sw.ru \
    --cc=Nikita@Namesys.COM \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.