From: "Yinghai Lu" <yinghai.lu@amd.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "Arjan van de Ven" <arjan@linux.intel.com>,
"Ingo Molnar" <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] Add allowed_affinity to the irq_desc to make it possible to have restricted irqs
Date: Wed, 13 Dec 2006 22:24:41 -0800 [thread overview]
Message-ID: <86802c440612132224w795f3e01qfeee7183b791922c@mail.gmail.com> (raw)
In-Reply-To: <m11wn3p0zk.fsf@ebiederm.dsl.xmission.com>
On 12/13/06, Eric W. Biederman <ebiederm@xmission.com> wrote:
> Arjan van de Ven <arjan@linux.intel.com> writes:
> > the numa case is already handled; the needed info for that is exposed already
> > enough... at least for irqbalance
>
> What is the problem you are trying to solve?
>
> If it is just interrupts irqbalanced can't help with we can do that
> with a single bit.
>
> My basic problem with understanding what this patch is trying to
> solve is that I've seen some theoretical cases raised but I don't see
> the real world problem.
Good question.
irqbalance could use set_affinity from boot cpu to final cpu.
YH
next prev parent reply other threads:[~2006-12-14 6:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-13 13:53 Arjan van de Ven
2006-12-13 19:41 ` Eric W. Biederman
2006-12-13 19:43 ` Ingo Molnar
2006-12-13 20:06 ` Eric W. Biederman
2006-12-13 20:19 ` Ingo Molnar
2006-12-13 20:23 ` Arjan van de Ven
2006-12-14 4:14 ` Eric W. Biederman
2006-12-14 6:24 ` Yinghai Lu [this message]
2006-12-14 7:55 ` Arjan van de Ven
2006-12-14 8:22 ` Eric W. Biederman
2006-12-14 8:23 ` Arjan van de Ven
2006-12-14 8:34 ` Eric W. Biederman
2006-12-14 8:40 ` Arjan van de Ven
2006-12-13 20:02 ` Arjan van de Ven
2006-12-13 20:16 ` Eric W. Biederman
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=86802c440612132224w795f3e01qfeee7183b791922c@mail.gmail.com \
--to=yinghai.lu@amd.com \
--cc=arjan@linux.intel.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®