public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Bodo Eggert <7eggert@gmx.de>
Cc: Andi Kleen <andi@firstfloor.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Mikulas Patocka <mpatocka@redhat.com>,
	linux-kernel@vger.kernel.org, xfs@oss.sgi.com,
	Alasdair G Kergon <agk@redhat.com>,
	Andi Kleen <andi-suse@firstfloor.org>,
	Milan Broz <mbroz@redhat.com>
Subject: Re: Device loses barrier support (was: Fixed patch for simple barriers.)
Date: Fri, 5 Dec 2008 19:41:14 +0100	[thread overview]
Message-ID: <20081205184114.GE6703@one.firstfloor.org> (raw)
In-Reply-To: <E1L8fIY-0001ui-DV@be1.7eggert.dyndns.org>

On Fri, Dec 05, 2008 at 07:21:06PM +0100, Bodo Eggert wrote:
> Andi Kleen <andi@firstfloor.org> wrote:
> 
> >> Not when the fundamental design of the code is broken and trashes
> >> performance.
> > 
> > Sorry but that's just not correct. There's nothing in late failing
> > barriers that "trashes performance". The file system writers have 
> > to be careful to handle it, but at least the current ones all do.
> 
> So let's keep requiring the "trashes performance" hacks, because they're

Again there's nothing about the code that handles this that 
"trashes performance". 

Mickulas was just ranting that the current file systems don't use
barriers in the way he thinks they ought to be used, but that
is completely orthogonal to the problem if barriers may fail
late or not.

In Mickulas imaginary barrier world it would be slightly more 
complicated to handle it, but far from impossible. And again
if there it wouldn't affect performance. In the real world
Linux barrier world handling late failing barriers in the fs
is also very easy currently.

-Andi


  reply	other threads:[~2008-12-05 18:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bFnGM-7mA-5@gated-at.bofh.it>
     [not found] ` <bFpyX-1jh-15@gated-at.bofh.it>
     [not found]   ` <bFquY-2x2-5@gated-at.bofh.it>
     [not found]     ` <bFsnc-51o-37@gated-at.bofh.it>
     [not found]       ` <bFuyC-7Zt-11@gated-at.bofh.it>
     [not found]         ` <bFvuI-L8-29@gated-at.bofh.it>
     [not found]           ` <bFwTJ-2oc-13@gated-at.bofh.it>
     [not found]             ` <bFxwq-3g7-1@gated-at.bofh.it>
     [not found]               ` <bFxGa-3pz-1@gated-at.bofh.it>
     [not found]                 ` <bFHvW-7up-5@gated-at.bofh.it>
     [not found]                   ` <bFHPd-84I-13@gated-at.bofh.it>
2008-12-05 18:21                     ` Device loses barrier support (was: Fixed patch for simple barriers.) Bodo Eggert
2008-12-05 18:41                       ` Andi Kleen [this message]
     [not found] <Pine.LNX.4.64.0812040009340.15169@hs20-bc2-1.build.redhat.com>
     [not found] ` <20081204100050.GN6703@one.firstfloor.org>
2008-12-04 14:00   ` Mikulas Patocka
2008-12-04 14:20     ` Andi Kleen
2008-12-04 14:17       ` Mikulas Patocka
2008-12-04 14:58         ` Andi Kleen
2008-12-04 16:45           ` Mikulas Patocka
2008-12-04 17:48             ` Andi Kleen
2008-12-04 17:53               ` Christoph Hellwig
2008-12-04 19:37               ` Mikulas Patocka
2008-12-04 22:15                 ` Andi Kleen
2008-12-04 23:08                   ` Mikulas Patocka
2008-12-05  0:48                     ` Andi Kleen
2008-12-05  1:16                       ` Mikulas Patocka
2008-12-05  1:37                         ` Andi Kleen
2008-12-05  2:21                           ` Mikulas Patocka
2008-12-05  3:09                             ` Andi Kleen
2008-12-05 11:52                           ` Alan Cox
2008-12-05 12:29                             ` Andi Kleen
2008-12-07  4:17             ` Dave Chinner

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=20081205184114.GE6703@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=7eggert@gmx.de \
    --cc=agk@redhat.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andi-suse@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbroz@redhat.com \
    --cc=mpatocka@redhat.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