| To: | herbert@xxxxxxxxxxxxxxxxxxx |
|---|---|
| Subject: | Re: [PATCH] Super TSO v3 |
| From: | "David S. Miller" <davem@xxxxxxxxxxxxx> |
| Date: | Mon, 23 May 2005 19:38:17 -0700 (PDT) |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <20050524023256.GA29242@xxxxxxxxxxxxxxxxxxx> |
| References: | <20050524003208.GA25778@xxxxxxxxxxxxxxxxxxx> <20050523.192917.48530622.davem@xxxxxxxxxxxxx> <20050524023256.GA29242@xxxxxxxxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Date: Tue, 24 May 2005 12:32:57 +1000 > True, the Nagle algorithm itself aims to do something different > from this function. However, the act of turning Nagle off is > an indication that the application wants to minimise the latency > by sending things out ASAP. So we should either respect that > here by not delaying the packets to increase the TSO size, or > we'll need a new socket option to do that for TSO. Sure, we can check tp->nonagle to turn this deferring off. But, I bet there are folks who want traditional Nagle turned off, yet TSO chunking enabled. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] Super TSO v3, Herbert Xu |
|---|---|
| Next by Date: | [XFRM] Call dst_check() with appropriate cookie, YOSHIFUJI Hideaki / 吉藤英明 |
| Previous by Thread: | Re: [PATCH] Super TSO v3, Herbert Xu |
| Next by Thread: | Re: [PATCH] Super TSO v3, Rick Jones |
| Indexes: | [Date] [Thread] [Top] [All Lists] |