From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Traversing Runqueu - CFS
Date: Thu, 13 Jan 2011 12:40:53 +0700 [thread overview]
Message-ID: <AANLkTikR17ez9HD0NcsRQtJ4jt+dbrk5TMhktEgqzBk9@mail.gmail.com> (raw)
In-Reply-To: <BAY146-w11F4078F82ADAAE2773476BCF00@phx.gbl>
Hi Jestin...
On Thu, Jan 13, 2011 at 08:34, Jestin Joy <jestinjoy@hotmail.com> wrote:
> Hi,
>
> ??? Looking for a way to traverse the runqueue, so that I could get the
> contents of the runqueue. Initial reading tells that sched.h has ched_entity
> structure, which holds some of the data for it, like the
>
> struct rb_node??? ??? run_node;
I think, for simple traversing, you could just use for_each_process,
unless you wanna find out something related to the rb tree. And, with
my limited knowledge, rbtree.h doesn't include any traversing
function.
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
prev parent reply other threads:[~2011-01-13 5:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 1:34 Traversing Runqueu - CFS Jestin Joy
2011-01-13 5:40 ` Mulyadi Santosa [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=AANLkTikR17ez9HD0NcsRQtJ4jt+dbrk5TMhktEgqzBk9@mail.gmail.com \
--to=mulyadi.santosa@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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;
as well as URLs for NNTP newsgroup(s).