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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 12 May 2010 12:04:08 -0600
From:	"Chris Friesen" <cfriesen@...tel.com>
To:	James Kosin <jkosin@...comgrp.com>
CC:	Dhaval Giani <dhaval.giani@...il.com>,
	Jan Safranek <jsafrane@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	linux-kernel@...r.kernel.org, menage@...gle.com,
	balbir@...ux.vnet.ibm.com, lennart@...ttering.net,
	tglx@...utronix.de
Subject: Re: [PATCH/RFC] Have sane default values for cpusets

On 05/12/2010 11:58 AM, James Kosin wrote:

> Thanks for clearing that up.
> It looks like they are not under the control of the programmer on
> purpose.  It is not outlined in the description of how to use this feature.
> The tasks have to be added separately by an administrator that is
> operating the system to tune performance and to provide resources where
> most needed.

Depending on the type of system, they may or may not be under the
control of the programmer. In an embedded environment, the programmer is
the administrator and generally has control over how the groups are set
up. On a more generic time-sharing system it's likely that the
individual programmer won't have control over the groups.

Something I haven't tried is whether or not it's possible to set
ownership/permissions on subtrees within the cgroup hierarchy to allow
unprivileged users/groups to control their own tasks (basically letting
them prioritize their own jobs without being able to affect anything
else).  Does anyone know if this sort of thing is possible?

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