linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: mel@skynet.ie (Mel Gorman)
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Badari Pulavarty <pbadari@us.ibm.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	melgor@ie.ibm.com, linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH 2/2] Add mem_type in /syfs to show memblock migrate type
Date: Fri, 26 Oct 2007 17:14:06 +0100	[thread overview]
Message-ID: <20071026161406.GB19443@skynet.ie> (raw)
In-Reply-To: <1193413936.24087.91.camel@localhost>

On (26/10/07 08:52), Dave Hansen didst pronounce:
> On Fri, 2007-10-26 at 10:50 +0100, Mel Gorman wrote:
> > I think that's overkill, especially as any awkward page would give the
> > section a score of 0. 
> 
> But, if we have a choice, shouldn't we go for a section that is
> completely free instead of one that has pages that need some kind of
> reclaim first?
> 

I would think that if memory is being shrunk in the system, the monitoring
software would not particularly care. If you think that might be the case,
then rename mem_removable to mem_removable_score and have it print out 0 or
1 for the moment based on the current criteria. Tell userspace developers
that the higher the score, the more suitable it is for removing.  That will
allow the introduction of a proper scoring mechanism later if there is a
good reason for it without breaking backwards compatability.

> We also don't have to have awkward pages keep giving a 0 score, as long
> as we have _some_ way of reclaiming them.  If we can't reclaim them,
> then I think it *needs* to be 0.
> 
> -- Dave
> 
> --
> 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>

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

--
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:[~2007-10-26 16:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-25 15:55 Badari Pulavarty
2007-10-25 16:07 ` Mel Gorman
2007-10-25 16:52 ` Dave Hansen
2007-10-25 17:07   ` Badari Pulavarty
2007-10-25 17:15     ` Dave Hansen
2007-10-25 17:36       ` Badari Pulavarty
2007-10-25 17:34         ` Dave Hansen
2007-10-25 18:05         ` Mel Gorman
2007-10-25 18:12           ` Dave Hansen
2007-10-26  9:50             ` Mel Gorman
2007-10-26 15:52               ` Dave Hansen
2007-10-26 16:14                 ` Mel Gorman [this message]
2007-10-26 17:18                   ` Dave Hansen
  -- strict thread matches above, loose matches on Subject: below --
2007-10-24 16:37 Badari Pulavarty
2007-10-25 10:17 ` 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=20071026161406.GB19443@skynet.ie \
    --to=mel@skynet.ie \
    --cc=haveblue@us.ibm.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=melgor@ie.ibm.com \
    --cc=pbadari@us.ibm.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