From: David Miller <davem@davemloft.net>
To: andi@firstfloor.org
Cc: jchapman@katalix.com, netdev@vger.kernel.org, auke-jan.h.kok@intel.com
Subject: Re: NAPI poll behavior in various Intel drivers
Date: Sat, 05 Jan 2008 20:15:49 -0800 (PST) [thread overview]
Message-ID: <20080105.201549.184458758.davem@davemloft.net> (raw)
In-Reply-To: <p738x348kpq.fsf@bingen.suse.de>
From: Andi Kleen <andi@firstfloor.org>
Date: Sat, 05 Jan 2008 14:29:05 +0100
> In 2.4 we used to have (haven't checked recently) performance regressions
> with NAPI vs non NAPI (or versus the old BCM vendor driver) on tg3 for
> some workloads that didn't fully fill the link. The theory was always
> that the reason for that was something like the regular switching in
> and out. So I think we saw that problem on tg3 too.
It was because we originally didn't program the HW interrupt
mitigation settings at all when using NAPI, now we do and the problem
is long gone.
next prev parent reply other threads:[~2008-01-06 4:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-04 11:40 NAPI poll behavior in various Intel drivers David Miller
2008-01-04 20:10 ` James Chapman
2008-01-04 21:24 ` David Miller
2008-01-05 0:18 ` James Chapman
2008-01-05 7:25 ` David Miller
2008-01-05 13:29 ` Andi Kleen
2008-01-06 4:15 ` David Miller [this message]
2008-01-07 8:24 ` Jarek Poplawski
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=20080105.201549.184458758.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andi@firstfloor.org \
--cc=auke-jan.h.kok@intel.com \
--cc=jchapman@katalix.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).