public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Neil Brown <neilb@cse.unsw.edu.au>,
	Christoph Hellwig <hch@lst.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: bug in md write barrier support?
Date: Thu, 9 Sep 2004 10:29:22 +0200	[thread overview]
Message-ID: <20040909082922.GN1737@suse.de> (raw)
In-Reply-To: <1094718179.2801.3.camel@laptop.fenrus.com>

On Thu, Sep 09 2004, Arjan van de Ven wrote:
> 
> > Precisely, it's always possible to just drop queueing depth to zero at
> > that point. If I2O really does reorder around the cache flush (this
> > seems broken...),
> 
> why does this seem broken? semantics of "cache flush guarantees that all
> io submitted prior to it hits the spindle" are quite sane imo; no
> guarantee of later submitted IO.. compare the unix "sync" command; same
> level of semantics.

Depends on your angle, I think it breaks the principle of least
surprise.

-- 
Jens Axboe


  reply	other threads:[~2004-09-09  8:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-03 17:24 bug in md write barrier support? Christoph Hellwig
2004-09-04  0:56 ` Neil Brown
2004-09-04  8:21   ` Jens Axboe
2004-09-06  1:36     ` Neil Brown
2004-09-08  9:23       ` Jens Axboe
2004-09-08 13:35         ` Alan Cox
2004-09-08 15:46           ` Jens Axboe
2004-09-08 22:21             ` Alan Cox
2004-09-09  8:06               ` Jens Axboe
2004-09-09  8:22                 ` Arjan van de Ven
2004-09-09  8:29                   ` Jens Axboe [this message]
2004-09-09 12:51                     ` Alan Cox
2004-09-09 14:34                       ` Jens Axboe
2004-09-12 17:13               ` Rogier Wolff

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=20040909082922.GN1737@suse.de \
    --to=axboe@suse.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arjanv@redhat.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    /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