public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@engr.sgi.com>
To: mita akinobu <amgta@yacht.ocn.ne.jp>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
	Matthew Dobson <colpatch@us.ibm.com>
Subject: Re: [PATCH] shows Active/Inactive on per-node meminfo
Date: Sat, 21 Aug 2004 16:11:12 -0400	[thread overview]
Message-ID: <200408211611.12568.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <200408211529.37839.amgta@yacht.ocn.ne.jp>

On Saturday, August 21, 2004 2:29 am, mita akinobu wrote:
> get_zone_counts() is used by max_sane_readahead(), and
> max_sane_readahead() is often called in filemap_nopage().
>
> If iterating over every node is going to be very slow, the following change
> would have a little bit of improvement on a large machine?
>
>
> --- linux-2.6.8.1-mm3/mm/readahead.c.orig	2004-08-21 15:18:08.924273720
> +0900 +++ linux-2.6.8.1-mm3/mm/readahead.c	2004-08-21 15:22:31.123413392
> +0900 @@ -572,6 +572,6 @@ unsigned long max_sane_readahead(unsigne
>  	unsigned long inactive;
>  	unsigned long free;
>
> -	get_zone_counts(&active, &inactive, &free);
> +	__get_zone_counts(&active, &inactive, &free, NODE_DATA(numa_node_id()));
>  	return min(nr, (inactive + free) / 2);
>  }

Good catch, this looks good.  for_each_pgdat just raises a red flag for me 
these days. :)

Thanks,
Jesse

      reply	other threads:[~2004-08-21 20:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-20 18:02 [PATCH] shows Active/Inactive on per-node meminfo mita akinobu
2004-08-20 18:48 ` Jesse Barnes
2004-08-20 19:01   ` Jesse Barnes
2004-08-20 22:25     ` Andrew Morton
2004-08-20 23:08       ` Matthew Dobson
2004-08-21 20:09       ` Jesse Barnes
2004-08-21  6:29   ` mita akinobu
2004-08-21 20:11     ` Jesse Barnes [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=200408211611.12568.jbarnes@engr.sgi.com \
    --to=jbarnes@engr.sgi.com \
    --cc=akpm@osdl.org \
    --cc=amgta@yacht.ocn.ne.jp \
    --cc=colpatch@us.ibm.com \
    --cc=linux-kernel@vger.kernel.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