All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ashok Raj <ashok.raj@intel.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [RFC][patch 2/10] Multiple vector domain support - cpu and domain management
Date: Thu, 14 Jul 2005 18:03:43 +0000	[thread overview]
Message-ID: <20050714110342.B2630@unix-os.sc.intel.com> (raw)
In-Reply-To: <42D62E73.1050108@jp.fujitsu.com>

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?..
 
> +
> +#ifdef CONFIG_VECTOR_DOMAIN
> +int ia64_cpu_domain_map[NR_CPUS];
> +cpumask_t ia64_domain_cpumask[NR_VECTOR_DOMAINS];
> +
> +void __devinit
> +ia64_attach_cpu_to_domain (int cpu)
> +{
> +	static int domain = -1;
> +
> +	/* Simple Round Robin for now */
> +	if (++domain >= NR_VECTOR_DOMAINS)
> +		domain = 0;
> +	ia64_cpu_domain_map[cpu] = domain;
> +	cpu_set(cpu, ia64_domain_cpumask[domain]);
> +}
> +#endif /* CONFIG_VECTOR_DOMAIN */

-- 
Cheers,
Ashok Raj
- Open Source Technology Center

  reply	other threads:[~2005-07-14 18:03 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 ` Ashok Raj [this message]
2005-07-14 18:09 ` [RFC][patch 2/10] Multiple vector domain support - cpu and domain management 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

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=20050714110342.B2630@unix-os.sc.intel.com \
    --to=ashok.raj@intel.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 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.