From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Dave Chinner <david@fromorbit.com>,
linux-kernel@vger.kernel.org, hch@infradead.org,
lnxninja@linux.vnet.ibm.com, axboe@kernel.dk, pbadari@us.ibm.com,
Yuri L Volobuev <volobuev@us.ibm.com>
Subject: Re: [RFC][PATCH] try not to let dirty inodes fester
Date: Mon, 11 Oct 2010 15:01:30 -0700 [thread overview]
Message-ID: <1286834490.20322.8.camel@nimitz> (raw)
In-Reply-To: <20101005153604.GA25228@lst.de>
Dave, Christoph,
Thanks again for looking at this. It turned out not to be dirty data at
all that was causing this. It was dispose_list() taking extraordinarily
long to complete. There were cases where it was taking 2 or 3 minutes
per batch of ~75 inodes. This was all due to the underlying filesystem
(GPFS) taking a couple of seconds for each clear_inode(). This kept the
kernel from being able to do any slab reclaim effectively.
Sorry for the noise.
-- Dave
prev parent reply other threads:[~2010-10-11 22:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-01 19:14 [RFC][PATCH] try not to let dirty inodes fester Dave Hansen
2010-10-02 11:32 ` Dave Chinner
2010-10-05 15:25 ` Dave Hansen
2010-10-05 15:36 ` Christoph Hellwig
2010-10-11 22:01 ` Dave Hansen [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=1286834490.20322.8.camel@nimitz \
--to=dave@linux.vnet.ibm.com \
--cc=axboe@kernel.dk \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lnxninja@linux.vnet.ibm.com \
--cc=pbadari@us.ibm.com \
--cc=volobuev@us.ibm.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 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.