[PATCH] Added NoDelay config option and nodelay subsystem option

Nicolas Williams Nicolas.Williams at ubsw.com
Tue Jan 29 04:23:21 EST 2002


On Mon, Jan 28, 2002 at 05:49:17PM +0100, Markus Friedl wrote:
> On Mon, Jan 28, 2002 at 11:33:57AM -0500, Nicolas Williams wrote:
> > TCP_NODELAY is a socket option
> 
> i know.

I figured as much! :) :)

> > and so applies to all of an SSH
> > connection, not to a specific channel.
> 
> wrong, you have to consider each channel endpoint, e.g.
> for tcp forwarding.

Yes, but a single global SSHv2 request will do. I don't see why it has
to be a channel request.

Or are you thinking that, if you have a connection with 3 channels, one
of which needs TCP_NODELAY, and then that channel is closed, both
parties should immediately unset TCP_NODELAY?

But if the client has control over whether the server has TCP_NODELAY
on, then the client can keep track of when to turn Nagle on and off
using as finely or coarsely tuned heuristic as it wants (or as it's told
by the user).

> > Or do you think that the protocol should have a per-channel Nagle-like
> > option at the SSHv2 transport layer?
> 
> no.

Ok.

Nico
--
-DISCLAIMER: an automatically appended disclaimer may follow. By posting-
-to a public e-mail mailing list I hereby grant permission to distribute-
-and copy this message.-

Visit our website at http://www.ubswarburg.com

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.




More information about the openssh-unix-dev mailing list