| To: | Stephen Hemminger <shemminger@xxxxxxxx> |
|---|---|
| Subject: | Re: netif_rx packet dumping |
| From: | jamal <hadi@xxxxxxxxxx> |
| Date: | 03 Mar 2005 16:24:25 -0500 |
| Cc: | "David S. Miller" <davem@xxxxxxxxxxxxx>, rhee@xxxxxxxxxxxx, jheffner@xxxxxxx, Yee-Ting.Li@xxxxxxx, baruch@xxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <20050303132143.7eef517c@dxpl.pdx.osdl.net> |
| Organization: | jamalopolous |
| References: | <20050303123811.4d934249@dxpl.pdx.osdl.net> <20050303125556.6850cfe5.davem@davemloft.net> <1109884688.1090.282.camel@jzny.localdomain> <20050303132143.7eef517c@dxpl.pdx.osdl.net> |
| Reply-to: | hadi@xxxxxxxxxx |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Thu, 2005-03-03 at 16:21, Stephen Hemminger wrote: > My plan is to keep netif_max_backlog but bump it up to something bigger > by default. Maybe even autosize it based on memory available. But > get rid of the "dump till empty" behaviour that screws over TCP. Ok, this does sound more reasonable. Out of curiosity, are packets being dropped at the socket queue? Why is "dump till empty" behaviour screwing over TCP. cheers, jamal |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: netif_rx packet dumping, Stephen Hemminger |
|---|---|
| Next by Date: | Re: netif_rx packet dumping, Baruch Even |
| Previous by Thread: | Re: netif_rx packet dumping, Stephen Hemminger |
| Next by Thread: | Re: netif_rx packet dumping, David S. Miller |
| Indexes: | [Date] [Thread] [Top] [All Lists] |