| To: | "David S. Miller" <davem@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: RFC: NAPI packet weighting patch |
| From: | Jon Mason <jdmason@xxxxxxxxxx> |
| Date: | Fri, 3 Jun 2005 16:12:10 -0500 |
| Cc: | hadi@xxxxxxxxxx, mitch.a.williams@xxxxxxxxx, john.ronciak@xxxxxxxxx, shemminger@xxxxxxxx, netdev@xxxxxxxxxxx, Robert.Olsson@xxxxxxxxxxx, ganesh.venkatesan@xxxxxxxxx, jesse.brandeburg@xxxxxxxxx |
| In-reply-to: | <20050603.133133.38710501.davem@xxxxxxxxxxxxx> |
| Organization: | IBM |
| References: | <20050603.120126.41874584.davem@xxxxxxxxxxxxx> <1117828771.6071.77.camel@xxxxxxxxxxxxxxxxxxxxx> <20050603.133133.38710501.davem@xxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | KMail/1.7.2 |
On Friday 03 June 2005 03:31 pm, David S. Miller wrote: > From: jamal <hadi@xxxxxxxxxx> > Date: Fri, 03 Jun 2005 15:59:31 -0400 > > > But one that you could validate by putting proper hooks. As an example, > > try to restore a descriptor every time you pick one - for an example of > > this look at the sb1250 driver. > > Yes, this in my mind is exactly the problem. TG3 does this > properly, as do several other drivers. > > You should never defer RX buffer replenishment, you should > always do it as you grab packets off of the ring. You will > starve the chip otherwise. e1000 isn't the only driver to do things this way. r8169, via-velocity, dl2k, and skge (and I'm sure many more). Might be nice to perform a driver audit to see what drivers do this. |
| Previous by Date: | Re: RFC: NAPI packet weighting patch, Edgar E Iglesias |
|---|---|
| Next by Date: | [PATCHSET] PKT_SCHED related fixes and a meta ematch completion, Thomas Graf |
| Previous by Thread: | Re: RFC: NAPI packet weighting patch, David S. Miller |
| Next by Thread: | Re: RFC: NAPI packet weighting patch, David S. Miller |
| Indexes: | [Date] [Thread] [Top] [All Lists] |