linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mel Gorman <mel@csn.ul.ie>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-kernel@vger.kernel.org, Nick Piggin <npiggin@suse.de>,
	Rik van Riel <riel@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	apw@shadowen.org, linux-mm@kback.org
Subject: Re: [rfc 01/10] Pageflags: Use an enum for the flags
Date: Mon, 3 Mar 2008 10:09:23 +0000	[thread overview]
Message-ID: <20080303100923.GC19485@csn.ul.ie> (raw)
In-Reply-To: <20080301040620.029724488@sgi.com>

On (29/02/08 20:05), Christoph Lameter didst pronounce:
> Use an enum to ease the maintenance of page flags. This is going to change the
> numbering from 0 to 18.
> 
> Signed-off-by: Christoph Lameter <clameter@sgi.com>
> 
> ---
>  include/linux/page-flags.h |   54 ++++++++++++++++++++-------------------------
>  1 file changed, 24 insertions(+), 30 deletions(-)
> 
> Index: linux-2.6/include/linux/page-flags.h
> ===================================================================
> --- linux-2.6.orig/include/linux/page-flags.h	2008-02-29 14:54:22.000000000 -0800
> +++ linux-2.6/include/linux/page-flags.h	2008-02-29 15:00:00.000000000 -0800
> @@ -67,35 +67,28 @@
>   * FLAGS_RESERVED which defines the width of the fields section
>   * (see linux/mmzone.h).  New flags must _not_ overlap with this area.
>   */
> -#define PG_locked	 	 0	/* Page is locked. Don't touch. */
> -#define PG_error		 1
> -#define PG_referenced		 2
> -#define PG_uptodate		 3
> -
> -#define PG_dirty	 	 4
> -#define PG_lru			 5
> -#define PG_active		 6
> -#define PG_slab			 7	/* slab debug (Suparna wants this) */
> -
> -#define PG_owner_priv_1		 8	/* Owner use. If pagecache, fs may use*/
> -#define PG_arch_1		 9
> -#define PG_reserved		10
> -#define PG_private		11	/* If pagecache, has fs-private data */
> -
> -#define PG_writeback		12	/* Page is under writeback */
> -#define PG_compound		14	/* Part of a compound page */
> -#define PG_swapcache		15	/* Swap page: swp_entry_t in private */
> -
> -#define PG_mappedtodisk		16	/* Has blocks allocated on-disk */
> -#define PG_reclaim		17	/* To be reclaimed asap */
> -#define PG_buddy		19	/* Page is free, on buddy lists */
> -
> -/* PG_readahead is only used for file reads; PG_reclaim is only for writes */
> -#define PG_readahead		PG_reclaim /* Reminder to do async read-ahead */
> -
> -/* PG_owner_priv_1 users should have descriptive aliases */
> -#define PG_checked		PG_owner_priv_1 /* Used by some filesystems */
> -#define PG_pinned		PG_owner_priv_1	/* Xen pinned pagetable */

These two verbose descriptions appear to go missing in the enum below.
It probably is intentional because they are aliases but you can preseve them
being aliases with

PG_checked = PG_owner_priv_1,
PG_pinned = PG_owner_priv_1,

That would keep the comments about flags in one place. I note that you
move the comment to the macro definitions in a later patch but maybe having
comments about some flags in multiple places is not very desirable?

> +enum pageflags {
> +	PG_locked,		/* Page is locked. Don't touch. */
> +	PG_error,
> +	PG_referenced,
> +	PG_uptodate,
> +	PG_dirty,
> +	PG_lru,
> +	PG_active,
> +	PG_slab,
> +	PG_owner_priv_1,	/* Owner use. If pagecache, fs may use*/
> +	PG_arch_1,
> +	PG_reserved,
> +	PG_private,		/* If pagecache, has fs-private data */
> +	PG_writeback,		/* Page is under writeback */
> +	PG_compound,		/* A compound page */
> +	PG_swapcache,		/* Swap page: swp_entry_t in private */
> +	PG_mappedtodisk,	/* Has blocks allocated on-disk */
> +	PG_reclaim,		/* To be reclaimed asap */
> +	/* PG_readahead is only used for file reads; PG_reclaim is only for writes */
> +	PG_readahead = PG_reclaim, /* Reminder to do async read-ahead */
> +	PG_buddy,		/* Page is free, on buddy lists */
> +	NR_PAGEFLAGS,		/* For verification purposes */
>  
>  #if (BITS_PER_LONG > 32)
>  /*
> @@ -105,8 +98,9 @@
>   * 64 bit  |           FIELDS             | ??????         FLAGS         |
>   *         63                            32                              0
>   */
> -#define PG_uncached		31	/* Page has been mapped as uncached */
> +	PG_uncached = 31,		/* Page has been mapped as uncached */
>  #endif
> +};
>  
>  /*
>   * Manipulation of page state flags
> 
> -- 
> 

-- 
Mel Gorman
Part-time Phd Student                          Linux Technology Center
University of Limerick                         IBM Dublin Software Lab

  reply	other threads:[~2008-03-03 10:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-01  4:05 [rfc 00/10] [RFC] Page flags: Saving some, making handling easier etc Christoph Lameter
2008-03-01  4:05 ` [rfc 01/10] Pageflags: Use an enum for the flags Christoph Lameter
2008-03-03 10:09   ` Mel Gorman [this message]
2008-03-01  4:05 ` [rfc 02/10] Pageflags: Introduce macros to generate page flag functions Christoph Lameter
2008-03-01  4:05 ` [rfc 03/10] Pageflags: Convert to the use of new macros Christoph Lameter
2008-03-03 10:24   ` Mel Gorman
2008-03-03 18:03     ` Christoph Lameter
2008-03-07 11:13       ` Mel Gorman
2008-03-01  4:05 ` [rfc 04/10] Pageflags: Eliminate PG_readahead Christoph Lameter
2008-03-01  4:05 ` [rfc 05/10] Sparsemem: Vmemmap does not need section bits Christoph Lameter
2008-03-01  4:05 ` [rfc 06/10] Kbuild: Create a way to create preprocessor constants from C expressions Christoph Lameter
2008-03-01  4:05 ` [rfc 07/10] Pageflags: Get rid of FLAGS_RESERVED Christoph Lameter
2008-03-01 16:26   ` Rik van Riel
2008-03-03 17:57     ` Christoph Lameter
2008-03-01  4:05 ` [rfc 08/10] Export NR_MAX_ZONES to the preprocessor Christoph Lameter
2008-03-01  4:05 ` [rfc 09/10] Get rid of __ZONE_COUNT Christoph Lameter
2008-03-01  4:05 ` [rfc 10/10] Pageflags land grab Christoph Lameter
2008-03-01 17:21   ` Rik van Riel
2008-03-04  0:04 [rfc 00/10] [Patch] Page flags: Cleanup, reorg and introduce 5 new flags Christoph Lameter
2008-03-04  0:04 ` [rfc 01/10] Pageflags: Use an enum for the flags Christoph Lameter

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=20080303100923.GC19485@csn.ul.ie \
    --to=mel@csn.ul.ie \
    --cc=akpm@linux-foundation.org \
    --cc=apw@shadowen.org \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kback.org \
    --cc=npiggin@suse.de \
    --cc=riel@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).