From: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-mm@kvack.org, dgc@sgi.com, npiggin@suse.de
Subject: Re: [RFC] Free up page->private for compound pages
Date: Thu, 05 Apr 2007 10:13:52 -0500 [thread overview]
Message-ID: <1175786037.28125.8.camel@shaggy> (raw)
In-Reply-To: <Pine.LNX.4.64.0704042016490.7885@schroedinger.engr.sgi.com>
On Wed, 2007-04-04 at 20:19 -0700, Christoph Lameter wrote:
> Index: linux-2.6.21-rc5-mm4/include/linux/page-flags.h
> ===================================================================
> --- linux-2.6.21-rc5-mm4.orig/include/linux/page-flags.h 2007-04-03 23:48:34.000000000 -0700
> +++ linux-2.6.21-rc5-mm4/include/linux/page-flags.h 2007-04-04 18:25:47.000000000 -0700
> @@ -91,6 +91,7 @@
> #define PG_booked 20 /* Has blocks reserved on-disk */
>
> #define PG_readahead 21 /* Reminder to do read-ahead */
> +#define PG_tail 22 /* Tail portion of a compound page */
>
> /* PG_owner_priv_1 users should have descriptive aliases */
> #define PG_checked PG_owner_priv_1 /* Used by some filesystems */
> @@ -214,6 +215,10 @@ static inline void SetPageUptodate(struc
> #define __SetPageCompound(page) __set_bit(PG_compound, &(page)->flags)
> #define __ClearPageCompound(page) __clear_bit(PG_compound, &(page)->flags)
>
> +#define PageTail(page) test_bit(PG_tail, &(page)->flags)
> +#define __SetPageTail(page) __set_bit(PG_tail, &(page)->flags)
> +#define __ClearPageTail(page) __clear_bit(PG_tail, &(page)->flags)
> +
> #ifdef CONFIG_SWAP
> #define PageSwapCache(page) test_bit(PG_swapcache, &(page)->flags)
> #define SetPageSwapCache(page) set_bit(PG_swapcache, &(page)->flags)
Wow, I was planning on adding that exact flag for the work I'm doing
with Page Cache Tails:
http://kernel.org/pub/linux/kernel/people/shaggy/OLS-2006/
I'm working on killing the page flag, but I am still using PageTail() to
test for the special-case page. No worry. I'll rename it to something
less ambiguous.
As far as the Page Cache Tail work, I'll try to get some patches out for
review soon.
Shaggy
--
David Kleikamp
IBM Linux Technology Center
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2007-04-05 15:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 3:19 Christoph Lameter
2007-04-05 3:36 ` Nick Piggin
2007-04-05 3:38 ` Christoph Lameter
2007-04-05 3:57 ` Nick Piggin
2007-04-05 4:04 ` Christoph Lameter
2007-04-05 4:25 ` Nick Piggin
2007-04-05 4:34 ` Christoph Lameter
2007-04-05 14:30 ` Hugh Dickins
2007-04-05 18:17 ` Christoph Lameter
2007-04-05 18:40 ` Hugh Dickins
2007-04-05 18:58 ` Christoph Lameter
2007-04-05 19:50 ` Hugh Dickins
2007-04-05 20:07 ` Christoph Lameter
2007-04-05 15:13 ` Dave Kleikamp [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=1175786037.28125.8.camel@shaggy \
--to=shaggy@linux.vnet.ibm.com \
--cc=clameter@sgi.com \
--cc=dgc@sgi.com \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
/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