From: "Gérard Roudier" <groudier@free.fr>
To: Andre Hedrick <andre@linuxdiskcert.org>
Cc: CJ <cj@cjcj.com>, Linux Kernel <linux-kernel@vger.kernel.org>,
Dave Jones <davej@codemonkey.org.uk>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
Dave Jones <davej@suse.de>, Chuck Lever <cel@monkey.org>
Subject: Re: Possible O_DIRECT problems ?
Date: Sun, 30 Dec 2001 12:16:51 +0100 (CET) [thread overview]
Message-ID: <20011230120352.Y780-100000@gerard> (raw)
In-Reply-To: <Pine.LNX.4.10.10112292138250.32522-100000@master.linux-ide.org>
On Sat, 29 Dec 2001, Andre Hedrick wrote:
> On Sat, 29 Dec 2001, CJ wrote:
>
> > Shouldn't O_DIRECT's requirements come from the hardware? If we can
> > ASPI or CAM DMA SCSI devices to odd addresses and lengths, why not
> > O_DIRECT? Do ape drives DMA to user buffers? Are O_DIRECT's
> > current limits gratuitous?
>
> CAM is a very bad thing and that is why the X3 committees split.
There were interesting guide-lines in CAM, notably the topology handling
and the error recovery scheme. But it was another different wheel in a
world where everybody did reinvent its own. It seemed also very DEC
tainted.
Btw, given guys like you in X3 committees, I am not surprised that splits
occur in this place. :-)
Gérard.
PS: Your various email addresses bounce back claiming some ridiculous
text about spammers. Is this still another show of your apparent
existential complex.
prev parent reply other threads:[~2001-12-30 10:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-21 0:08 Possible O_DIRECT problems ? Dave Jones
2001-12-21 0:23 ` Trond Myklebust
2001-12-21 0:39 ` Dave Jones
[not found] ` <w53ellp2out.wl@megaela.fe.dis.titech.ac.jp>
2001-12-21 12:46 ` Trond Myklebust
2001-12-21 16:14 ` Chuck Lever
2001-12-21 16:04 ` Chuck Lever
2001-12-29 15:25 ` Andrea Arcangeli
2001-12-29 18:46 ` CJ
2001-12-30 5:39 ` Andre Hedrick
2001-12-30 11:16 ` Gérard Roudier [this message]
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=20011230120352.Y780-100000@gerard \
--to=groudier@free.fr \
--cc=andre@linuxdiskcert.org \
--cc=cel@monkey.org \
--cc=cj@cjcj.com \
--cc=davej@codemonkey.org.uk \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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