From: Con Kolivas <kernel@kolivas.org>
To: Pekka J Enberg <penberg@cs.helsinki.fi>
Cc: linux-kernel@vger.kernel.org, ck@vds.kolivas.org
Subject: Re: [PATCH] vm - swap_prefetch-15
Date: Fri, 7 Oct 2005 22:33:11 +1000 [thread overview]
Message-ID: <200510072233.12216.kernel@kolivas.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0510071511040.6755@sbz-30.cs.Helsinki.FI>
On Fri, 7 Oct 2005 22:26, Pekka J Enberg wrote:
> On Fri, 7 Oct 2005, Con Kolivas wrote:
> > Makes sense but it is only used in the CONFIG_SWAP_PREFETCH case so it
> > would end up as a static inline in swap.h to avoid ending being #ifdefed
> > in page_alloc.c. Do you think that's preferable to having it in
> > swap_prefetch.c ?
>
> But then you would still have to open up buffered_rmqueue() and
> zone_statistics() to everyone, no?
bah of course.. /me slaps forehead
> How about you implement a new gfp flag
> __GFP_NEVER_RECLAIM similar to __GFP_NORECLAIM instead so you don't have
> to duplicate __page_alloc()?
That will end up being far more intrusive than this version and __alloc_pages
would need more tests that affect every call to __alloc_pages which seems
much more expensive to me than exporting buffered_rmqueue and
zone_statistics, and the modified __alloc_pages will still be a much more
complicated function than prefetch_get_page.
Thanks,
Con
next prev parent reply other threads:[~2005-10-07 12:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-06 14:01 [PATCH] vm - swap_prefetch-15 Con Kolivas
2005-10-06 14:13 ` [PATCH] vm - swap_prefetch-15 docs Con Kolivas
2005-10-07 10:03 ` [PATCH] vm - swap_prefetch-15 Pekka Enberg
2005-10-07 10:54 ` Con Kolivas
2005-10-07 11:31 ` Pekka Enberg
2005-10-07 12:08 ` Con Kolivas
2005-10-07 12:26 ` Pekka J Enberg
2005-10-07 12:33 ` Con Kolivas [this message]
2005-10-07 12:49 ` Pekka J Enberg
2005-10-07 14:44 ` [ck] " Gustavo Barbieri
2005-10-07 18:28 ` Rudo Thomas
2005-10-07 18:40 ` Gustavo Barbieri
2005-10-07 11:46 ` Paolo Ciarrocchi
2005-10-07 12:18 ` Con Kolivas
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=200510072233.12216.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=ck@vds.kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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