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: Sat, 4 Mar 2006 06:33:51 +0000 [thread overview]
Message-ID: <35fb2e590603032233i7302162do553ba61674cc8e50@mail.gmail.com> (raw)
In-Reply-To: <4407584A.60301@ya.com>
On 3/2/06, Raúl Baena <raul_baena@ya.com> wrote:
> Hello!!!, I´m a student of computer science and I´m doing my final
> degree job in linux. It is about "linux kernel modules" , I have to know
> some things of the scheduler. The runqueue struct, and so on. The
> problem is that in the last linux kernel version in the "sched.h" isn´t
> defined these structs (prio_array, runqueue...), and I cann´t access to
> runqueue or prio_array fields. I know that in the 2.6.5 kernel version
> these fields were accessible and now don´t, could you tell me what is
> the reason please?
Deliberately, these aren't available outside of the scheduler so that
they can't be played with. Much as things like the symbol table aren't
exported to modules, some things in the kernel aren't even available
to other parts of the core kernel :-)
> I think that I´m going to do it (the module) in the 2.6.5 kernel
> version and will try to explain why, and for this I need your help.
If you really need to play with this stuff, then why not just make
your own kernel tree with this hacked up in the scheduler code itself?
If it's just for you, then that'll work fine. If you would explain
what it is that you need to do, then someone might be able to offer
you advice on the general direction to take - see also
http://www.kernelnewbies.org/
Jon.
next prev parent reply other threads:[~2006-03-04 6:33 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 [this message]
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
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=35fb2e590603032233i7302162do553ba61674cc8e50@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®