From: Randy Dunlap <rdunlap@xenotime.net>
To: Wanlong Gao <wanlong.gao@gmail.com>
Cc: Paul Menage <menage@google.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Wanlong Gao <gaowanlong@cn.fujitsu.com>
Subject: Re: [PATCH] Doc:cgroup:fix a cpuset's file description in cpusets.txt
Date: Mon, 11 Jul 2011 09:48:47 -0700 [thread overview]
Message-ID: <20110711094847.f9813b65.rdunlap@xenotime.net> (raw)
In-Reply-To: <1310288313-4908-1-git-send-email-wanlong.gao@gmail.com>
On Sun, 10 Jul 2011 16:58:33 +0800 Wanlong Gao wrote:
> Only the root cpuset has cpuset.memory_pressure_enabled flag,
> but not the only one.
>
> Signed-off-by: Wanlong Gao <gaowanlong@cn.fujitsu.com>
Applied. Thanks.
> ---
> Documentation/cgroups/cpusets.txt | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/Documentation/cgroups/cpusets.txt b/Documentation/cgroups/cpusets.txt
> index 5b0d78e..5c51ed4 100644
> --- a/Documentation/cgroups/cpusets.txt
> +++ b/Documentation/cgroups/cpusets.txt
> @@ -180,7 +180,7 @@ files describing that cpuset:
> - cpuset.sched_load_balance flag: if set, load balance within CPUs on that cpuset
> - cpuset.sched_relax_domain_level: the searching range when migrating tasks
>
> -In addition, the root cpuset only has the following file:
> +In addition, only the root cpuset has the following file:
> - cpuset.memory_pressure_enabled flag: compute memory_pressure?
>
> New cpusets are created using the mkdir system call or shell
> --
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-07-11 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-10 8:58 [PATCH] Doc:cgroup:fix a cpuset's file description in cpusets.txt Wanlong Gao
2011-07-11 16:48 ` Randy Dunlap [this message]
2011-07-11 17:23 ` Paul Menage
2011-07-11 17:45 ` Randy Dunlap
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=20110711094847.f9813b65.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=gaowanlong@cn.fujitsu.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=wanlong.gao@gmail.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.