From: george anzinger <george@mvista.com>
To: Shaya Potter <spotter@cs.columbia.edu>
Cc: "José Luis Domingo López" <jdomingo@internautas.org>,
linux-kernel@vger.kernel.org
Subject: Re: Linux Scheduler and Compilation
Date: Thu, 25 Oct 2001 16:07:10 -0700 [thread overview]
Message-ID: <3BD89B1E.28E4D7DC@mvista.com> (raw)
In-Reply-To: <007501c15d68$94f12c60$8630fdd4@3232424> <20011025203743.B504@dardhal.mired.net> <1004036810.1770.2.camel@zaphod>
Shaya Potter wrote:
>
> On Thu, 2001-10-25 at 16:37, José Luis Domingo López wrote:
> > On Thursday, 25 October 2001, at 18:20:25 +0300,
> > Omer Sever wrote:
> >
> > > I have a project on Linux CPU Scheduler to make it Fair Share
> > > Scheduler.I will make some changes on some files such as sched.c vs...I will
> > > want to see the effect ot the change but recompilation of the kernel takes
> > > about half an hour on my machine.How can I minimize this time?Which part
> > > should I necessarily include in my config file for the kernel to minimize
> > > it?
> > >
> > make is your friend: it will only recompile those files that changed from
> > the last compilation. If you modify some #includes in the code, I believe
> > you will have to also run "make dep" before, to get dependencies right.
>
> Except, as I discovered recently in playing around with the scheduler,
> if you modify sched.h, you basically have to recompile the entire
> kernel, as it seems everything depends on it.
>
> On that note, why is add_to_runqueue() in sched.c and
> del_from_runqueue() in sched.h? del_from_runqueue being the only func I
> was modifying in sched.h (really annoying have to recompile an entire
> kernel multiple times in a vmware vm, albiet thats not a good reason to
> move it, I'm just wondering why they are split in 2 different files)
>
Somewhere back around 2.2.15 (or so) a change was made that has the smp
cpu start up code removing the start up task from the run list. I think
you will find the del_from_runqueue() is only used in this case. It
could have been done in init_idle() in sched.c (in fact the code is
there) but it is also done prior to this call. Sigh...
George
next prev parent reply other threads:[~2001-10-25 23:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-25 20:37 José Luis Domingo López
2001-10-25 15:20 ` Omer Sever
2001-10-25 19:06 ` Shaya Potter
2001-10-25 19:16 ` Richard B. Johnson
2001-10-25 23:07 ` george anzinger [this message]
2001-10-25 21:48 ` J . A . Magallon
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=3BD89B1E.28E4D7DC@mvista.com \
--to=george@mvista.com \
--cc=jdomingo@internautas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=spotter@cs.columbia.edu \
/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®