From: ruben@mrbrklyn.com (Ruben Safir)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Start it again .. Returning the Kernel Writing
Date: Sun, 15 Mar 2015 12:29:47 -0400 [thread overview]
Message-ID: <5505B37B.5050808@mrbrklyn.com> (raw)
Hello
I'm taking a class on operating systems and it includes, happily,
many Linux examples, outlining OS internal structures and algorithms.
I wanted to delve into the Scheduler, particularly the CFS that has
been implemented and to try running and testing things such as what
is outlined here
http://www.embedded.com/design/operating-systems/4371651/Comparing-the-real-time-scheduling-policies-of-the-Linux-kernel-and-an-RTOS-
In order to do this, I need to compile and code the Kernel and
Kernel modules. I've done this many many time in years gone
by, but the current kernel has seemed to have grown even more
than I anticipated. For those who work on the kernel and drivers
everyday, what would you recommend as a best approach to tinker
with the scheduler or even tinker with struct.h entries.
I set up a VM with oracles virtualbox, and even that was new to
me. I used to keep a usb drive to development and rebooting
when I last attempted this.
Ruben
reply other threads:[~2015-03-15 16:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5505B37B.5050808@mrbrklyn.com \
--to=ruben@mrbrklyn.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).