[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080906153855.7260.E1E9C6FF@jp.fujitsu.com>
Date: Sat, 06 Sep 2008 16:06:38 +0900
From: Yasunori Goto <y-goto@...fujitsu.com>
To: Andi Kleen <andi@...stfloor.org>
Cc: Gary Hade <garyhade@...ibm.com>, linux-mm@...ck.org,
Andrew Morton <akpm@...ux-foundation.org>,
Badari Pulavarty <pbadari@...ibm.com>,
Mel Gorman <mel@....ul.ie>, Chris McDermott <lcm@...ibm.com>,
linux-kernel@...r.kernel.org, x86@...nel.org,
Ingo Molnar <mingo@...e.hu>
Subject: Re: [PATCH] [RESEND] x86_64: add memory hotremove config option
> > I am not sure if I understand why you appear to be opposed to
> > enabling the hotremove function before all the issues related
>
> I'm quite sceptical that it can be ever made to work in a useful
> way for real hardware (as opposed to an hypervisor para virtual setup
> for which this interface is not the right way -- it should be done
> in some specific driver instead)
> And if it cannot be made to work then it will be a false promise
> to the user. They will see it and think it will work, but it will
> not.
>
> This means I don't see a real use case for this feature.
I don't think its driver is almighty.
IIRC, balloon driver can be cause of fragmentation for 24-7 system.
In addition, I have heard that memory hotplug would be useful for reducing
of power consumption of DIMM.
I have to admit that memory hotplug has many issues, but I would like to
solve them step by step.
Thanks.
--
Yasunori Goto
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists