From: William Lee Irwin III <wli@holomorphy.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Keith Mannthey <kmannth@us.ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][Patch] fix for irq_affinity_write_proc v2.5
Date: Tue, 6 May 2003 19:27:17 -0700 [thread overview]
Message-ID: <20030507022717.GV8978@holomorphy.com> (raw)
In-Reply-To: <1052250874.1202.162.camel@dhcp22.swansea.linux.org.uk>
On Maw, 2003-05-06 at 20:03, Keith Mannthey wrote:
>> irq_affinity_write_proc currently directly calls set_ioapic_affinity
>> which writes to the ioapic. This undermines the work done by kirqd by
>> writing a cpu mask directly to the ioapic. I propose the following patch
>> to tie the /proc affinity writes into the same code path as kirqd.
>> Kirqd will enforce the affinity requested by the user.
On Tue, May 06, 2003 at 08:54:35PM +0100, Alan Cox wrote:
> Why should the kernel be enforcing policy here. You have to be root to
> do this, and root should have the ability to configure apparently stupid
> things because they may find them useful.
It's basically not working as specified for clustered hierarchical, and
in truth the specification can never be met. As it stands most calls to
it are lethal on such systems, especially those using physical destmod.
I'd prefer to have it redesigned for some validity checking and error
returns as on such systems the impossible destinations serve no purpose
but raising MCE's and/or deadlocking the box.
-- wli
next prev parent reply other threads:[~2003-05-07 2:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 19:03 [RFC][Patch] fix for irq_affinity_write_proc v2.5 Keith Mannthey
2003-05-06 19:54 ` Alan Cox
2003-05-06 21:58 ` Keith Mannthey
2003-05-07 2:27 ` William Lee Irwin III [this message]
2003-05-07 12:16 ` Alan Cox
2003-05-07 18:12 ` Keith Mannthey
2003-05-07 3:56 ` Martin J. Bligh
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=20030507022717.GV8978@holomorphy.com \
--to=wli@holomorphy.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=kmannth@us.ibm.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