| To: | shemminger@xxxxxxxx |
|---|---|
| Subject: | Re: RFC: NAPI packet weighting patch |
| From: | "David S. Miller" <davem@xxxxxxxxxxxxx> |
| Date: | Tue, 21 Jun 2005 13:20:44 -0700 (PDT) |
| Cc: | mitch.a.williams@xxxxxxxxx, john.ronciak@xxxxxxxxx, mchan@xxxxxxxxxxxx, hadi@xxxxxxxxxx, buytenh@xxxxxxxxxxxxxx, jdmason@xxxxxxxxxx, netdev@xxxxxxxxxxx, Robert.Olsson@xxxxxxxxxxx, ganesh.venkatesan@xxxxxxxxx, jesse.brandeburg@xxxxxxxxx |
| In-reply-to: | <42A5284C.3060808@osdl.org> |
| References: | <468F3FDA28AA87429AD807992E22D07E0450C00B@orsmsx408> <Pine.CYG.4.58.0506061647340.128@mawilli1-desk2.amr.corp.intel.com> <42A5284C.3060808@osdl.org> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
From: Stephen Hemminger <shemminger@xxxxxxxx> Date: Mon, 06 Jun 2005 21:53:32 -0700 > I noticed that the tg3 driver copies packets less than a certain > threshold to a new buffer, but e1000 always passes the big buffer up > the stack. Could this be having an impact? I bet it does, this makes ACK processing a lot more expensive. And it is so much cheaper to just recycle the big buffer back to the chip if you copy to a small buffer, and it warms up the caches for the packet headers as a side effect as well. Actually, it has a _HUGE_ _HUGE_ impact. If you pass the big buffer up, the receiving socket gets charged for the size of the huge buffer, not for just the size of the packet contained within. This makes sockets get overcharged for data reception, and it can cause all kinds of performance problems. I highly recommend that this gets fixed. |
| Previous by Date: | Re: ipw2100: firmware problem, Simon Kelley |
|---|---|
| Next by Date: | Re: [PATCH]: Tigon3 new NAPI locking v2, David S. Miller |
| Previous by Thread: | Re: RFC: NAPI packet weighting patch, P |
| Next by Thread: | Re: RFC: NAPI packet weighting patch, Rick Jones |
| Indexes: | [Date] [Thread] [Top] [All Lists] |