public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: bzolnier@milosz.na.pl
Cc: Alan Cox <alan@redhat.com>,
	torvalds@osdl.org, linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: PATCH: fix the barrier IDE detection logic
Date: Fri, 3 Sep 2004 17:10:53 +0200	[thread overview]
Message-ID: <20040903151053.GB1717@suse.de> (raw)
In-Reply-To: <200409031554.31057.bzolnier@elka.pw.edu.pl>

On Fri, Sep 03 2004, Bartlomiej Zolnierkiewicz wrote:
> 
> On Tuesday 31 August 2004 18:50, Alan Cox wrote:
> > This fixes the logic so we always check for the cache. It also defaults
> > to safer behaviour for the non cache flush case now we have the right bits
> > in the right places. I've also played a bit with timings - the worst case
> > timings I can get for the flush are about 7 seconds (which I'd expect
> > as the engineering worst cases will include retries)
> > 
> > Probably what should happen is that the barrier logic is enabled providing
> > the wcache is disabled. I've not meddled with this as I don't know what
> > the intended semantics and rules are for disabling barrier on a live disk
> > (eg when a user uses hdparm to turn on the write cache). In the current
> > code as with Jens original that cannot occur.
> 
> I think that logic is reversed here, I guess it should be: enable barrier
> if user enables wcache and disable it if user disables wcache.

There's no need for changes, ide_queue_flush_cmd() handles this fine
right now.

-- 
Jens Axboe


  parent reply	other threads:[~2004-09-03 15:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-31 16:50 PATCH: fix the barrier IDE detection logic Alan Cox
2004-09-03 13:54 ` Bartlomiej Zolnierkiewicz
2004-09-03 14:05   ` Alan Cox
2004-09-03 15:10   ` Jens Axboe [this message]
2004-09-03 15:08 ` 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=20040903151053.GB1717@suse.de \
    --to=axboe@suse.de \
    --cc=akpm@osdl.org \
    --cc=alan@redhat.com \
    --cc=bzolnier@milosz.na.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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