From: Li Zefan <lizf@cn.fujitsu.com>
To: rolando.martins@gmail.com
Cc: containers@lists.linux-foundation.org,
Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: cpuset.sched_relax_domain_level problem
Date: Mon, 22 Aug 2011 09:08:41 +0800 [thread overview]
Message-ID: <4E51AC19.4010208@cn.fujitsu.com> (raw)
In-Reply-To: <CABcS5h13R0omxkZW_aJaza9FynbKSc=CVaYDkHMvJ64nAnWPvw@mail.gmail.com>
Add Cc's
Rolando Martins wrote:
> Hi,
> I am testing kernel 3.0.3 and I am unable to "echo 3 >
> cpuset.sched_relax_domain_level".
> I was able to do it in 2.6.39.
>
> Any clues?
>
I think it's because your machine doesn't support level 3.
This commit made the change:
commit 60495e7760d8ee364695006af37309b0755e0e17
Author: Peter Zijlstra <a.p.zijlstra@chello.nl>
Date: Thu Apr 7 14:10:04 2011 +0200
sched: Dynamic sched_domain::level
Remove the SD_LV_ enum and use dynamic level assignments.
parent reply other threads:[~2011-08-22 1:08 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CABcS5h13R0omxkZW_aJaza9FynbKSc=CVaYDkHMvJ64nAnWPvw@mail.gmail.com>]
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=4E51AC19.4010208@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=containers@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rolando.martins@gmail.com \
--cc=seto.hidetoshi@jp.fujitsu.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