From: Michal Soltys <soltys@ziu.info>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: netdev@vger.kernel.org
Subject: Re: r8169 (+others ?) and note_interrupt performance hit on 2.6.30.x
Date: Sun, 26 Jul 2009 12:50:28 +0200 [thread overview]
Message-ID: <4A6C34F4.4060709@ziu.info> (raw)
In-Reply-To: <20090726091803.GA28374@electric-eye.fr.zoreil.com>
Francois Romieu wrote:
> Michal Soltys <soltys@ziu.info> :
> [...]
>> I did some quick oprofile, and noticed one new call -
>> note_interrupt - which wasn't present in the earlier kernel,
>> taking majority of the cpu time, relatively to the rest, e.g.:
>>
>> samples cum. samples % cum. % symbol name
>> 90984 90984 42.8695 42.8695 note_interrupt
>
> May be some screaming irq.
>
> Do your /proc/interrupts look the same with both kernels ?
>
Yes - nothing unusual there, and amount of interrupts on the interface
corresponds to pps. The rest is roughly idle.
next prev parent reply other threads:[~2009-07-26 10:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-26 0:31 r8169 (+others ?) and note_interrupt performance hit on 2.6.30.x Michal Soltys
2009-07-26 9:18 ` Francois Romieu
2009-07-26 10:50 ` Michal Soltys [this message]
2009-07-26 18:43 ` Michal Soltys
2009-07-27 21:52 ` Jarek Poplawski
2009-08-05 18:54 ` Michal Soltys
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=4A6C34F4.4060709@ziu.info \
--to=soltys@ziu.info \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.