From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Paul Jackson <pj@sgi.com>
Cc: maxk@qualcomm.com, menage@google.com, mingo@elte.hu,
linux-kernel@vger.kernel.org
Subject: Re: IRQ affinities (was: boot cgroup questions)
Date: Fri, 09 May 2008 14:14:30 +0200 [thread overview]
Message-ID: <1210335270.13978.252.camel@twins> (raw)
In-Reply-To: <20080509070314.f86aece4.pj@sgi.com>
On Fri, 2008-05-09 at 07:03 -0500, Paul Jackson wrote:
> Peter wrote:
> > I see two use-cases:
> >
> > - Isolation
> > - NUMA node devices
>
> Ok ... so let me propose an entirely different solution.
>
> No doubt it has some terrible flaw, but I'll just have to
> await your replies to see what that is.
>
> How about we have:
>
> 1) Yet another text config file in /etc, this one containing
> lines having two fields:
> * a list of IRQs, and
> * a cpumask.
> This file would specify which CPUs should handle which IRQs.
>
> 2) A utility that can be run, after changing the above file,
> to poke the proper cpumask to each IRQ, as specified in
> the file.
>
> (Obligatory "simple" marketing claim: the above requires no
> kernel changes.)
>
> What am I missing?
Two points:
- we can't currently set irq affinities for non-existent (aka new) IRQs
- its a shame to duplicate the masks - most of this information would
also be used in the cpuset structure used to place the tasks.
next prev parent reply other threads:[~2008-05-09 12:14 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 1:23 boot cgroup questions Max Krasnyansky
2008-03-12 1:27 ` Paul Menage
2008-03-12 2:34 ` Max Krasnyansky
2008-03-12 2:36 ` Paul Menage
2008-03-12 2:53 ` Max Krasnyansky
2008-03-12 3:09 ` Paul Menage
2008-03-12 3:39 ` Max Krasnyansky
2008-03-12 4:59 ` Paul Jackson
2008-03-12 18:24 ` Max Krasnyanskiy
2008-03-12 18:57 ` Paul Jackson
2008-03-12 19:11 ` Max Krasnyanskiy
2008-03-12 19:32 ` Paul Jackson
2008-03-12 20:08 ` Max Krasnyanskiy
2008-03-12 20:37 ` Paul Jackson
2008-03-12 22:29 ` Max Krasnyanskiy
2008-03-12 23:30 ` Paul Jackson
2008-03-13 0:57 ` Max Krasnyanskiy
2008-03-13 7:03 ` Paul Jackson
2008-04-10 18:03 ` Max Krasnyanskiy
2008-04-14 18:39 ` Paul Jackson
2008-05-09 10:45 ` Peter Zijlstra
2008-05-09 11:17 ` IRQ affinities (was: boot cgroup questions) Paul Jackson
2008-05-09 11:48 ` Peter Zijlstra
2008-05-09 12:03 ` Paul Jackson
2008-05-09 12:14 ` Peter Zijlstra [this message]
2008-05-09 12:36 ` Paul Jackson
2008-05-09 17:43 ` Paul Jackson
2008-05-21 1:21 ` IRQ affinities Max Krasnyanskiy
2008-05-21 1:14 ` Max Krasnyanskiy
2008-05-21 4:45 ` Arjan van de Ven
2008-05-21 16:18 ` Max Krasnyanskiy
2008-05-21 6:34 ` Paul Jackson
2008-05-21 17:58 ` Max Krasnyanskiy
2008-04-14 18:42 ` boot cgroup questions Paul Jackson
2008-03-13 7:12 ` Paul Jackson
2008-04-10 17:24 ` Max Krasnyanskiy
2008-04-10 17:37 ` Paul Jackson
2008-03-12 23:32 ` Paul Jackson
2008-03-13 0:46 ` Max Krasnyanskiy
2008-03-12 19:16 ` Paul Menage
2008-03-12 19:24 ` Paul Jackson
2008-03-12 19:30 ` Max Krasnyanskiy
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=1210335270.13978.252.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.com \
--cc=menage@google.com \
--cc=mingo@elte.hu \
--cc=pj@sgi.com \
/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