| To: | Stephen Hemminger <shemminger@xxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH] unclamp tcp receive window if doing dynamic receive sizing |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Mon, 7 Jun 2004 16:17:41 -0700 |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <20040607133056.5ab9e72d@dell_ss3.pdx.osdl.net> |
| References: | <20040607133056.5ab9e72d@dell_ss3.pdx.osdl.net> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Mon, 7 Jun 2004 13:30:56 -0700 Stephen Hemminger <shemminger@xxxxxxxx> wrote: > When running tests over higher speed links, the new 2.6 Dynamic Receiver > Sizing > code doesn't increase the window large enough. The problem is that the window > clamp restricts the allowed window to the socket receive buffer size (85k) > > Easiest fix is to not restrict window clamp if we want to dynamic receiver > stuff. > This is what web100 did. > > Thanks to John Heffner for finding this. This turns off all tcp_app_win semantics, are you sure that tcp_app_win makes no sense when doing dynamic receive buffer sizing? I think we should still factor it in, perhaps dynamically, during rcvbuf growth. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: in-driver QoS, Andi Kleen |
|---|---|
| Next by Date: | Re: [RFC] ethtool semantics, Marc Herbert |
| Previous by Thread: | [PATCH] unclamp tcp receive window if doing dynamic receive sizing, Stephen Hemminger |
| Next by Thread: | Re: [PATCH] unclamp tcp receive window if doing dynamic receive sizing, David S. Miller |
| Indexes: | [Date] [Thread] [Top] [All Lists] |