mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jon Masters" <jonmasters@gmail.com>
To: "Raúl Baena" <raul_baena@ya.com>
Cc: "Nick Piggin" <nickpiggin@yahoo.com.au>, linux-kernel@vger.kernel.org
Subject: Re: Doubt about scheduler
Date: Sun, 5 Mar 2006 21:30:24 +0000	[thread overview]
Message-ID: <35fb2e590603051330o1dfa6951le3e7f14cda0c0eaa@mail.gmail.com> (raw)
In-Reply-To: <440B01E1.8080102@ya.com>

On 3/5/06, Raúl Baena <raul_baena@ya.com> wrote:

> I thought that to make the module about the new O(k) scheduler would be
> a good idea. I think that it´s not enough for me schedstats, because I
> want to make a visual scheduler, I mean, using GTK+ , a module and
> something else to make a visual scheduler monitor, how the tasks move
> between "active" and "expired", where the task are in prio_array with
> the bitmap fields...this module isn´t usefull, only in a didactic way.

If you're seriously interested in this then cool. Let me know how you get on.

I looked at hacking something into gtop etc. previously to use
/proc/kcore and pull out task information - I'd certainly like to see
a visual process monitor that could pull all of this stuff out and
display it for educational interest (page tables, vmas, other
resources). But then, it's probably been done - I didn't look to see
what else is out there.

Jon.

  reply	other threads:[~2006-03-05 21:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-02 20:40 Raúl Baena
2006-03-04  6:33 ` Jon Masters
2006-03-05 13:13   ` Raúl Baena
2006-03-05 13:30     ` Nick Piggin
2006-03-05 15:21       ` Raúl Baena
2006-03-05 21:30         ` Jon Masters [this message]
2006-03-06  7:29           ` Steven Rostedt
2006-03-06  8:52             ` Raul
2006-03-06 15:44               ` Randy.Dunlap
2006-03-05 21:27       ` Mike Galbraith
2006-03-05 22:37       ` Peter Williams
2006-03-05 22:58         ` Raúl Baena
2006-03-05 21:27     ` Jon Masters

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=35fb2e590603051330o1dfa6951le3e7f14cda0c0eaa@mail.gmail.com \
    --to=jonmasters@gmail.com \
    --cc=jonathan@jonmasters.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=raul_baena@ya.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®