All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, Dave Hansen <haveblue@us.ibm.com>,
	hari@in.ibm.com
Subject: Re: [RFC][PATCH] nameing reserved pages [0/3]
Date: Wed, 20 Apr 2005 23:15:04 +0900	[thread overview]
Message-ID: <426663E8.3080502@jp.fujitsu.com> (raw)
In-Reply-To: <1114000447.6238.64.camel@laptopd505.fenrus.org>

Arjan van de Ven wrote:

>>For example, Memory Hotplug can ignore (a).
>>    
>>
>
>Memory Hotplug can also use page_is_ram().
>  
>
Yes. we can use page_is_ram() for finding (a)memory hole.
But I'd like to catch other removable PG_reserved pages like (d)Isorated 
by MCA (e)used by perfmon and
some of (b) used by kernerl and (c) Set by drivers.
What I'm thinking of is to detect whether memory is hot-removable or not 
before removing actually.

>/dev/memstate really looks like a bad idea to me as well... I rather
>have less than more /dev/*mem*
>  
>
For showing page usage and its "location", I've thought of other 
interface, sysfs, procfs...
But I have no idea.
Physical memory area has vast space and I want to use lseek() or 
ioctl().( I don't like  ioctl())
Do you have any recommendation ?

-- Kame



  reply	other threads:[~2005-04-20 14:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-20 12:02 [RFC][PATCH] nameing reserved pages [0/3] KAMEZAWA Hiroyuki
2005-04-20 12:34 ` Arjan van de Ven
2005-04-20 14:15   ` Kamezawa Hiroyuki [this message]
2005-04-20 14:30     ` Arjan van de Ven
2005-04-20 14:58       ` Kamezawa Hiroyuki
2005-04-20 17:18       ` Dave Hansen
2005-04-20 17:00   ` Dave Hansen

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=426663E8.3080502@jp.fujitsu.com \
    --to=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=arjan@infradead.org \
    --cc=hari@in.ibm.com \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.