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:	Sat, 25 Oct 2008 08:43:53 -0700
From:	"Paul Menage" <menage@...gle.com>
To:	"Dong-Jae Kang" <baramsori72@...il.com>
Cc:	"Matthew Garrett" <mjg@...hat.com>, balbir@...ux.vnet.ibm.com,
	xen-devel@...ts.xensource.com,
	containers@...ts.linux-foundation.org,
	linux-kernel@...r.kernel.org,
	virtualization@...ts.linux-foundation.org, dm-devel@...hat.com,
	corsetproject@...glegroups.com,
	"Vaidyanathan Srinivasan" <svaidy@...ux.vnet.ibm.com>
Subject: Re: [Question] power management related with cgroup based resource management

On Sat, Oct 25, 2008 at 1:05 AM, Dong-Jae Kang <baramsori72@...il.com> wrote:
> Thank you for your positive opinion about my question
>
> I also hope cgroup framework has good point related with power management
> I think I need more re-consideration for it. ^^
>
> How do you think about cgroup based management of new HW devices, for
> example, SSD, NVRAM and so on.
> Is there any requirement for it ?
> and is there any required work for it?
> I didn't seriously consider  about that until now.^^ so I don't have cool idea
> but, I think it is worthy to find new domain to be applied by existing
> technology

Control Groups is just a framework for associating state with
(user-created) groups of processes. So if you have a problem to solve
that involves tracking state for different processes, or applying
different behaviour to groups of processes based on that group's
state, then cgroups may well be an appropriate tool.

In the case you mention (management of new devices) that's already
somewhat covered by the existing device isolation subsystem - you can
create a cgroup that has (or doesn't have) access to particular HW
devices.

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ