linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mel Gorman <mel@csn.ul.ie>
To: Minchan Kim <minchan.kim@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	Rik van Riel <riel@redhat.com>,
	Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [PATCH 1/3] clean up setup_per_zone_pages_min
Date: Wed, 20 May 2009 11:21:29 +0100	[thread overview]
Message-ID: <20090520102129.GA12433@csn.ul.ie> (raw)
In-Reply-To: <20090520185803.e5b0698a.minchan.kim@barrios-desktop>

On Wed, May 20, 2009 at 06:58:03PM +0900, Minchan Kim wrote:
> Hi, Mel. 
> 
> On Wed, 20 May 2009 09:54:16 +0100
> Mel Gorman <mel@csn.ul.ie> wrote:
> 
> > On Wed, May 20, 2009 at 04:18:53PM +0900, Minchan Kim wrote:
> > > 
> > > Mel changed zone->pages_[high/low/min] with zone->watermark array.
> > > So, setup_per_zone_pages_min also have to be changed.
> > > 
> > 
> > Just to be clear, this is a function renaming to match the new zone
> > field name, not something I missed. As the function changes min, low and
> > max, a better name might have been setup_per_zone_watermarks but whether
> 
> At first, I thouht, too. But It's handle of min_free_kbytes.
> Documentation said, it's to compute a watermark[WMARK_MIN]. 
> I think many people already used that knob to contorl pages_min to keep the 
> low pages. 

Which documentation?

I'm looking at the function comment and see

 * setup_per_zone_pages_min - called when min_free_kbytes changes.
 *
 * Ensures that the pages_{min,low,high} values for each zone are set
 * correctly with respect to min_free_kbytes.

So, the values of all the watermarks are updated by that function depending
on what the new value of min_free_kbytes is. It is a bit wrong I suppose as
it missed memory hot-add

setup_per_zone_pages_min - called when min_free_kbytes changes or when memory is hot-added

> 
> So, I determined function name is proper now. 
> If setup_per_zone_watermark is better than it, we also have to change with 
> documentation. 
> 
> > you go with that name or not, this is better than what is there so;
> > 
> > Acked-by: Mel Gorman <mel@csn.ul.ie>
> 
> 
> -- 
> Kinds Regards
> Minchan Kim
> 

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

  reply	other threads:[~2009-05-20 10:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-20  7:18 [PATCH 1/3] clean up setup_per_zone_pages_min Minchan Kim
2009-05-20  7:23 ` KOSAKI Motohiro
2009-05-20  7:26   ` Minchan Kim
2009-05-20  8:54 ` Mel Gorman
2009-05-20  9:58   ` Minchan Kim
2009-05-20 10:21     ` Mel Gorman [this message]
2009-05-20 10:30       ` Minchan Kim
2009-05-20 10:47         ` Mel Gorman
2009-05-20 10:53           ` Minchan Kim

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=20090520102129.GA12433@csn.ul.ie \
    --to=mel@csn.ul.ie \
    --cc=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan.kim@gmail.com \
    --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).