From: Max Krasnyanskiy <maxk@qualcomm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Oleg Nesterov <oleg@tv-sign.ru>,
mingo@elte.hu, Andrew Morton <akpm@linux-foundation.org>,
David Rientjes <rientjes@google.com>, Paul Jackson <pj@sgi.com>,
menage@google.com, linux-kernel@vger.kernel.org,
Mark Hounschell <dmarkh@cfl.rr.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: workqueue cpu affinity
Date: Thu, 12 Jun 2008 12:10:11 -0700 [thread overview]
Message-ID: <48517493.30305@qualcomm.com> (raw)
In-Reply-To: <1213296240.31518.163.camel@twins>
Peter Zijlstra wrote:
> Sorry for being late,.. and I'm afraid most will have to wait a bit
> longer :-(
>
> On Wed, 2008-06-11 at 12:02 -0700, Max Krasnyansky wrote:
>> Peter Zijlstra wrote:
>
>>> Please don't take this too personal - I'm glad you're working on this.
>>> I'm just trying to see what we can generalize.
>
>> Oh, no worries, I'm not taking this personally, except maybe the "most your
>> ideas suck" part which got me a little bit ;-). I'm definitely all for making
>> it suitable for more general usage.
>> This is actually first constructive criticism (except for the "most of your
>> ideas suck" part :).
>
> No, no, you understand me wrong (or I expressed myself wrong). Your
> ideas are good, its just the implementation / execution I have issues
> with.
>
> Like with extending the isolation map, what didn't leave any room for
> hard-rt smp schedulers or multiple rt domains. Whereas the cpuset stuff
> does.
Yep. And I redid it completely and switched gears to fix/improve cpusets,
genirq, etc.
Anyway, I think we're on the same page. Please look over the summary that I
sent out and see if I missed anything.
Max
next prev parent reply other threads:[~2008-06-12 19:10 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 19:57 [patch] sched: prevent bound kthreads from changing cpus_allowed David Rientjes
2008-06-05 20:29 ` Paul Jackson
2008-06-05 21:12 ` David Rientjes
2008-06-09 20:59 ` Max Krasnyanskiy
2008-06-09 22:07 ` David Rientjes
2008-06-10 4:23 ` Max Krasnyansky
2008-06-10 17:04 ` David Rientjes
2008-06-10 16:30 ` cpusets and kthreads, inconsistent behaviour Max Krasnyansky
2008-06-10 18:47 ` David Rientjes
2008-06-10 20:44 ` Max Krasnyansky
2008-06-10 20:54 ` David Rientjes
2008-06-10 21:15 ` Max Krasnyansky
2008-06-10 6:44 ` [patch] sched: prevent bound kthreads from changing cpus_allowed Peter Zijlstra
2008-06-10 15:38 ` Max Krasnyansky
2008-06-10 17:00 ` Oleg Nesterov
2008-06-10 17:19 ` Peter Zijlstra
2008-06-10 20:24 ` workqueue cpu affinity Max Krasnyansky
2008-06-11 6:49 ` Peter Zijlstra
2008-06-11 19:02 ` Max Krasnyansky
2008-06-12 18:44 ` Peter Zijlstra
2008-06-12 19:10 ` Max Krasnyanskiy [this message]
2008-06-11 16:08 ` Oleg Nesterov
2008-06-11 19:21 ` Max Krasnyansky
2008-06-11 19:21 ` Max Krasnyansky
2008-06-12 16:35 ` Oleg Nesterov
2008-06-11 20:44 ` Max Krasnyansky
2008-06-10 18:00 ` [patch] sched: prevent bound kthreads from changing cpus_allowed Max Krasnyansky
2008-06-05 20:52 ` Daniel Walker
2008-06-05 21:47 ` Paul Jackson
2008-06-10 10:28 ` Ingo Molnar
2008-06-10 17:47 ` Oleg Nesterov
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=48517493.30305@qualcomm.com \
--to=maxk@qualcomm.com \
--cc=akpm@linux-foundation.org \
--cc=dmarkh@cfl.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=mingo@elte.hu \
--cc=oleg@tv-sign.ru \
--cc=peterz@infradead.org \
--cc=pj@sgi.com \
--cc=rientjes@google.com \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).