linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: Arjan van de Ven <arjan@infradead.org>, Andi Kleen <ak@suse.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] i386: Per node IDT
Date: Tue, 12 Jul 2005 00:17:18 +0900	[thread overview]
Message-ID: <42D28D7E.3050401@jp.fujitsu.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0507110804210.16055@montezuma.fsmlabs.com>

Hi,

> Agreed, the first version was a per cpu one simply so that i could test it 
> on a normal SMP system. Andi seems to be of the same opinion, what do you 
> think of the hotplug cpu case (explained in previous email)?

I think we need to migrate interrupts to the other CPU
in the hotplug CPU case. Even when we use per node approach,
we need to consider interrupt migration between nodes
because all CPUs on the node could be hot-removed.

Thanks,
Kenji Kaneshige

  parent reply	other threads:[~2005-07-11 18:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.61.0507101617240.16055@montezuma.fsmlabs.com.suse.lists.linux.kernel>
2005-07-11  1:59 ` [RFC][PATCH] i386: Per node IDT Andi Kleen
2005-07-11  4:02   ` Arjan van de Ven
2005-07-11  4:08     ` Andi Kleen
2005-07-11 14:09     ` Zwane Mwaikambo
2005-07-11 14:05       ` Arjan van de Ven
2005-07-11 15:17       ` Kenji Kaneshige [this message]
2005-07-11 13:34   ` Zwane Mwaikambo
2005-07-11 15:03     ` Brian Gerst
2005-07-11 15:21       ` Zwane Mwaikambo
2005-07-11 16:39         ` Andi Kleen
2005-07-11 12:28 Oleg Nesterov
2005-07-11 14:03 ` Zwane Mwaikambo
2005-07-11 14:44   ` Oleg Nesterov
2005-07-11 15:05     ` Zwane Mwaikambo
2005-07-11 15:19     ` Oleg Nesterov
2005-08-07  1:13       ` Zwane Mwaikambo
2005-08-07 10:47         ` Oleg Nesterov
  -- strict thread matches above, loose matches on Subject: below --
2005-07-10 22:41 Zwane Mwaikambo

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=42D28D7E.3050401@jp.fujitsu.com \
    --to=kaneshige.kenji@jp.fujitsu.com \
    --cc=ak@suse.de \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zwane@arm.linux.org.uk \
    /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).