From: Christoph Hellwig <hch@infradead.org>
To: Shawn Bohrer <sbohrer@rgmadvisors.com>
Cc: "Darrick J. Wong" <djwong@us.ibm.com>,
Christoph Hellwig <hch@infradead.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
xfs@oss.sgi.com
Subject: Re: Stalls during writeback for mmaped I/O on XFS in 3.0
Date: Tue, 20 Sep 2011 12:30:34 -0400 [thread overview]
Message-ID: <20110920163034.GB18914@infradead.org> (raw)
In-Reply-To: <20110916163232.GA2109@BohrerMBP.rgmadvisors.com>
On Fri, Sep 16, 2011 at 11:32:32AM -0500, Shawn Bohrer wrote:
> So for the most part it sounds like this change is needed for DIF/DIX.
> Could we only enable the wait_on_page_writeback() if
> CONFIG_BLK_DEV_INTEGRITY is set? Does it make sense to tie these
> together?
It will also allow for huge efficiency gains on software raid. There
have been some Lustre patches for that.
> The other thread in this case is the [flush-8:0] daemon writing back
> the pages. So in our case you could see the spikes every time it wakes
> up to write back dirty pages. While we can control this to some
> extent with vm.dirty_writeback_centisecs and vm.dirty_expire_centisecs
> it essentially impossible to ensure the writeback doesn't coincide
> with us writing to the page again.
Can you explain how your use case looks in more details? Right now
for example a mlock removes the page from the lru list and thus stops
VM writeback. If such an interface would be useful for you we could
offer an fadvice call that stops writeback entirely, and requires you
to force it when you want it.
next prev parent reply other threads:[~2011-09-20 16:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 14:47 Stalls during writeback for mmaped I/O on XFS in 3.0 Shawn Bohrer
2011-09-15 14:55 ` Christoph Hellwig
2011-09-15 15:47 ` Shawn Bohrer
2011-09-16 0:25 ` Darrick J. Wong
2011-09-16 16:32 ` Shawn Bohrer
2011-09-20 16:30 ` Christoph Hellwig [this message]
2011-09-20 18:42 ` Shawn Bohrer
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=20110920163034.GB18914@infradead.org \
--to=hch@infradead.org \
--cc=djwong@us.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sbohrer@rgmadvisors.com \
--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;
as well as URLs for NNTP newsgroup(s).