All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Gary Hade <garyhade@us.ibm.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
	Yasunori Goto <y-goto@jp.fujitsu.com>,
	Badari Pulavarty <pbadari@us.ibm.com>, Mel Gorman <mel@csn.ul.ie>,
	Chris McDermott <lcm@us.ibm.com>,
	linux-kernel@vger.kernel.org, x86@kernel.org,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] [RESEND] x86_64: add memory hotremove config option
Date: Sat, 6 Sep 2008 02:01:54 +0200	[thread overview]
Message-ID: <20080906000154.GC18288@one.firstfloor.org> (raw)
In-Reply-To: <20080905215452.GF11692@us.ibm.com>

> 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.

-Andi


WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <andi@firstfloor.org>
To: Gary Hade <garyhade@us.ibm.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
	Yasunori Goto <y-goto@jp.fujitsu.com>,
	Badari Pulavarty <pbadari@us.ibm.com>, Mel Gorman <mel@csn.ul.ie>,
	Chris McDermott <lcm@us.ibm.com>,
	linux-kernel@vger.kernel.org, x86@kernel.org,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] [RESEND] x86_64: add memory hotremove config option
Date: Sat, 6 Sep 2008 02:01:54 +0200	[thread overview]
Message-ID: <20080906000154.GC18288@one.firstfloor.org> (raw)
In-Reply-To: <20080905215452.GF11692@us.ibm.com>

> 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.

-Andi

--
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:[~2008-09-05 23:58 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-05 17:21 [PATCH] [RESEND] x86_64: add memory hotremove config option Gary Hade
2008-09-05 17:21 ` Gary Hade
2008-09-05 17:44 ` Ingo Molnar
2008-09-05 17:44   ` Ingo Molnar
2008-09-05 18:14   ` Badari Pulavarty
2008-09-05 18:14     ` Badari Pulavarty
2008-09-05 18:17     ` Ingo Molnar
2008-09-05 18:17       ` Ingo Molnar
2008-09-08 21:52       ` [PATCH] Cleanup to make remove_memory() arch neutral Badari Pulavarty
2008-09-08 21:52         ` Badari Pulavarty
2008-09-09  0:56         ` Andrew Morton
2008-09-09  0:56           ` Andrew Morton
2008-09-09  1:14           ` Randy Dunlap
2008-09-09  1:14             ` Randy Dunlap
2008-09-09  1:21           ` Yasunori Goto
2008-09-09  1:21             ` Yasunori Goto
2008-09-09 15:12             ` Badari Pulavarty
2008-09-09 15:12               ` Badari Pulavarty
2008-09-08 21:56       ` [PATCH] x86: add memory hotremove config option Badari Pulavarty
2008-09-08 21:56         ` Badari Pulavarty
2008-09-05 18:04 ` [PATCH] [RESEND] x86_64: " Andi Kleen
2008-09-05 18:04   ` Andi Kleen
2008-09-05 18:31   ` Badari Pulavarty
2008-09-05 18:31     ` Badari Pulavarty
2008-09-05 18:54     ` Andi Kleen
2008-09-05 18:54       ` Andi Kleen
2008-09-05 22:34       ` Badari Pulavarty
2008-09-05 22:34         ` Badari Pulavarty
2008-09-05 19:53   ` Gary Hade
2008-09-05 19:53     ` Gary Hade
2008-09-05 20:04     ` Andi Kleen
2008-09-05 20:04       ` Andi Kleen
2008-09-05 21:54       ` Gary Hade
2008-09-05 21:54         ` Gary Hade
2008-09-06  0:01         ` Andi Kleen [this message]
2008-09-06  0:01           ` Andi Kleen
2008-09-06  7:06           ` Yasunori Goto
2008-09-06  7:06             ` Yasunori Goto
2008-09-06  8:53             ` Andi Kleen
2008-09-06  8:53               ` Andi Kleen
2008-09-08  5:52               ` Nick Piggin
2008-09-08  5:52                 ` Nick Piggin
2008-09-08  9:36                 ` Andi Kleen
2008-09-08  9:36                   ` Andi Kleen
2008-09-08  9:46                   ` Nick Piggin
2008-09-08  9:46                     ` Nick Piggin
2008-09-08 10:30                     ` Andi Kleen
2008-09-08 10:30                       ` Andi Kleen
2008-09-08 11:19                       ` Nick Piggin
2008-09-08 11:19                         ` Nick Piggin
2008-09-08 11:30                         ` Andi Kleen
2008-09-08 11:30                           ` Andi Kleen
2008-09-08 13:48                           ` Nick Piggin
2008-09-08 13:48                             ` Nick Piggin
2008-09-06 14:33             ` Ingo Molnar
2008-09-06 14:33               ` Ingo Molnar
2008-09-06 16:00               ` kamezawa.hiroyu
2008-09-06 16:00                 ` kamezawa.hiroyu
2008-09-06 16:05                 ` kamezawa.hiroyu
2008-09-06 16:05                   ` kamezawa.hiroyu
2008-09-06 16:17                 ` Ingo Molnar
2008-09-06 16:17                   ` Ingo Molnar

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=20080906000154.GC18288@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=akpm@linux-foundation.org \
    --cc=garyhade@us.ibm.com \
    --cc=lcm@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    --cc=mingo@elte.hu \
    --cc=pbadari@us.ibm.com \
    --cc=x86@kernel.org \
    --cc=y-goto@jp.fujitsu.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.