mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: "Raúl Baena" <raul_baena@ya.com>
Cc: jonathan@jonmasters.org, linux-kernel@vger.kernel.org
Subject: Re: Doubt about scheduler
Date: Mon, 06 Mar 2006 00:30:11 +1100	[thread overview]
Message-ID: <440AE7E3.4060500@yahoo.com.au> (raw)
In-Reply-To: <440AE3F3.3090404@ya.com>

Raúl Baena wrote:
> Thank you very much Jon. But I think I haven´t explained very well.
> 
> I know that now the prio_array and runqueues structs aren´t accesible 
> for modules, but in the 2.6.5 version they were. I would like to know 
> the reason, why before they were accesible and now they don´t? If you 
> could answer me, it would be great.

I don't remember them being available in 2.6.5... but as to why they
aren't available now: it is much cleaner this way. It even benefits
you because now nobody will break your module when they change the
data structure.

> 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

-- 
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 

  reply	other threads:[~2006-03-05 13: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 [this message]
2006-03-05 15:21       ` Raúl Baena
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=440AE7E3.4060500@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=jonathan@jonmasters.org \
    --cc=linux-kernel@vger.kernel.org \
    --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

Powered by JetHome