From: Dave Hansen <haveblue@us.ibm.com>
To: Mel Gorman <mel@skynet.ie>
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 10:18:46 -0700 [thread overview]
Message-ID: <1193419126.24087.130.camel@localhost> (raw)
In-Reply-To: <20071026161406.GB19443@skynet.ie>
On Fri, 2007-10-26 at 17:14 +0100, Mel Gorman wrote:
>
> 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.
I completely agree.
-- 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>
next prev parent reply other threads:[~2007-10-26 17:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 15:55 [PATCH 2/2] Add mem_type in /syfs to show memblock migrate type 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
2007-10-26 17:18 ` Dave Hansen [this message]
-- 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=1193419126.24087.130.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=mel@skynet.ie \
--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 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.