All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Raúl Baena" <raul_baena@ya.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Doubt about scheduler
Date: Sun, 05 Mar 2006 16:21:05 +0100	[thread overview]
Message-ID: <440B01E1.8080102@ya.com> (raw)
In-Reply-To: <440AE7E3.4060500@yahoo.com.au>


>> I could to write the reason in my university job. (In Spain we have 
>> to make a final degree job, and mine is about modules in linux (I 
>> chose this), I would like to show information of the new scheduler, a 
>> scheduler monitor, and these fields are indispensable for me)
>
>
> If your task is about modules in Linux, then I don't see how that
> involves the scheduler at all?
>
> On the other hand, if you want a scheduler monitor then I can't see
> why it would be appropriate to implement as a module (we have schedstats,
> which you can read from a userspace program or daemon).
>
> Nick
>
Thank you very much Nick.

My task is free, I can do everything that I want that involves modules, 
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. 
This is the reason because I have to make a module althought ( according 
with your recomendations, recomendations of a person who knows 
infinitely much than me) probably would be better to make another thing.

At any rate, I will search "schedstats" references, in case it was usefull.

Thank all of you very much again , with your help I hope to be able to 
make a good final degree job.

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

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-02 20:40 Doubt about scheduler 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 [this message]
2006-03-05 21:30         ` Jon Masters
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=440B01E1.8080102@ya.com \
    --to=raul_baena@ya.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    /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.