linux-kernel - Re: [PATCH v2 0/3] distinct load average per-cpuset

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] [day] [month] [year] [list]

Message-ID: <CAFub=KQJu-kD1_oA6=2y7svwixvFTc-g_D3aMkwuARfFx6H4RQ@mail.gmail.com>
Date:	Thu, 18 Jul 2013 13:34:04 +0300
From:	Ozan Çağlayan <ozancag@...il.com>
To:	Andrea Righi <andrea@...terlinux.com>
Cc:	Paul Menage <paul@...lmenage.org>, Ingo Molnar <mingo@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/3] distinct load average per-cpuset

On Sat, Oct 20, 2012 at 10:05 PM, Andrea Righi <andrea@...terlinux.com> wrote:
> Overview
> ~~~~~~~~
> The cpusets subsystem allows to assign a different set of CPUs to a cgroup. A
> typical use case is to split large systems in small CPU/memory partitions and
> isolate certain users/applications in these subsets of the system.
>
> Sometimes, to have a quick overview of the state of each partition, we may be
> interested to get the load average of the CPUs assigned to a particular cpuset,
> rather than the global load average of the system.
>
> Proposed solution
> ~~~~~~~~~~~~~~~~~
> The proposal is to add a new file in the cpuset subsystem to report the load
> average of the CPUs assinged to a particular cpuset cgroup.

Hi,

What is the situation with this patch?


--
Ozan Çağlayan
Research Assistant
Galatasaray University - Computer Engineering Dept.
http://www.ozancaglayan.com
--
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/