From: Arjan van de Ven <arjan@infradead.org>
To: Sharma Sushant <sushant@cs.unm.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Benchmarks
Date: Tue, 03 Jan 2006 22:36:34 +0100 [thread overview]
Message-ID: <1136324194.2869.22.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20060103213244.M41864@webmail.cs.unm.edu>
On Tue, 2006-01-03 at 16:34 -0500, Sharma Sushant wrote:
> Hello everyone,
> If someone make some modifications to kernel code and want to know how much
> overead those modifications has caused, what are the benchmarks that one
> should use to calculate the overhead of the added code.
> please cc the reply to me.
it really depends on what area of the kernel you're changing.. there's
no "golden" benchmark that tests the entire kernel and gives one nice
answer... there are however a lot of smaller benchmarks that test a
portion of the kernel....
next prev parent reply other threads:[~2006-01-03 21:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-03 21:34 Benchmarks Sharma Sushant
2006-01-03 21:36 ` Arjan van de Ven [this message]
2006-01-03 21:39 ` Benchmarks Avishay Traeger
2006-01-03 21:44 ` Benchmarks Jesper Juhl
2006-01-03 22:29 Benchmarks Randy.Dunlap
2006-02-08 20:10 benchmarks Jan Koss
2006-02-08 23:35 ` benchmarks Michal Piotrowski
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=1136324194.2869.22.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sushant@cs.unm.edu \
/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®