From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [RFC][patch 2/10] Multiple vector domain support - cpu and domain
Date: Sat, 16 Jul 2005 01:41:41 +0000 [thread overview]
Message-ID: <42D865D5.5090305@jp.fujitsu.com> (raw)
In-Reply-To: <42D62E73.1050108@jp.fujitsu.com>
Ashok Raj wrote:
> On Thu, Jul 14, 2005 at 06:20:51PM +0900, Kenji Kaneshige wrote:
>
>>This patch add the code to handle the relationship between cpu and
>>domains. We need more consideration about how to separate vector
>>domains.
>>
>>Signed-off-by: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
>>
>>---
>>
>
>
> Should we consider this based on some mach-* like schemes, so for e.g in
> NUMA case we could use node as a VECTOR_DOMAIN? ... or maybe we could
> somehow tie this into CPUSETS?..
>
>
I think some hardware implements hardware interrupt
redirection on each node. For such system, I think it
is good idea to use NUMA node as a VECTOR_DOMAIN to
make it possible to use hardware interrupt redirection.
Currently I don't have other reasons to use the set of
processors as a vector domain instead of per-CPU approach.
Does anyone have other reasons to use other approach than
per-CPU approach?
Thanks,
Kenji Kaneshige
prev parent reply other threads:[~2005-07-16 1:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-14 9:20 [RFC][patch 2/10] Multiple vector domain support - cpu and domain Kenji Kaneshige
2005-07-14 18:03 ` [RFC][patch 2/10] Multiple vector domain support - cpu and domain management Ashok Raj
2005-07-14 18:09 ` david mosberger
2005-07-14 18:23 ` [RFC][patch 2/10] Multiple vector domain support - cpu and domain Zwane Mwaikambo
2005-07-16 1:41 ` Kenji Kaneshige [this message]
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=42D865D5.5090305@jp.fujitsu.com \
--to=kaneshige.kenji@jp.fujitsu.com \
--cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox