mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "George Spelvin" <linux@horizon.com>
To: andi@firstfloor.org
Cc: linux@horizon.com, linux-kernel@vger.kernel.org
Subject: Re: How to measure enable_kernel_fpu overhead?
Date: 4 Jun 2011 20:23:23 -0400	[thread overview]
Message-ID: <20110605002323.16365.qmail@science.horizon.com> (raw)
In-Reply-To: <m2pqmts654.fsf@firstfloor.org>

> 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.

I don't understand.  Do you mean different CPUs of the same SMP system?
That would be really bad...

The whole point is to, like the RAID6 code, benchmark after boot time
so that the numbers reflect the individual hardware instance.

Doing that in a clean maintainable way suitabkle for merging into Linus's
tree is the problem.  If I just needed a one-off rude hack to measure
on my systems, it would be easy.  But that's so obviously not useful
that I didn't bother to mention it.

"Too clever for its own good" would be to keep more statistics, including
confidence intervals, on actual calls, and randomly dispatch requests
to code paths based on the current estimated probabilities of A being
faster than B.

That avoids doing redundant work just for benchmarking, but does entail
quite a lot of bookkeeping overhead.  I'd rather just measure once at boot
(or module load) and be done with it.


Anyway, thanks for thinking about the problem.

  reply	other threads:[~2011-06-05  0:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-03 17:26 George Spelvin
2011-06-04 20:17 ` Andi Kleen
2011-06-05  0:23   ` George Spelvin [this message]
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=20110605002323.16365.qmail@science.horizon.com \
    --to=linux@horizon.com \
    --cc=andi@firstfloor.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 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®