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: linux-kernel@vger.kernel.org
Subject: Re: Doubt about scheduler
Date: Sun, 5 Mar 2006 21:27:21 +0000	[thread overview]
Message-ID: <35fb2e590603051327u5dd4740eod7cc3b6afe583252@mail.gmail.com> (raw)
In-Reply-To: <440AE3F3.3090404@ya.com>

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

> Thank you very much Jon. But I think I haven´t explained very well.

No, you did. Perhaps I wasn't terse enough in my reply :-)

> 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?

Because it's a /bad idea/ to screw around with these. That's why. I
was trying to say that nicely before - it's cleaner and safer if the
scheduler is the only thing playing there as it's the only thing with
a bona fide need.

I'm not trying to be offensive at all - by all means make your own
kernel, perhaps with an exported version of these structure or
introduce your own API for tinkering with them. But just don't
necessarily expect everyone else to jump at it :-)

Jon.

      parent reply	other threads:[~2006-03-05 21:27 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
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 [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=35fb2e590603051327u5dd4740eod7cc3b6afe583252@mail.gmail.com \
    --to=jonmasters@gmail.com \
    --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

all inboxes | Powered by JetHome®