From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <jaxboe@fusionio.com>
Cc: Shaohua Li <shaohua.li@intel.com>,
lkml <linux-kernel@vger.kernel.org>, Tejun Heo <htejun@gmail.com>,
"Shi, Alex" <alex.shi@intel.com>,
"Chen, Tim C" <tim.c.chen@intel.com>
Subject: Re: [RFC]block: add flush request at head
Date: Mon, 18 Apr 2011 05:26:07 -0400 [thread overview]
Message-ID: <20110418092607.GA3837@infradead.org> (raw)
In-Reply-To: <4DABF194.4010603@fusionio.com>
On Mon, Apr 18, 2011 at 10:08:52AM +0200, Jens Axboe wrote:
> Might be worth adding something for this special case, seems like the
> NCQ restrictions will continue to be around forever (or a long time, at
> least).
I heared people are working on adding a queued FLUSH to the standard,
but it's going to take a long time for it to get into real life systems.
What would help now is allowing libata to actually use the FUA bit,
given that every common disk and controller supports it these days.
Shaohua, does adding a
libata.fua = 1
to the kernel command line help your benchmark in any way? It should
if you flushes are mostly from journal writes, but not from fsync
that didn't change any metadata.
next prev parent reply other threads:[~2011-04-18 9:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 7:36 [RFC]block: add flush request at head Shaohua Li
2011-04-18 8:08 ` Jens Axboe
2011-04-18 8:25 ` Shaohua Li
2011-04-22 22:57 ` Tejun Heo
2011-04-25 1:01 ` Shaohua Li
2011-04-25 8:21 ` Tejun Heo
2011-04-26 0:49 ` Shaohua Li
2011-04-26 11:29 ` Tejun Heo
2011-04-28 5:13 ` Shaohua Li
2011-04-18 9:26 ` Christoph Hellwig [this message]
2011-04-19 1:07 ` Shaohua Li
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=20110418092607.GA3837@infradead.org \
--to=hch@infradead.org \
--cc=alex.shi@intel.com \
--cc=htejun@gmail.com \
--cc=jaxboe@fusionio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
--cc=tim.c.chen@intel.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).