All of lore.kernel.org
 help / color / mirror / Atom feed
From: Badari <pbadari@us.ibm.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: 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: Wed, 24 Oct 2007 21:51:20 -0700	[thread overview]
Message-ID: <472020C8.4090007@us.ibm.com> (raw)
In-Reply-To: <20071025093531.d2357422.kamezawa.hiroyu@jp.fujitsu.com>

KAMEZAWA Hiroyuki wrote:
> On Wed, 24 Oct 2007 09:37:40 -0700
> Badari Pulavarty <pbadari@us.ibm.com> wrote:
>
>   
>> Hi,
>>
>> Now that grouping of pages by mobility is in mainline, I would like 
>> to make use of it for selection memory blocks for hotplug memory remove.
>> Following set of patches exports memblock's migrate type to /sysfs. 
>> This would be useful for user-level agent for selecting memory blocks
>> to try to remove.
>>
>> 	[PATCH 1/2] Fix migratetype_names[] and make it available
>> 	[PATCH 2/2] Add mem_type in /syfs to show memblock migrate type
>>
>>     
> At first, I welcome this patch. Thanks :)
>   
>> Todo:
>>
>> 	Currently, we decide the memblock's migrate type looking at
>> first page of memblock. But on some architectures (x86_64), each
>> memblock can contain multiple groupings of pages by mobility. Is it
>> important to address ?
>>     
>
> Hmm, that is a problem annoying me. There is 2 points.
>
> 1. In such arch, we'll have to use ZONE_MOVABLE for hot-removable.
> 2. But from view of showing information to users, more precice is better
>    of course.
>
> 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.

Thanks,
Badari

--
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  4:51 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 [this message]
2007-10-25  7:21     ` KAMEZAWA Hiroyuki
2007-10-25 10:10       ` 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=472020C8.4090007@us.ibm.com \
    --to=pbadari@us.ibm.com \
    --cc=haveblue@us.ibm.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=melgor@ie.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.