From: Chris Friesen <chris.friesen@genband•com>
To: John Lumby <johnlumby@hotmail•com>
Cc: Francois Romieu <romieu@fr•zoreil.com>,
netdev@vger•kernel.org, Ben Hutchings <bhutchings@solarflare•com>,
nic_swsd@realtek•com
Subject: Re: r8169 : always copying the rx buffer to new skb
Date: Mon, 02 May 2011 13:04:19 -0600 [thread overview]
Message-ID: <4DBF0033.2070804@genband.com> (raw)
In-Reply-To: <4DB77D03.9070507@hotmail.com>
On 04/26/2011 08:18 PM, John Lumby wrote:
> So - question :
> is there any way, when returning from rtl8169_poll, to tell napi
> something like :
> " finish this interrupt context and let something else run on this CPU
> (always CPU0 on my machine) BUT reschedule another napi poll on this
> same device at some time after that "
Does the hardware support any options for interrupt mitigation? I've
used some devices where you can specify a minimum time between
interrupts such that even if NAPI re-enabled interrupts and there were
packets waiting the hardware would wait a certain time before raising a
new interrupt.
Chris
--
Chris Friesen
Software Developer
GENBAND
chris.friesen@genband•com
www.genband.com
next prev parent reply other threads:[~2011-05-02 19:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 17:08 r8169 : always copying the rx buffer to new skb John Lumby
2011-04-18 17:27 ` Ben Hutchings
2011-04-18 21:26 ` John Lumby
2011-04-20 19:13 ` Francois Romieu
2011-04-21 3:41 ` John Lumby
2011-04-21 3:52 ` John Lumby
2011-04-27 2:18 ` John Lumby
2011-04-27 3:57 ` Eric Dumazet
2011-04-27 20:35 ` Francois Romieu
2011-04-29 1:55 ` John Lumby
2011-04-29 4:54 ` Eric Dumazet
2011-05-02 19:04 ` Chris Friesen [this message]
2011-05-03 11:59 ` hayeswang
2011-04-18 18:21 ` Francois Romieu
-- strict thread matches above, loose matches on Subject: below --
2011-06-27 22:54 John Lumby
2011-06-28 7:55 ` Francois Romieu
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=4DBF0033.2070804@genband.com \
--to=chris.friesen@genband$(echo .)com \
--cc=bhutchings@solarflare$(echo .)com \
--cc=johnlumby@hotmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nic_swsd@realtek$(echo .)com \
--cc=romieu@fr$(echo .)zoreil.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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