linux-kernel - Re: [PATCH] cgroupfs: create /sys/fs/cgroup to mount cgroupfs on

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]

Date:	Thu, 22 Jul 2010 11:44:50 -0700
From:	Paul Menage <menage@...gle.com>
To:	Greg KH <gregkh@...e.de>
Cc:	Li Zefan <lizf@...fujitsu.com>,
	Lennart Poettering <lennart@...ttering.net>,
	Kay Sievers <kay.sievers@...y.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	Ben Blum <bblum@...rew.cmu.edu>,
	containers@...ts.linux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] cgroupfs: create /sys/fs/cgroup to mount cgroupfs on

On Thu, Jul 22, 2010 at 11:36 AM, Greg KH <gregkh@...e.de> wrote:
>
> Really?  I see systems mounting it at /cgroups/ in the filesystem today.

Sure, it *can* be mounted as a single instance, but you then lose
flexibility. E.g. at Google we want to have a different hierarchy for
the CPU subsystem (with the tree grouped according to
latency-sensitive versus batch, etc) and memory (grouped according to
what jobs are sharing memory with each other).

> Where are you expecting it to be mounted at?

I have no particular expectation. (At Google we're actually using
/dev/cgroup/* but that's just for historical reasons, from
/dev/cpuset). Under /sys/fs/cgroup sounds reasonable, but you'd want
people to have the ability to manually create subdirs in there for
separate mount points.

Paul
--
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/