From: "Raúl Baena" <raul_baena@ya.com>
To: Peter Williams <pwil3058@bigpond.net.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Doubt about scheduler
Date: Sun, 05 Mar 2006 23:58:25 +0100 [thread overview]
Message-ID: <440B6D11.9040301@ya.com> (raw)
In-Reply-To: <440B681C.8030403@bigpond.net.au>
Peter Williams escribió:
> SuSE patched their 2.6.5 kernel to make the run queues visible in a
> header file. Perhaps Raul was using a SuSE version of 2.6.5.
Exact!!!! . To be honest, I have the 2.6.12 version to debian, but my
project tutor has this one. And when I argued about my project and I
told him that those fields weren´t accesible, he sent me his sched.h,
and I saw that runqueue and prio_array were accesible in it. I didn´t
think that it was a SUSE patch . Sorry, it's my fault
I have made a litte cheat to be able to see prio_array fields, I have
created a new struct and later with the "array" field of "task_struct" I
have made a cast to my struct. Then I have been able to show these
values, but I don't like this "solution", because I can´t know anything
of tasks in another state ("active" or "expired"), neither which is my
state!! For this reason I would like to know how to get this
information, my project have to be done in June 30 :(.
Thank you very much again for your help, I´m getting a lot of
information about the kernel that I'll be able to use in my report, of
course if you agree.
next prev parent reply other threads:[~2006-03-05 22:58 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
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 [this message]
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=440B6D11.9040301@ya.com \
--to=raul_baena@ya.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pwil3058@bigpond.net.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.