All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: clameter@sgi.com, nickpiggin@yahoo.com.au, linux-mm@kvack.org
Subject: Re: Avoid excessive time spend on concurrent slab shrinking
Date: Fri, 31 Mar 2006 16:14:10 -0800	[thread overview]
Message-ID: <20060331161410.733cf360.akpm@osdl.org> (raw)
In-Reply-To: <20060331160032.6e437226.akpm@osdl.org>

Andrew Morton <akpm@osdl.org> wrote:
>
>  A plain old sysrq-T would be great.
>

Really great.

We do potentially-vast gobs of waiting for I/O in
prune_icache->dispose_list->truncate_inode_pages().

But then, why would dispose_list() run truncate_inode_pages()?  Reclaiming
an inode which has no links to it, perhaps - it's been a while since I was
in there <wishes he added more comments last time he understood that stuff>

clear_inode() does wait_on_inode()...

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2006-04-01  0:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-31 22:44 Avoid excessive time spend on concurrent slab shrinking Christoph Lameter
     [not found] ` <20060331150120.21fad488.akpm@osdl.org>
2006-03-31 23:17   ` Christoph Lameter
2006-03-31 23:46     ` Andrew Morton
     [not found]     ` <20060331153235.754deb0c.akpm@osdl.org>
2006-03-31 23:48       ` Christoph Lameter
2006-04-01  0:00         ` Andrew Morton
2006-04-01  0:14           ` Andrew Morton [this message]
2006-04-01  0:22           ` Christoph Lameter
2006-04-01  1:25             ` Andrew Morton
2006-04-01  2:34               ` Nick Piggin
2006-04-01  5:59               ` Nathan Scott
2006-04-01 18:30                 ` David Chinner
2006-04-01 18:49                   ` Christoph Lameter
2006-04-01 18:24             ` David Chinner
2006-03-31 23:45 ` 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=20060331161410.733cf360.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=clameter@sgi.com \
    --cc=linux-mm@kvack.org \
    --cc=nickpiggin@yahoo.com.au \
    /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.