linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: mel@skynet.ie (Mel Gorman)
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Badari <pbadari@us.ibm.com>,
	melgor@ie.ibm.com, haveblue@us.ibm.com,
	linux-mm <linux-mm@kvack.org>
Subject: Re: [RFC][PATCH 0/2] Export memblock migrate type to /sysfs
Date: Thu, 25 Oct 2007 11:10:24 +0100	[thread overview]
Message-ID: <20071025101024.GA30732@skynet.ie> (raw)
In-Reply-To: <20071025162118.bb24aa4b.kamezawa.hiroyu@jp.fujitsu.com>

On (25/10/07 16:21), KAMEZAWA Hiroyuki didst pronounce:
> On Wed, 24 Oct 2007 21:51:20 -0700
> Badari <pbadari@us.ibm.com> wrote:
> > > How about showing information as following ?
> > > ==
> > > %cat ./memory/memory0/mem_type
> > >  1 0 0 0 0
> > > %
> > > as 
> > >  Reserved Unmovable Movable Reserve Isolate
> > >
> > >   
> > Personally, I have no problem. But its against the rules of /sysfs - 
> > "one value per file" rule :(
> > I would say, lets keep it simple for now and extend it if needed.
> > 
> Hmm, but misleading information is not good.
> 
> How about adding "Mixed" status for memory section which containes multiple
> page types ? For memory hotplug, it's enough.
> 

"Mixed" to me implies that the section doesn't contain exclusively pages
of that type. It never happens in ZONE_MOVABLE of course, but it can happen
elsewhere due to fragmentation. "Multiple" I'd be happy with. So if we saw
"Movable", it's movable blocks only in that section but "Multiple" means
that there are more than one pageblock type in that section.

At some time in the future, Movable-mixed would imply that this is a
Movable section but memory pressure forced non-movable pages in there.
Again, would never happen in ZONE_MOVABLE.

-- 
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-25 10:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-24 16:37 [RFC][PATCH 0/2] Export memblock migrate type to /sysfs Badari Pulavarty
2007-10-25  0:35 ` KAMEZAWA Hiroyuki
2007-10-25  4:51   ` Badari
2007-10-25  7:21     ` KAMEZAWA Hiroyuki
2007-10-25 10:10       ` Mel Gorman [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=20071025101024.GA30732@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;
as well as URLs for NNTP newsgroup(s).