From: Mark Lord <lkml@rtr.ca>
To: kernel coder <lhrkernelcoder@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: increased number of cycles
Date: Sun, 18 Nov 2007 09:39:29 -0500 [thread overview]
Message-ID: <47404EA1.5010902@rtr.ca> (raw)
In-Reply-To: <f69849430711172131j41c21d84y2ac10759eff29eb7@mail.gmail.com>
kernel coder 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.
..
A cache miss ?
next prev parent reply other threads:[~2007-11-18 14:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-18 5:31 increased number of cycles kernel coder
2007-11-18 13:48 ` Wander Winkelhorst
2007-11-18 14:39 ` Mark Lord [this message]
2007-11-20 1:24 ` Arjan van de Ven
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=47404EA1.5010902@rtr.ca \
--to=lkml@rtr.ca \
--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