From: Arjan van de Ven <arjan@infradead.org>
To: Mel Gorman <mel@csn.ul.ie>
Cc: Daniel J Blueman <daniel.blueman@gmail.com>,
Christoph Lameter <clameter@sgi.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Alexander Beregalov <a.beregalov@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
dgc@sgi.com
Subject: Re: [2.6.26-rc7] shrink_icache from pagefault locking (nee: nfsd hangs for a few sec)...
Date: Sun, 22 Jun 2008 11:21:00 -0700 [thread overview]
Message-ID: <20080622112100.794b1ae1@infradead.org> (raw)
In-Reply-To: <20080622181011.GC625@csn.ul.ie>
On Sun, 22 Jun 2008 19:10:11 +0100
Mel Gorman <mel@csn.ul.ie> wrote:
> On (22/06/08 10:58), Daniel J Blueman didst pronounce:
> > I'm seeing a similar issue [2] to what was recently reported [1] by
> > Alexander, but with another workload involving XFS and memory
> > pressure.
> >
>
> Is NFS involved or is this XFS only? It looks like XFS-only but no
> harm in being sure.
>
> I'm beginning to wonder if this is a problem where a lot of dirty
> inodes are being written back in this path and we stall while that
> happens. I'm still not getting why we are triggering this now and did
> not before 2.6.26-rc1 or why it bisects to the zonelist
> modifications. Diffing the reclaim and allocation paths between
> 2.6.25 and 2.6.26-rc1 has not yielded any candidates for me yet that
> would explain this.
>
this sort of thing can easily be exposed with the latencytop tool...
it will at least tell you WHAT the system is blocking on.
(not so much the why, the tool isn't smart enough to automatically spit
out kernel patches yet)
--
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2008-06-22 18:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6278d2220806220256g674304ectb945c14e7e09fede@mail.gmail.com>
2008-06-22 9:58 ` [2.6.26-rc7] shrink_icache from pagefault locking (nee: nfsd hangs for a few sec) Daniel J Blueman
2008-06-22 18:10 ` Mel Gorman
2008-06-22 18:14 ` Mel Gorman
2008-06-22 18:54 ` Daniel J Blueman
2008-06-22 18:21 ` Arjan van de Ven [this message]
2008-06-22 20:56 ` Daniel J Blueman
2008-06-22 22:29 ` Dave Chinner
2008-06-22 22:19 ` Dave Chinner
2008-06-23 0:24 ` Mel Gorman
2008-06-23 0:53 ` Dave Chinner
2008-06-23 7:22 ` Christoph Hellwig
2008-06-23 18:38 ` Mel Gorman
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=20080622112100.794b1ae1@infradead.org \
--to=arjan@infradead.org \
--cc=a.beregalov@gmail.com \
--cc=clameter@sgi.com \
--cc=daniel.blueman@gmail.com \
--cc=dgc@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox