| To: | Jeff Garzik <jgarzik@xxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: New net features for added performance |
| From: | Andi Kleen <ak@xxxxxxx> |
| Date: | Sun, 25 Feb 2001 01:16:40 +0100 |
| Cc: | Andi Kleen <ak@xxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <3A984E1A.DF67E730@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Sat, Feb 24, 2001 at 07:13:14PM -0500 |
| References: | <3A9842DC.B42ECD7A@mandrakesoft.com> <oupsnl3k5gs.fsf@pigdrop.muc.suse.de> <3A984BDA.190B4D8E@mandrakesoft.com> <3A984E1A.DF67E730@mandrakesoft.com> |
| Sender: | owner-netdev@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5i |
On Sat, Feb 24, 2001 at 07:13:14PM -0500, Jeff Garzik wrote: > Sorry... I should also point out that I was thinking of tulip > architecture and similar architectures, where you have a fixed number of > Skbs allocated at all times, and that number doesn't change for the > lifetime of the driver. > > Clearly not all cases would benefit from skb recycling, but there are a > number of rx-ring-based systems where this would be useful, and (AFAICS) > reduce the work needed to be done by the system, and reduce the amount > of overall DMA traffic by a bit. A simple way to do it currently is just to compare the new skb with the old one. If it is the same, do a shortcut. That should usually work out when the system has enough memory. -Andi |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: New net features for added performance, Andi Kleen |
|---|---|
| Next by Date: | Re: New net features for added performance, Jeremy Jackson |
| Previous by Thread: | Re: New net features for added performance, Andi Kleen |
| Next by Thread: | Re: New net features for added performance, Jeremy Jackson |
| Indexes: | [Date] [Thread] [Top] [All Lists] |