From: Jens Axboe <axboe@suse.de>
To: Andre Hedrick <andre@linuxdiskcert.org>
Cc: "Axel H. Siebenwirth" <axel@hh59.org>,
Anton Altaparmakov <aia21@cam.ac.uk>,
linux-kernel@vger.kernel.org
Subject: Re: 2.5.3 - (IDE) hda: drive not ready for command errors
Date: Sun, 3 Feb 2002 00:28:21 +0100 [thread overview]
Message-ID: <20020203002821.A29553@suse.de> (raw)
In-Reply-To: <20020202102659.L12156@suse.de> <Pine.LNX.4.10.10202021158010.26613-100000@master.linux-ide.org>
In-Reply-To: <Pine.LNX.4.10.10202021158010.26613-100000@master.linux-ide.org>
On Sat, Feb 02 2002, Andre Hedrick wrote:
>
> Jens,
>
> You and I know Linus will go ballistic over the reintroduction of a
> working copy model using rq scratch pad. We can go with this return to
No I don't think so, I'd be surprised if Linus cared about that at all.
> what we are trying to get away from but we really need a way to stream the
> pointers to the data register cleanly. Otherwise the benefits of the zero
> copy in block go away.
?? Your point is not clear. zero copy what, request struct?! That would
be way below measurable.
--
Jens Axboe
next prev parent reply other threads:[~2002-02-02 23:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-01 14:33 2.5.3 - (IDE) hda: drive not ready for command errors axel
2002-02-01 16:06 ` Anton Altaparmakov
2002-02-01 16:48 ` Axel H. Siebenwirth
2002-02-01 17:52 ` Andreas Dilger
2002-02-02 2:44 ` Anton Altaparmakov
2002-02-02 9:26 ` Jens Axboe
2002-02-02 19:10 ` Axel H. Siebenwirth
2002-02-02 21:48 ` Andre Hedrick
2002-02-02 23:28 ` Jens Axboe [this message]
2002-02-02 23:58 ` Jens Axboe
2002-02-05 15:32 ` Holger Lubitz
2002-02-05 16:09 ` Anton Altaparmakov
2002-02-05 16:57 ` Holger Lubitz
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=20020203002821.A29553@suse.de \
--to=axboe@suse.de \
--cc=aia21@cam.ac.uk \
--cc=andre@linuxdiskcert.org \
--cc=axel@hh59.org \
--cc=linux-kernel@vger.kernel.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