From: Jens Axboe <axboe@suse.de>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alexander Viro <viro@math.psu.edu>,
"David S. Miller" <davem@redhat.com>,
Andrea Arcangeli <andrea@suse.de>, Alan Cox <alan@redhat.com>,
David Woodhouse <dwmw2@redhat.com>,
linux-scsi@vger.kernel.org, Andrew Morton <andrewm@uow.edu.au>
Subject: Re: 2.4.7-pre9..
Date: Fri, 20 Jul 2001 10:26:14 +0200 [thread overview]
Message-ID: <20010720102614.A13354@suse.de> (raw)
In-Reply-To: <20010720092202.A9525@suse.de> <Pine.LNX.4.31.0107200111280.718-100000@p4.transmeta.com>
In-Reply-To: <Pine.LNX.4.31.0107200111280.718-100000@p4.transmeta.com>
On Fri, Jul 20 2001, Linus Torvalds wrote:
>
>
> On Fri, 20 Jul 2001, Jens Axboe wrote:
> >
> > Attached are two patches -- one that should fix DAC960 for this new
> > completion scheme, and one that corrects the corrected comment in
> > blkdev.h :-)
>
> No, the correction of the correction is worse.
?
> The paging stuff doesn't use any of this. The paging stuff use the page
> cache lock bit, and always has.
Paging still hits a request, I assumed that's what the (really really)
old comment meant to say.
> The only thing that uses request completion checking are special commands,
> like the initial SCSI spin-up etc (scsi_init_one()).
Sure, and IDE ide_wait etc.
--
Jens Axboe
next prev parent reply other threads:[~2001-07-20 8:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-20 5:17 2.4.7-pre9 Linus Torvalds
2001-07-20 7:22 ` 2.4.7-pre9 Jens Axboe
2001-07-20 8:15 ` 2.4.7-pre9 Linus Torvalds
2001-07-20 8:26 ` Jens Axboe [this message]
2001-07-20 16:42 ` 2.4.7-pre9 Linus Torvalds
2001-07-20 18:57 ` 2.4.7-pre9 Jens Axboe
2001-07-20 10:23 ` 2.4.7-pre9 David Woodhouse
2001-07-23 12:56 ` 2.4.7-pre9 Pavel Machek
2001-07-27 16:18 ` 2.4.7-pre9 Matthew Dharm
2001-07-27 17:46 ` 2.4.7-pre9 Linus Torvalds
2001-07-27 19:47 ` 2.4.7-pre9 Matthew Dharm
2001-07-27 21:00 ` 2.4.7-pre9 Linus Torvalds
2001-07-28 3:53 ` 2.4.7-pre9 David Woodhouse
2001-07-27 19:55 ` 2.4.7-pre9 Matthew Dharm
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=20010720102614.A13354@suse.de \
--to=axboe@suse.de \
--cc=alan@redhat.com \
--cc=andrea@suse.de \
--cc=andrewm@uow.edu.au \
--cc=davem@redhat.com \
--cc=dwmw2@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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