From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Raul <raul_baena@ya.com>
Cc: rostedt@goodmis.org, jonathan@jonmasters.org,
nickpiggin@yahoo.com.au, linux-kernel@vger.kernel.org
Subject: Re: Doubt about scheduler
Date: Mon, 6 Mar 2006 07:44:43 -0800 [thread overview]
Message-ID: <20060306074443.fb6b8afb.rdunlap@xenotime.net> (raw)
In-Reply-To: <440BF854.1050201@ya.com>
On Mon, 06 Mar 2006 09:52:36 +0100 Raul wrote:
> Steven Rostedt wrote:
>
> >On Sun, 5 Mar 2006, Jon Masters wrote:
> >
> >
> >
> >>On 3/5/06, Raúl Baena <raul_baena@ya.com> wrote:
> >>
> >>
> >>
> >>>I thought that to make the module about the new O(k) scheduler would be
> >>>a good idea. I think that it´s not enough for me schedstats, because I
> >>>want to make a visual scheduler, I mean, using GTK+ , a module and
> >>>something else to make a visual scheduler monitor, how the tasks move
> >>>between "active" and "expired", where the task are in prio_array with
> >>>the bitmap fields...this module isn´t usefull, only in a didactic way.
> >>>
> >>>
> >>If you're seriously interested in this then cool. Let me know how you get on.
> >>
> >>I looked at hacking something into gtop etc. previously to use
> >>/proc/kcore and pull out task information - I'd certainly like to see
> >>a visual process monitor that could pull all of this stuff out and
> >>display it for educational interest (page tables, vmas, other
> >>resources). But then, it's probably been done - I didn't look to see
> >>what else is out there.
> >>
> >>
> >>
> >
> >Raul, Also take a look at relayfs. It's a fast way to record data in the
> >kernel and pass it back to a userland process. You'll have to patch the
> >kernel as it is said that the data needed is private to sched.c
> >
> >Look into Documentation/filesystems/relayfs.txt
> >
> >relayfs entered the kernel in 2.6.14.
> >
> >-- Steve
> >
> >
> >
> Thank you very much, I'll see it. I'll tell you my progress!!!
note that in recent kernels it has changed to:
config RELAY
bool "Kernel->user space relay support (formerly relayfs)"
help
This option enables support for relay interface support in
certain file systems (such as sysfs, and trivially debugfs).
It is designed to provide an efficient mechanism for tools and
facilities to relay large amounts of data from kernel space to
user space.
---
~Randy
next prev parent reply other threads:[~2006-03-06 15:43 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 [this message]
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=20060306074443.fb6b8afb.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=jonathan@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=raul_baena@ya.com \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®