[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20110906151747.26aa4fd2.akpm@linux-foundation.org>
Date: Tue, 6 Sep 2011 15:17:47 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Frederic Weisbecker <fweisbec@...il.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
Paul Menage <paul@...lmenage.org>,
Li Zefan <lizf@...fujitsu.com>,
Johannes Weiner <hannes@...xchg.org>,
Aditya Kali <adityakali@...gle.com>,
Oleg Nesterov <oleg@...hat.com>,
Kay Sievers <kay.sievers@...y.org>,
Tim Hockin <thockin@...kin.org>, Tejun Heo <tj@...nel.org>
Subject: Re: [PATCH 02/12] cgroups: New resource counter inheritance API
On Tue, 6 Sep 2011 02:12:56 +0200
Frederic Weisbecker <fweisbec@...il.com> wrote:
> +void res_counter_inherit(struct res_counter *counter, int member)
> +{
> + struct res_counter *parent;
> + unsigned long long val;
> +
> + parent = counter->parent;
> + if (parent) {
> + val = res_counter_read_u64(parent, member);
> + res_counter_write_u64(counter, member, val);
> + }
> +}
What locking protects the read-modify-write? If none, please fix,
otherwise please document it.
All of kernel/res_counter.c is charmingly undocumented.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists