linux-kernel - Re: [RFC][PATCH] Per container statistics

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: <46495FD4.9080607@linux.vnet.ibm.com>
Date:	Tue, 15 May 2007 12:53:00 +0530
From:	Balbir Singh <balbir@...ux.vnet.ibm.com>
To:	Kirill Korotaev <dev@...ru>
CC:	Paul Menage <menage@...gle.com>, vatsa@...ibm.com,
	linux-kernel@...r.kernel.org, xemul@...ru,
	akpm@...ux-foundation.org, devel@...nvz.org
Subject: Re: [RFC][PATCH] Per container statistics

Kirill Korotaev wrote:
> oh, please no... Andrew, this loop can be very very long when having > 10,000 tasks on the machine...
> we have had enough such issues in OpenVZ and just don't want to come through this again.
> Also sum of RUNNING + UNINTERRUPTIBLE is required for per-container loadavg calculations.
> 

Hi, Kirill,

I've asked Paul Menage to help us with this scenario by adding a per-container task list.
Would you be ok, if we walked the per-container task list. We could further optimize
the routine by adding

1. A container id (avoid parsing file paths to uniquely identify a container)
2. If we cannot do (1), then cache container paths

The other option is of-course what Pavel posted, but I think the amortized cost of tracking
task state at the time of task state change or looping over tasks on demand should be the
same.

Do you agree in general with containerstats? How we build (walk the task list or at the
time of task state change) is flexible with containerstats.

Thanks for your comments!

-- 
	Warm Regards,
	Balbir Singh
	Linux Technology Center
	IBM, ISTL
-
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/