From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Linus Walleij <linus.ml.walleij@gmail.com>
Cc: linux kernel <linux-kernel@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: CGFreak control group visualizer
Date: Wed, 7 Oct 2009 17:18:54 +0530 [thread overview]
Message-ID: <20091007114854.GI6818@balbir.in.ibm.com> (raw)
In-Reply-To: <63386a3d0910070403k1d1e6d56xa46d95d2ff448b2a@mail.gmail.com>
* Linus Walleij <linus.ml.walleij@gmail.com> [2009-10-07 13:03:30]:
> 2009/10/7 Balbir Singh <balbir@linux.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
prev parent reply other threads:[~2009-10-07 11:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 21:06 CGFreak control group visualizer Linus Walleij
2009-10-06 23:10 ` Balbir Singh
2009-10-07 11:03 ` Linus Walleij
2009-10-07 11:48 ` Balbir Singh [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091007114854.GI6818@balbir.in.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=corbet@lwn.net \
--cc=linus.ml.walleij@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.