| |||||||||||||
Essential, but not the first lineEssential, but not the first linePosted Sep 22, 2011 17:20 UTC (Thu) by nix (subscriber, #2304)In reply to: Essential, but not the first line by cmccabe Parent article: LPC: An update on bufferbloat
I still feel like the right solution is to have the application set a flag in the header somewhere. The application is the one who knows. Just to take your example, the ssh does know whether the input it's getting is coming from a tty (interactive) or a file that's been catted to it (non-interactive). And scp should probably always be non-interactive. You can't deduce this kind of information at a lower layer, because only the application knows.And SSH can do just this: if DISPLAY is unset and SSH is running without a terminal, it sets the QoS bits for a bulk transfer: otherwise, it sets them for an interactive transfer. Unfortunately scp doesn't unset DISPLAY, so if you run scp from inside an X session I suspect it always gets incorrectly marked as interactive... but that's a small thing.
(Log in to post comments)
Essential, but not the first line Posted Sep 23, 2011 6:44 UTC (Fri) by salimma (subscriber, #34460) [Link]
Can't you do "DISPLAY= scp ..." ?
Essential, but not the first line Posted Sep 23, 2011 10:57 UTC (Fri) by nix (subscriber, #2304) [Link]
Yes, but my point is that you shouldn't have to. scp should pass in "-o IPQoS throughput" by default. (Speaking as someone who, er, hasn't written the patch to make it do so.)
|
|||||||||||||