linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: "Rohit, Seth" <rohit.seth@intel.com>
Cc: torvalds@osdl.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH]: Cleanup of __alloc_pages
Date: Mon, 7 Nov 2005 17:53:58 -0800	[thread overview]
Message-ID: <20051107175358.62c484a3.akpm@osdl.org> (raw)
In-Reply-To: <20051107174349.A8018@unix-os.sc.intel.com>

"Rohit, Seth" <rohit.seth@intel.com> wrote:
>
> [PATCH]: Clean up of __alloc_pages. Couple of difference from original behavior:
> 	1- remove the initial reclaim logic
> 	2- GFP_HIGH pages are allowed to go little below watermark sooner.
> 	3- Search for free pages unconditionally after direct reclaim.

Would it be possible to break these into three separate patches?  The
cleanup part should be #1.

> +/* get_page_from_freeliest loops through all the possible zones
> + * to find out if it can allocate a page.  can_try_harder can have following
> + * values:
> + * -1 => No need to check for the watermarks.
> + *  0 => Don't go too low down in deeps below the low watermark (GFP_HIGH)
> + *  1 => Go far below the low watermark.  See zone_watermark_ok (RT TASK)
> + *
> + * cpuset check is not performed when the skip_cpuset_chk flag is set.
> + */
> +
> +static struct page *
> +get_page_from_freelist(gfp_t gfp_mask, unsigned int order, struct zone **zones, 
> +			int can_try_harder, int skip_cpuset_chk)
> +{
> +	struct zone *z;
> +	struct page *page = NULL;
> +	int classzone_idx = zone_idx(zones[0]);
> +	int i;
> +
> +	/*
> +	 * Go through the zonelist once, looking for a zone with enough free.
> +	 * See also cpuset_zone_allowed() comment in kernel/cpuset.c.
> +	 */
> +	for (i = 0; (z = zones[i]) != NULL; i++) {
> +		if (!skip_cpuset_chk && (!cpuset_zone_allowed(z, gfp_mask)))

It'd be nice to not have the `skip_cpuset_chk' flag there.  a) it gives
Linus conniptions and b) it's a little extra overhead for !CONFIG_CPUSETS
kernels.

> -	zone_statistics(zonelist, z);
> +	zone_statistics(zonelist, page_zone(page));

Evaluating page_zone() is not completely trivial.  Can we avoid the above?

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

  reply	other threads:[~2005-11-08  1:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-08  1:43 Rohit, Seth
2005-11-08  1:53 ` Andrew Morton [this message]
2005-11-08  2:16   ` Rohit Seth
2005-11-08  2:44     ` Andrew Morton
2005-11-08  3:47     ` Nick Piggin
2005-11-08  5:44       ` Paul Jackson
2005-11-08  6:00         ` Nick Piggin
2005-11-08  6:22           ` Paul Jackson
2005-11-08 18:17           ` Rohit Seth
2005-11-08 19:54             ` Paul Jackson
2005-11-09  2:52             ` Nick Piggin
2005-11-13  5:09               ` Paul Jackson
2005-11-13  5:14                 ` Paul Jackson
2005-11-13  7:00                   ` Nathan Scott
2005-11-13  7:12                   ` Andrew Morton
2005-11-13  7:47                     ` Paul Jackson
2005-11-08  3:07 ` Paul Jackson
2005-11-08  5:31   ` Nick Piggin
2005-11-09  0:17 ` Paul Jackson

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=20051107175358.62c484a3.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rohit.seth@intel.com \
    --cc=torvalds@osdl.org \
    /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