From: Ingo Molnar <mingo@elte.hu>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Arjan van de Ven <arjan@linux.intel.com>, 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 20:43:32 +0100 [thread overview]
Message-ID: <20061213194332.GA29185@elte.hu> (raw)
In-Reply-To: <m1lklbport.fsf@ebiederm.dsl.xmission.com>
* Eric W. Biederman <ebiederm@xmission.com> wrote:
> In addition the cases I can think of allowed_affinity is the wrong
> name. suggested_affinity sounds like what you are trying to implement
> and when it is merely a suggestion and not a hard limit it doesn't
> make sense to export like this.
well, there are interrupts that must be tied to a single CPU and must
never be moved away. For example per-CPU clock-events-source interrupts
are such. So allowed_affinity very much exists.
also there might be hardware that can only route a given IRQ to a subset
of CPUs. While setting set_affinity allows the irqbalance-daemon to
'probe' this mask, it's a far from optimal API.
Ingo
next prev parent reply other threads:[~2006-12-13 19:45 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 [this message]
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
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=20061213194332.GA29185@elte.hu \
--to=mingo@elte.hu \
--cc=arjan@linux.intel.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®