[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20071003194652.873b0bcf.pj@sgi.com>
Date: Wed, 3 Oct 2007 19:46:52 -0700
From: Paul Jackson <pj@....com>
To: "Paul Menage" <menage@...gle.com>
Cc: akpm@...ux-foundation.org, balbir@...ux.vnet.ibm.com,
serue@...ibm.com, clg@...ibm.com, ebiederm@...ssion.com,
xemul@...nvz.org, rientjes@...gle.com, svaidy@...ux.vnet.ibm.com,
nickpiggin@...oo.com.au, a.p.zijlstra@...llo.nl,
containers@...ts.osdl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 03/33] task containersv11 add tasks file interface
> > - There are many instances of the local variable 'cont', referring
> > to a struct cgroup pointer. I presume the spelling 'cont' is a
> > holdover from the time when we called these containers.
>
> Yes, and since cgroup is short for "control group", "cont" still
> seemed like a reasonable abbreviation. (And made the automatic
> renaming much simpler).
The following will change all 'cont' words to your choice (I doubt
you want to use 'XXXX' as I did here) in cgroup.c:
sed -i -r 's/(\W|^)cont(\W|$)/\1XXXX\2/g' kernel/cgroup.c
I can't say for sure, but I suspect that if cgroups had always
been cgroups (short for control groups), then these local 'cont'
variables would have a different name. One can often, as in this
case, find some justification for most any name. The question is
which name is most quickly and easily understood.
... yes ... I'm a stickler for names ... sorry.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@....com> 1.925.600.0401
-
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