lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091104081618.GD3560@balbir.in.ibm.com>
Date:	Wed, 4 Nov 2009 13:46:18 +0530
From:	Balbir Singh <balbir@...ux.vnet.ibm.com>
To:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Cc:	libcg-devel <libcg-devel@...ts.sourceforge.net>,
	"menage@...gle.com" <menage@...gle.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	containers@...ts.linux-foundation.org,
	Jan Safranek <jsafrane@...hat.com>,
	Dhaval Giani <dhaval@...ux.vnet.ibm.com>,
	Bharata B Rao <bharata.rao@...ibm.com>
Subject: Re: [RFC] Mount point suggestions for cgroup

* KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com> [2009-11-04 15:40:24]:

> On Wed, 4 Nov 2009 12:00:05 +0530
> Balbir Singh <balbir@...ux.vnet.ibm.com> wrote:
> 
> > Hi, All,
> > 
> > We've been having a discussion as to what would be the right place to
> > mount the cgroup filesystem. Jan has been proactively looking into
> > this. The FHS has no recommendation since cgroup filesystem came in
> > much later.
> > 
> > The options are
> > 
> > 1. /dev/cgroup
> > 2. /cgroup
> > 3. Some place under /sys
> > 
> > The problem with (2) is that it is quite non-standard and pollutes the
> > root directory. (3) requires some basic support to create a directory
> > for cgroup under /sys. (1) seems the most obvious choice since cpusets
> > were mounted under /dev/cpuset, but /dev is controlled by udev.
> > 
> > Given the three choices or any other suggestions, is there a general
> > preference as to where we can mount it? The goal is to standardize
> > the mount point (if possible).
> > 
> > BTW, the mounting is expected to be done using cgconfigparser present
> > in libcgroup.
> > 
> 
> IMHO, even if anywhere is ok to me, the suggestion should includes the fact
>   - Each cgroup subsystem can be mounted independenty from other cgroup.
>   - some cgroup (noop) can be mounted multiple times
> etc...there are some points which is different from /proc or /sys.
> So, we need multiple mount points.
> 
> Then, to say my own not-seriously-considered idea, I vote for
>  - /cgroup/[HierarchyName]/
> rather than /dev/ or /sys or /opt. This sounds straightforward.

The reason I liked /dev/cgroup was because cpusets could be
mounted at /dev/cpuset or /dev/cgroup/cpuset. My concern with /cgroup
is that a ls "/" now becomes larger in size. But I'll take your vote
for it as +1 for /cgroup.

> 
> If /sys,  /sys/cgroup/[HierarchyName] will be candidate. But considering
> users can use arbitarary combination of subsystem, using /sys may require
> much work, I think.
> 

Yes, Agreed.

> Thanks,
> -Kame
> 

-- 
	Balbir
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ