All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Mel Gorman <mel@csn.ul.ie>
Cc: akpm@osdl.org, jschopp@austin.ibm.com, mel@csn.ul.ie,
	kravetz@us.ibm.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, lhms-devel@lists.sourceforge.net
Subject: Re: [PATCH 0/8] Fragmentation Avoidance V17
Date: Sat, 15 Oct 2005 19:52:13 -0700	[thread overview]
Message-ID: <20051015195213.44e0dabb.pj@sgi.com> (raw)
In-Reply-To: <20051011151221.16178.67130.sendpatchset@skynet.csn.ul.ie>

Mel wrote:
> +#define __GFP_USER       0x80000u  /* User and other easily reclaimed pages */
> +#define __GFP_KERNRCLM   0x100000u /* Kernel page that is reclaimable */

Sorry, but that __GFP_USER name is still sticking in my craw.

I won't try to reopen my quest to get it named __GFP_REALLY_REALLY_EASY_RCLM
or whatever it was, but instead will venture on a new quest.

Can we get the 'RCLM' in there.  Especially since this term appears
naked in such code as:

> -				page = alloc_page(GFP_HIGHUSER);
> +				page = alloc_page(GFP_HIGHUSER|__GFP_USER);

where it is not at all obvious to the reader of this file (fs/exec.c)
that the __GFP_USER term is commenting on the reclaim behaviour of
the page to be allocated.

I'd be happier with:

> +#define __GFP_USERRCLM    0x80000u /* User and other easily reclaimed pages */
> +#define __GFP_KERNRCLM   0x100000u /* Kernel page that is reclaimable */

and:

> -				page = alloc_page(GFP_HIGHUSER);
> +				page = alloc_page(GFP_HIGHUSER|__GFP_USERRCLM);

Also the bold assymetry of these two #defines seems to be without motivation,
one with the 'RCLM', and the other with '    ' four spaces.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401

WARNING: multiple messages have this Message-ID (diff)
From: Paul Jackson <pj@sgi.com>
To: Mel Gorman <mel@csn.ul.ie>
Cc: akpm@osdl.org, jschopp@austin.ibm.com, kravetz@us.ibm.com,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	lhms-devel@lists.sourceforge.net
Subject: Re: [PATCH 0/8] Fragmentation Avoidance V17
Date: Sat, 15 Oct 2005 19:52:13 -0700	[thread overview]
Message-ID: <20051015195213.44e0dabb.pj@sgi.com> (raw)
In-Reply-To: <20051011151221.16178.67130.sendpatchset@skynet.csn.ul.ie>

Mel wrote:
> +#define __GFP_USER       0x80000u  /* User and other easily reclaimed pages */
> +#define __GFP_KERNRCLM   0x100000u /* Kernel page that is reclaimable */

Sorry, but that __GFP_USER name is still sticking in my craw.

I won't try to reopen my quest to get it named __GFP_REALLY_REALLY_EASY_RCLM
or whatever it was, but instead will venture on a new quest.

Can we get the 'RCLM' in there.  Especially since this term appears
naked in such code as:

> -				page = alloc_page(GFP_HIGHUSER);
> +				page = alloc_page(GFP_HIGHUSER|__GFP_USER);

where it is not at all obvious to the reader of this file (fs/exec.c)
that the __GFP_USER term is commenting on the reclaim behaviour of
the page to be allocated.

I'd be happier with:

> +#define __GFP_USERRCLM    0x80000u /* User and other easily reclaimed pages */
> +#define __GFP_KERNRCLM   0x100000u /* Kernel page that is reclaimable */

and:

> -				page = alloc_page(GFP_HIGHUSER);
> +				page = alloc_page(GFP_HIGHUSER|__GFP_USERRCLM);

Also the bold assymetry of these two #defines seems to be without motivation,
one with the 'RCLM', and the other with '    ' four spaces.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401

--
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>

  parent reply	other threads:[~2005-10-16  2:52 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-11 15:12 [PATCH 0/8] Fragmentation Avoidance V17 Mel Gorman
2005-10-11 15:12 ` Mel Gorman
2005-10-11 15:12 ` [PATCH 1/8] Fragmentation Avoidance V17: 001_antidefrag_flags Mel Gorman
2005-10-11 15:12   ` Mel Gorman
2005-10-11 15:12 ` [PATCH 2/8] Fragmentation Avoidance V17: 002_usemap Mel Gorman
2005-10-11 15:12   ` Mel Gorman
2005-10-13 13:56   ` Dave Hansen
2005-10-13 13:56     ` Dave Hansen
2005-10-13 14:10     ` Mel Gorman
2005-10-13 14:10       ` Mel Gorman
2005-10-13 14:18       ` Dave Hansen
2005-10-13 14:18         ` Dave Hansen
2005-10-13 14:35         ` Mel Gorman
2005-10-13 14:35           ` Mel Gorman
2005-10-16 20:44         ` Mel Gorman
2005-10-16 20:44           ` Mel Gorman
2005-10-13 16:33       ` Joel Schopp
2005-10-13 16:33         ` Joel Schopp
2005-10-11 15:12 ` [PATCH 3/8] Fragmentation Avoidance V17: 003_fragcore Mel Gorman
2005-10-11 15:12   ` Mel Gorman
2005-10-11 15:12 ` [PATCH 4/8] Fragmentation Avoidance V17: 004_markfree Mel Gorman
2005-10-11 15:12   ` Mel Gorman
2005-10-11 15:12 ` [PATCH 5/8] Fragmentation Avoidance V17: 005_fallback Mel Gorman
2005-10-11 15:12   ` Mel Gorman
2005-10-12 16:43   ` mike kravetz
2005-10-12 16:43     ` mike kravetz
2005-10-12 17:21     ` Mel Gorman
2005-10-12 17:21       ` Mel Gorman
2005-10-12 17:29       ` [Lhms-devel] " Joel Schopp
2005-10-12 17:29         ` Joel Schopp
2005-10-14  5:12         ` Dave Hansen
2005-10-14  5:12           ` Dave Hansen
2005-10-11 15:12 ` [PATCH 6/8] Fragmentation Avoidance V17: 006_largealloc_tryharder Mel Gorman
2005-10-11 15:12   ` Mel Gorman
2005-10-13 19:07   ` Joel Schopp
2005-10-13 19:07     ` Joel Schopp
2005-10-14  5:36     ` Dave Hansen
2005-10-14  5:36       ` Dave Hansen
2005-10-11 15:12 ` [PATCH 7/8] Fragmentation Avoidance V17: 007_percpu Mel Gorman
2005-10-11 15:12   ` Mel Gorman
2005-10-11 15:13 ` [PATCH 8/8] Fragmentation Avoidance V17: 008_stats Mel Gorman
2005-10-11 15:13   ` Mel Gorman
2005-10-12 11:57   ` [Lhms-devel] " Dave Hansen
2005-10-12 11:57     ` Dave Hansen
2005-10-12 12:19     ` Mel Gorman
2005-10-12 12:19       ` Mel Gorman
2005-10-16  2:52 ` Paul Jackson [this message]
2005-10-16  2:52   ` [PATCH 0/8] Fragmentation Avoidance V17 Paul Jackson
2005-10-16 11:59   ` Mel Gorman
2005-10-16 11:59     ` Mel Gorman
2005-10-16 17:53     ` Paul Jackson
2005-10-16 17:53       ` Paul Jackson
2005-10-16 18:03       ` Mel Gorman
2005-10-16 18:03         ` Mel Gorman

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=20051015195213.44e0dabb.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=akpm@osdl.org \
    --cc=jschopp@austin.ibm.com \
    --cc=kravetz@us.ibm.com \
    --cc=lhms-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.