From: Shaya Potter <spotter@cs.columbia.edu>
To: "José Luis Domingo López" <jdomingo@internautas.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux Scheduler and Compilation
Date: 25 Oct 2001 15:06:49 -0400 [thread overview]
Message-ID: <1004036810.1770.2.camel@zaphod> (raw)
In-Reply-To: <20011025203743.B504@dardhal.mired.net>
In-Reply-To: <007501c15d68$94f12c60$8630fdd4@3232424> <20011025203743.B504@dardhal.mired.net>
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)
thanks,
shaya
next prev parent reply other threads:[~2001-10-25 19:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-25 15:20 Linux Scheduler and Compilation Omer Sever
2001-10-25 20:37 ` José Luis Domingo López
2001-10-25 19:06 ` Shaya Potter [this message]
2001-10-25 19:16 ` Richard B. Johnson
2001-10-25 23:07 ` george anzinger
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=1004036810.1770.2.camel@zaphod \
--to=spotter@cs.columbia.edu \
--cc=jdomingo@internautas.org \
--cc=linux-kernel@vger.kernel.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 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.