mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lin Feng <linfeng@cn.fujitsu.com>
To: Lenky Gao <lenky.gao@gmail.com>
Cc: linux-kernel@vger.kernel.org, yinghai@kernel.org, mingo@elte.hu,
	gorcunov@gmail.com, rusty@rustcorp.com.au, sivanich@sgi.com,
	agordeev@redhat.com
Subject: Re: Question: How to distribute the interrupts over multiple cores?
Date: Mon, 25 Mar 2013 17:41:10 +0800	[thread overview]
Message-ID: <51501BB6.5000306@cn.fujitsu.com> (raw)
In-Reply-To: <CAAO_Xo7CTzow1TN+4bmmHH9KB4NSLRv5ZsOmwEC2KGTxDc-1Ug@mail.gmail.com>

Hi,

On 03/25/2013 05:00 PM, Lenky Gao wrote:
> I have found a comment in function physflat_cpu_mask_to_apicid to explain why.
> 
> static unsigned int physflat_cpu_mask_to_apicid(const struct cpumask *cpumask)
> {
> 	int cpu;
> 
> 	/*
> 	 * We're using fixed IRQ delivery, can only return one phys APIC ID.
> 	 * May as well be the first.
> 	 */
> ...
> 
> This is mean i can not distribute the interrupts over multiple cores
> when the machine have more than 8 cores?
> 
> 
Sorry I can't find physflat_cpu_mask_to_apicid() in latest Linux tree, seems it has
been removed out.. But just consider what you said that it's limited by "8 cores"
IMHO it's impossible or it is a bug.

thanks,
linfeng

  reply	other threads:[~2013-03-25  9:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-25  2:33 Lenky Gao
2013-03-25  2:58 ` Lin Feng
2013-03-25  3:18   ` Lenky Gao
2013-03-25  3:24     ` Lin Feng
2013-03-25  3:44       ` Lenky Gao
2013-03-25  5:19         ` Lin Feng
2013-03-25  6:46           ` Lenky Gao
2013-03-25  7:04             ` Lin Feng
2013-03-25  7:10               ` Lenky Gao
2013-03-25  9:00                 ` Lenky Gao
2013-03-25  9:41                   ` Lin Feng [this message]
2013-03-25  9:45                     ` Lenky Gao

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=51501BB6.5000306@cn.fujitsu.com \
    --to=linfeng@cn.fujitsu.com \
    --cc=agordeev@redhat.com \
    --cc=gorcunov@gmail.com \
    --cc=lenky.gao@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rusty@rustcorp.com.au \
    --cc=sivanich@sgi.com \
    --cc=yinghai@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
all inboxes | Powered by JetHome®