All of lore.kernel.org
 help / color / mirror / Atom feed
From: WANG Cong <xiyou.wangcong@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Compile kernel for various times and problem of too long time consuming
Date: Mon, 8 Aug 2011 09:48:05 +0000 (UTC)	[thread overview]
Message-ID: <j1obck$554$1@dough.gmane.org> (raw)
In-Reply-To: CAC-yRPQS7r-MMh13Y1m0O+oLBu2OmQqmXS8iHFtCOS9YwrxrkA@mail.gmail.com

On Sun, 07 Aug 2011 21:39:12 +0430, Amirali Shambayati wrote:

> Hi all,
> Since I want to evaluate performance improvements by changing just one
> file in kernel(noop-iosched) and compiling kernel is too much
> time-consuming, I want to know that if I compile kernel for more than
> one time, does it take similar time to first time?
> 
> I use following commands. If I don't use "make-kpkg clean" for next
> times, does it just compile the files which have been modified or it
> compile whole kernel package again?
> 
> make-kpkg clean
> fakeroot make-kpkg --initrd --append-to-version=-some-string-here
> kernel-image kernel-headers

Don't run 'make-kpkg clean', and try to use ccache,
make CC='ccache gcc'


  parent reply	other threads:[~2011-08-08  9:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-07 17:09 Compile kernel for various times and problem of too long time consuming Amirali Shambayati
2011-08-07 17:09 ` Amirali Shambayati
2011-08-07 17:32 ` Amirali Shambayati
2011-08-07 17:32   ` Amirali Shambayati
2011-08-07 19:40   ` Mulyadi Santosa
2011-08-07 18:03 ` Randy Dunlap
2011-08-07 18:04   ` Randy Dunlap
2011-08-07 19:48   ` Amirali Shambayati
2011-08-07 19:48     ` Amirali Shambayati
2011-08-07 19:53     ` Stratos Psomadakis
2011-08-07 20:00       ` Stratos Psomadakis
2011-08-07 19:54     ` Randy Dunlap
2011-08-07 20:02       ` Randy Dunlap
2011-08-08  9:48 ` WANG Cong [this message]
2011-08-08 10:55 ` Javier Martinez Canillas
2011-08-08 10:55   ` Javier Martinez Canillas
2011-08-08 11:12   ` Prateek Sharma

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='j1obck$554$1@dough.gmane.org' \
    --to=xiyou.wangcong@gmail.com \
    --cc=kernelnewbies@kernelnewbies.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.