From: Paul Menage <menage@google.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux Containers <containers@lists.linux-foundation.org>
Subject: Re: [PATCH] cgroups: update documentation about css_set hash table
Date: Tue, 17 Feb 2009 17:31:52 -0800 [thread overview]
Message-ID: <6599ad830902171731m5bc41046r710255661defcf9f@mail.gmail.com> (raw)
In-Reply-To: <499B64DA.5070403@cn.fujitsu.com>
On Tue, Feb 17, 2009 at 5:31 PM, Li Zefan <lizf@cn.fujitsu.com> wrote:
> The css_set hash table was introduced in 2.6.26, so update the documentation
> accordingly.
>
> Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
Acked-by: Paul Menage <menage@google.com>
> ---
> Documentation/cgroups/cgroups.txt | 6 ++----
> 1 files changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/cgroups/cgroups.txt b/Documentation/cgroups/cgroups.txt
> index d9e5d6f..93feb84 100644
> --- a/Documentation/cgroups/cgroups.txt
> +++ b/Documentation/cgroups/cgroups.txt
> @@ -252,10 +252,8 @@ cgroup file system directories.
> When a task is moved from one cgroup to another, it gets a new
> css_set pointer - if there's an already existing css_set with the
> desired collection of cgroups then that group is reused, else a new
> -css_set is allocated. Note that the current implementation uses a
> -linear search to locate an appropriate existing css_set, so isn't
> -very efficient. A future version will use a hash table for better
> -performance.
> +css_set is allocated. The appropriate existing css_set is located by
> +looking into a hash table.
>
> To allow access from a cgroup to the css_sets (and hence tasks)
> that comprise it, a set of cg_cgroup_link objects form a lattice;
> --
> 1.5.4.rc3
>
prev parent reply other threads:[~2009-02-18 1:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 1:31 Li Zefan
2009-02-18 1:31 ` Paul Menage [this message]
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=6599ad830902171731m5bc41046r710255661defcf9f@mail.gmail.com \
--to=menage@google.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.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
all inboxes | Powered by JetHome®