From: Andi Kleen <andi@firstfloor.org>
To: "George Spelvin" <linux@horizon.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to measure enable_kernel_fpu overhead?
Date: Sat, 04 Jun 2011 13:17:43 -0700 [thread overview]
Message-ID: <m2pqmts654.fsf@firstfloor.org> (raw)
In-Reply-To: <20110603172652.11807.qmail@science.horizon.com> (George Spelvin's message of "3 Jun 2011 13:26:52 -0400")
"George Spelvin" <linux@horizon.com> writes:
>
> Does anyone have any suggestions?
This seems to clever for its own good. Even if you come up with some
number on one CPU it could be completely different on another.
I would suggest KISS.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2011-06-04 20:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 17:26 How to measure enable_kernel_fpu overhead? George Spelvin
2011-06-04 20:17 ` Andi Kleen [this message]
2011-06-05 0:23 ` George Spelvin
2011-06-05 0:31 ` Andi Kleen
2011-06-05 1:50 ` George Spelvin
[not found] <BANLkTimyCodUvBUEVUJcb8TALF5x3H3UEQ@mail.gmail.com>
2011-06-05 15:51 ` George Spelvin
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=m2pqmts654.fsf@firstfloor.org \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@horizon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox