| To: | Stephen Hemminger <shemminger@xxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH] fix tcp_default_win_scale. |
| From: | John Heffner <jheffner@xxxxxxx> |
| Date: | Wed, 7 Jul 2004 15:41:13 -0400 (EDT) |
| Cc: | "David S. Miller" <davem@xxxxxxxxxx>, bert hubert <ahu@xxxxxxx>, <jamie@xxxxxxxxxxxxx>, <netdev@xxxxxxxxxxx>, <linux-net@xxxxxxxxxxxxxxx>, <linux-kernel@xxxxxxxxxxxxxxx> |
| In-reply-to: | <20040707110653.7c49bef1@dell_ss3.pdx.osdl.net> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Wed, 7 Jul 2004, Stephen Hemminger wrote: > I do not argue with that the correct thing to do is to use window scaling > and find/fix the poor sop's stuck behind busted networks. > > But: isn't it better to have just one sysctl parameter set (tcp_rmem) > and set the window scale as needed rather than increasing the already > bewildering array of dials and knobs? I can't see why it would be > advantageous > to set a window scale of 7 if the largest possible window ever offered > is limited to a smaller value? I personally agree with this. One can imagine cases where it would be useful to have a control on window scale, but the added complexity is probably not worth it. -John |
| Previous by Date: | Re: [PATCH] fix tcp_default_win_scale., bert hubert |
|---|---|
| Next by Date: | Re: [PATCH] mark CSZ scheduler as broken, bert hubert |
| Previous by Thread: | Re: [PATCH] fix tcp_default_win_scale., bert hubert |
| Next by Thread: | Re: [PATCH] fix tcp_default_win_scale., David S. Miller |
| Indexes: | [Date] [Thread] [Top] [All Lists] |