From: Jens Axboe <axboe@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, Andre Hedrick <andre@linux-ide.org>
Cc: fverscheure@wanadoo.fr,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: Problem in IDE Disks cache handling in kernel 2.4.XX
Date: Fri, 10 Jan 2003 17:48:34 +0100 [thread overview]
Message-ID: <20030110164834.GM843@suse.de> (raw)
In-Reply-To: <1042207998.28469.98.camel@irongate.swansea.linux.org.uk>
On Fri, Jan 10 2003, Alan Cox wrote:
> On Fri, 2003-01-10 at 13:03, Andre Hedrick wrote:
> > Oh, just let the darn thing barf a 0x51/0x04 is fine with me!
> > Just an abort/unsupported command.
>
> Sounds ok to me. We do need a barfsupressor option so we can issue
> commands that may fail without confusing the user (eg multiwrite setup)
>
> ie
> ide_hwif_barfsupress(hwif);
> ide_command....
>
> That's very much true irrespective of the flush thing
In the barrier patches, I just used drive->quiet to supress ide_error()
complaining too much (on cache flushes, too). Whether that's per-drive
of per-hwif entity, dunno...
--
Jens Axboe
next prev parent reply other threads:[~2003-01-10 16:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 9:54 Problem in IDE Disks cache handling in kernel 2.4.XX Francis Verscheure
2003-01-10 10:19 ` John Bradford
2003-01-10 11:37 ` Alan Cox
2003-01-10 11:07 ` Benjamin Herrenschmidt
2003-01-10 11:14 ` Andre Hedrick
2003-01-10 13:35 ` Alan Cox
2003-01-10 13:03 ` Andre Hedrick
2003-01-10 14:13 ` Alan Cox
2003-01-10 16:48 ` Jens Axboe [this message]
2003-01-10 18:12 ` Alan Cox
2003-01-10 18:12 ` PATCH: [2.4.21-pre3] Fix for SMP race condition in IDE code Ross Biro
2003-01-10 19:29 ` Alan Cox
2003-01-10 20:22 ` Andre Hedrick
2003-01-10 18:25 ` Problem in IDE Disks cache handling in kernel 2.4.XX Jens Axboe
2003-01-10 17:23 ` Alan Cox
2003-01-10 17:02 ` John Bradford
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=20030110164834.GM843@suse.de \
--to=axboe@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@linux-ide.org \
--cc=fverscheure@wanadoo.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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