From: Max Krasnyanskiy <maxk@qualcomm.com>
To: Paul Jackson <pj@sgi.com>
Cc: Paul Menage <menage@google.com>,
mingo@elte.hu, a.p.zijlstra@chello.nl,
linux-kernel@vger.kernel.org
Subject: Re: boot cgroup questions
Date: Wed, 12 Mar 2008 12:30:53 -0700 [thread overview]
Message-ID: <47D82F6D.2000801@qualcomm.com> (raw)
In-Reply-To: <20080312142414.71c5731f.pj@sgi.com>
Paul Jackson wrote:
> Paul M wrote:
>> Not cgroups, no. If you really wanted to extend cpusets specifically
>> to allow irqs to be assigned to a cpuset to control which cpus they
>> could execute on, then that might be a possibility. But I don't see
>> how this would be useful for any other cgroup subsystem, so it doesn't
>> belong in the generic framework.
>
> Ok - a sensible decision.
>
>> My feeling is that just using a simple bitmask assignment, unrelated
>> to cpusets or cgroups, as Max suggested in his later email is the way
>> to go.
>
> I'll have to have another go at reading his replies. I seem to have
> more difficulty making sense of his posts ... not sure why.
I'm sure it's because of gazillion typos in them :).
Max
prev parent reply other threads:[~2008-03-12 19:31 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
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 [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=47D82F6D.2000801@qualcomm.com \
--to=maxk@qualcomm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--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