Messages in this thread |  | | Subject | Re: TCP acking too fast | From | Andi Kleen <> | Date | 14 Oct 2001 11:25:09 +0200 |
| |
In article <20011014.020326.18308527.davem@redhat.com>, "David S. Miller" <davem@redhat.com> writes:
> So, your point is? :-) A sensible sending application, and a sensible > TCP should not being setting PSH every single segment. And we're not > coding up hacks to make the Linux receiver handle this case better. > You'll have much better luck convincing us to implement ECN black hole > workarounds :-)
Ignoring PSH completely on RX would probably not be a worse heuristic than forcing an ACK on it. At least other stacks seem to do fine too without the force-ack-on-psh. I think you added it a long time ago, but I do not remember why you did it; but at least here is an counter example now that may be a good case for a reconsider.
-Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |