From: ebiederm@xmission.com (Eric W. Biederman)
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: 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 13:16:28 -0700 [thread overview]
Message-ID: <m1ac1rpn4z.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <1166040131.27217.888.camel@laptopd505.fenrus.org> (Arjan van de Ven's message of "Wed, 13 Dec 2006 21:02:11 +0100")
Arjan van de Ven <arjan@linux.intel.com> writes:
>> .
>>
>> 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.
>
> it really IS a hard limit.
Ok. Which generally makes it uninteresting. The only cases that I know
with a hard limit are completely unrouteable.
In addition upon reflection you don't handle PER_CPU irqs properly. As
I recall ia64 uses a different per cpu irq source to target each
individual processor. But because they are the same the share the
irq source.
I don't think allowed_affinity can even describe the case above.
Eric
prev parent reply other threads:[~2006-12-13 20:16 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
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 [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=m1ac1rpn4z.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=arjan@linux.intel.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®