public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@gmail.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Jens Axboe <jaxboe@fusionio.com>,
	Mike Snitzer <snitzer@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH 1/2] blktrace: treat flush as barrier
Date: Tue, 31 May 2011 19:27:16 +0900	[thread overview]
Message-ID: <1306837636.1464.15.camel@leonhard> (raw)
In-Reply-To: <20110528074449.GB22382@infradead.org>

2011-05-28 (토), 03:44 -0400, Christoph Hellwig:
> On Sat, May 28, 2011 at 11:09:41AM +0900, Namhyung Kim wrote:
> > AFAIK FLUSH always precedes WRITE and then followed by FUA, so how about
> 
> Right now most do because that's how the old barriers worked, but it's
> going to change.  For $NEXT + 1 I have a patch that for will make
> xfs sends FUA without flushes in a lot of cases, and afaik some device
> mapper code already does now.
> 

OK, thanks for the explanation.

Btw, the point was it seems possible that we can use the 'F' for both
FLUSH and FUA if we distinguish them by their (relative) position in the
output. How do you think? Do you still prefer F/U flags?

Thanks.


-- 
Regards,
Namhyung Kim



  reply	other threads:[~2011-05-31 10:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-27 13:11 [PATCH 1/2] blktrace: treat flush as barrier Namhyung Kim
2011-05-27 13:11 ` [PATCH 2/2] block: add REQ_SECURE to REQ_COMMON_MASK Namhyung Kim
2011-05-27 13:12 ` [PATCH 1/2] blktrace: treat flush as barrier Christoph Hellwig
2011-05-27 13:57   ` Mike Snitzer
2011-05-27 15:13     ` Namhyung Kim
2011-05-27 20:17       ` Jens Axboe
2011-05-27 20:27         ` Christoph Hellwig
2011-05-28  2:09           ` Namhyung Kim
2011-05-28  7:44             ` Christoph Hellwig
2011-05-31 10:27               ` Namhyung Kim [this message]
2011-05-31 10:37             ` Jens Axboe

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=1306837636.1464.15.camel@leonhard \
    --to=namhyung@gmail.com \
    --cc=hch@infradead.org \
    --cc=jaxboe@fusionio.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=snitzer@redhat.com \
    --cc=tj@kernel.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