From: Andi Kleen <ak@suse.de>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: Andi Kleen <ak@suse.de>, "David S. Miller" <davem@redhat.com>,
torvalds@transmeta.com, linux-kernel@vger.kernel.org, "Mallick,
Asit K" <asit.k.mallick@intel.com>,
"Saxena, Sunil" <sunil.saxena@intel.com>
Subject: Re: [PATCH] fixes for building kernel using Intel compiler (lmben ch data)
Date: Mon, 28 Oct 2002 15:51:23 +0100 [thread overview]
Message-ID: <20021028155123.A13576@wotan.suse.de> (raw)
In-Reply-To: <F2DBA543B89AD51184B600508B68D4000ECE730A@fmsmsx103.fm.intel.com>
On Mon, Oct 28, 2002 at 06:47:27AM -0800, Nakajima, Jun wrote:
> I don't think people need to use PGO for day-to-day development or
> debugging. Rather, it would be used only for systems deployed for actual
> use. For example, various kernel binaries optimized for particular use, such
> as database, web server, file server, embedded systems, etc, can be
> distributed as RPM (with profile feedback data).
But unless these kernels are 100% bug free it still leaves the mainteance
issues open.
Also is it really that big a win ?
>
> For development we should such profile feedback data to optimize the kernel
> in source code level (i.e by hand). I don't know the data in gcc has any
> clue for that.
likely/unlikely is the clue. In fact it is already overused.
-Andi
P.S.: Your original mail mentioned that the "P4P kernel was instable
with gcc32". Could you elaborate on the instability? We're using
kernels compiled with gcc 3.2 all the time and they work just fine.
next prev parent reply other threads:[~2002-10-28 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-28 14:47 [PATCH] fixes for building kernel using Intel compiler (lmben ch data) Nakajima, Jun
2002-10-28 14:51 ` Andi Kleen [this message]
2002-10-28 15:03 ` Richard B. Johnson
-- strict thread matches above, loose matches on Subject: below --
2002-10-26 2:16 Nakajima, Jun
2002-10-26 6:27 ` Andi Kleen
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=20021028155123.A13576@wotan.suse.de \
--to=ak@suse.de \
--cc=asit.k.mallick@intel.com \
--cc=davem@redhat.com \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sunil.saxena@intel.com \
--cc=torvalds@transmeta.com \
/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.