From: Andrew Morton <akpm@zip.com.au>
To: Roberto Nibali <ratz@drugphish.ch>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Question about the ide related ioctl's BLK* in 2.5.7-pre1 kernel
Date: Thu, 14 Mar 2002 00:13:17 -0800 [thread overview]
Message-ID: <3C905B9D.A1E3ACF6@zip.com.au> (raw)
In-Reply-To: <3C9007F5.1000003@drugphish.ch> <3C900A11.55BA4B32@zip.com.au> <3C905894.90407@drugphish.ch>
Roberto Nibali wrote:
>
> > They got collaterally damaged in the IDE "cleanup". The patch at
> > http://www.zip.com.au/~akpm/linux/patches/2.5/2.5.6/dallocbase-10-readahead.patch
> > resurrects them.
>
> Oh, I see. I've missed that patch of yours. I certainly enjoyed (maybe
> much to your grief) the comments in the code :).
hmm. I'd better go back and check them then ;)
> Is GFP_READAHEAD still a wish or did you drop that idea?
Dropped. Bad idea. If we have to do I/O to gather the readahead pages
then so be it. That I/O will cluster well, as will the subsequent readahead,
which is better than giving up on the readahead.
> AFAICS you only
> addressed the i386 arch with that patch, do you want the specific arch
> maintainers to clean up their part when your patch is finished?
? There's nothing arch-specific in any of this...
-
next prev parent reply other threads:[~2002-03-14 8:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-14 2:16 Question about the ide related ioctl's BLK* in 2.5.7-pre1 kernel Roberto Nibali
2002-03-14 2:25 ` Andrew Morton
2002-03-14 8:00 ` Roberto Nibali
2002-03-14 8:13 ` Andrew Morton [this message]
2002-03-14 12:04 ` Martin Dalecki
2002-03-14 20:04 ` Roberto Nibali
2002-03-18 13:28 ` Martin Dalecki
2002-03-18 13:34 ` Jens Axboe
2002-03-18 13:43 ` Martin Dalecki
2002-03-18 13:51 ` Jens Axboe
2002-03-14 12:12 ` Martin Dalecki
2002-03-14 12:43 ` Jeff Garzik
2002-03-14 12:51 ` Martin Dalecki
2002-03-14 17:38 ` Andrew Morton
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=3C905B9D.A1E3ACF6@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=ratz@drugphish.ch \
/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