From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com,
Alex Elder <aelder@sgi.com>
Subject: Re: [PATCH 2/2] xfs: kick inode writeback when low on memory
Date: Fri, 15 Apr 2011 04:09:16 -0400 [thread overview]
Message-ID: <20110415080915.GA10619@infradead.org> (raw)
In-Reply-To: <20110414050846.GJ21395@dastard>
On Thu, Apr 14, 2011 at 03:08:46PM +1000, Dave Chinner wrote:
> Unfortunately, we simply can't take the s_umount lock in reclaim
> context. So further hackery is going to be required here - I think
> that writeback_inodes_sb_nr_if_idle() need to use trylocks. if the
> s_umount lock is taken in write mode, then it's pretty certain that
> the sb is busy....
http://thread.gmane.org/gmane.linux.file-systems/48373/focus=48628
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-04-15 8:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 6:19 [PATCH 0/2] xfs: write back inodes during reclaim Dave Chinner
2011-04-07 6:19 ` [PATCH 1/2] bdi: mark the bdi flusher busy when being forked Dave Chinner
2011-04-11 18:34 ` Christoph Hellwig
2011-04-13 19:29 ` Alex Elder
2011-04-07 6:19 ` [PATCH 2/2] xfs: kick inode writeback when low on memory Dave Chinner
2011-04-11 18:36 ` Christoph Hellwig
2011-04-11 21:14 ` Dave Chinner
2011-04-13 20:33 ` Alex Elder
2011-04-14 5:08 ` Dave Chinner
2011-04-15 8:09 ` Christoph Hellwig [this message]
2011-04-15 7:23 ` [PATCH 0/2] xfs: write back inodes during reclaim Yann Dupont
2011-04-15 7:54 ` Dave Chinner
2011-04-15 9:13 ` Yann Dupont
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=20110415080915.GA10619@infradead.org \
--to=hch@infradead.org \
--cc=aelder@sgi.com \
--cc=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=xfs@oss.sgi.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