From: Michael Wang <wangyun@linux.vnet.ibm.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Ingo Molnar <mingo@elte.hu>,
Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>,
"Nikunj A. Dadhania" <nikunj@linux.vnet.ibm.com>,
Ram Pai <linuxram@us.ibm.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: About dynamic schedule domain
Date: Mon, 14 May 2012 16:08:50 +0800 [thread overview]
Message-ID: <4FB0BD92.5030202@linux.vnet.ibm.com> (raw)
Hi, Peter
I have read the mail thread on the topic about dynamic sched domain in link:
http://marc.info/?l=linux-kernel&m=130822782111533&w=2
But I'm not sure, is the dynamical sched domain means we can change the
sched domain at running time through proc or something else?
If it is still pending on implementation, could you please tell me how
things going on and what's the idea you have mentioned in the mail?
I want to do some help if I could :)
Regards,
Michael Wang
reply other threads:[~2012-05-14 8:09 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=4FB0BD92.5030202@linux.vnet.ibm.com \
--to=wangyun@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=mingo@elte.hu \
--cc=nikunj@linux.vnet.ibm.com \
--cc=vatsa@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.