From: Arjan van de Ven <arjan@infradead.org>
To: "kernel coder" <lhrkernelcoder@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: increased number of cycles
Date: Mon, 19 Nov 2007 17:24:18 -0800 [thread overview]
Message-ID: <20071119172418.3894fc25@laptopd505.fenrus.org> (raw)
In-Reply-To: <f69849430711172131j41c21d84y2ac10759eff29eb7@mail.gmail.com>
On Sat, 17 Nov 2007 21:31:25 -0800
"kernel coder" <lhrkernelcoder@gmail.com> wrote:
> hi,
> I'm trying to add some code to netif_receive_skb function in
> dev.c file . The cycles consumed by that code was around 16 cycles on
> Dual Core Opetron machine.I'm working on that code for last 6 months
> now and the consumed cycles have always been around 16 cycles .I don't
> touch any other part of kernel .
>
> But for last 4 days the consumed cycles have suddenly increased to
> around 35 cycles . I'm using RDTSC instruction to profile the
> code.There is no change in code and the kernel version is also the
> same .I am assuming that there must be something wrong with hardware.
note that profiling a section that takes this short with rdtsc is...
not really working well in practice; you're profiling something that's
smaller (or at least roughly the same size) than the cpu's out of order
speculation window, so your rdtsc greatly impacts what is actually
happening in the code.
as for the change... 16->35 cycles can well be a code or data alignment
change or even a branch misprediction due to some minor code generation
issue.... you're looking at a small microscopic part of the universe
after all, the butterfly in the pacific WILL influence you ;-)
--
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
prev parent reply other threads:[~2007-11-20 1:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-18 5:31 kernel coder
2007-11-18 13:48 ` Wander Winkelhorst
2007-11-18 14:39 ` Mark Lord
2007-11-20 1:24 ` Arjan van de Ven [this message]
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=20071119172418.3894fc25@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=lhrkernelcoder@gmail.com \
--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®