linux-kernel - Re: CGFreak control group visualizer

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: <20091007114854.GI6818@balbir.in.ibm.com>
Date:	Wed, 7 Oct 2009 17:18:54 +0530
From:	Balbir Singh <balbir@...ux.vnet.ibm.com>
To:	Linus Walleij <linus.ml.walleij@...il.com>
Cc:	linux kernel <linux-kernel@...r.kernel.org>,
	Jonathan Corbet <corbet@....net>
Subject: Re: CGFreak control group visualizer

* Linus Walleij <linus.ml.walleij@...il.com> [2009-10-07 13:03:30]:

> 2009/10/7 Balbir Singh <balbir@...ux.vnet.ibm.com>:
> 
> > I looked at the screenshots and they look very interesting. Would it
> > take a lot of effort to extend it to track other controllers like
> > memory, network, etc?
> 
> No I don't think that'd be a problem if you can just come up with some
> proper visualization idea.
> 
> Memory can probably be a piechart as well, representing the physical memory
> (I think Matt already has some support for offline-generation of such charts in
> smem but this could be interactive, on-the-fly.)
>

Yeah.. that is a challenge, I tried running the visulation and it
seems to be quite heavy on the CPU and in my case with several
hundreds of process and several threads per process, the output
stopped making sense at some point. I'll play a bit more with it.
 
> Network bandwidth is harder I think because I don't know how these interfaces
> look if you want to measure throughput also (alottment would be easy to draw
> as a pie chart).
> 
> Patches welcome :-)a

:)

> 
> Linus Walleij

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