[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3191E98898F04B88AE6C7E944DC28DA4@realtek.com.tw>
Date: Tue, 3 May 2011 19:59:05 +0800
From: hayeswang <hayeswang@...ltek.com>
To: 'Chris Friesen' <chris.friesen@...band.com>,
'John Lumby' <johnlumby@...mail.com>
CC: 'Francois Romieu' <romieu@...zoreil.com>, <netdev@...r.kernel.org>,
'Ben Hutchings' <bhutchings@...arflare.com>
Subject: RE: r8169 : always copying the rx buffer to new skb
> -----Original Message-----
> From: Chris Friesen [mailto:chris.friesen@...band.com]
> Sent: Tuesday, May 03, 2011 3:04 AM
> To: John Lumby
> Cc: Francois Romieu; netdev@...r.kernel.org; Ben Hutchings; nic_swsd
> Subject: Re: r8169 : always copying the rx buffer to new skb
>
> 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.
>
Yes, please refer to the register 0xE2 of datasheet. And the time is influenced
by the register 0xE0.
Best Regards,
Hayes
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists