From: Dmitry Adamushko <dmitry.adamushko@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
LKML <linux-kernel@vger.kernel.org>
Subject: [patch, rfc: 0/2] sched, hotplug: cpu-hotplug vs. sched synchronization
Date: Fri, 25 Jul 2008 00:05:56 +0200 [thread overview]
Message-ID: <1216937156.5368.5.camel@earth> (raw)
Hi,
RFC, because I obviously might have missed something important and if
not, there can be better ways to address the issues (a few alternatives
included).
[1/2] safe use of rq->migration_thread and find_busiest_queue()
[2/2] ensure a task is on the valid cpu after set_cpus_allowed_ptr()
--Dmitry
reply other threads:[~2008-07-24 22:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1216937156.5368.5.camel@earth \
--to=dmitry.adamushko@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--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