Hi Michael,
Long story short, I'm chasing a performance issue on linux
implementation and I think that TLR is the right fix for it. The receive
operation is way more expensive than transmit and this causes its buffer
to fill up, up to reach 0 window situation. Then, as the RFC allows,
sender keeps sending 1 data chunk at a time, as a probe for possible
unnoticed window updates due to SACK loss. But if the peer couldn't free
any window in time, it will drop that chunk, and will cause a RTO.
I'm not seeing anything in the specs that would prevent this situation
other than a TLR would do. Or I missed it?
On TLR, the most updated info I could find, is already (recently)
expired and archived:
https://datatracker.ietf.org/doc/draft-nielsen-tsvwg-sctp-tlr/
I could find Karen's email
https://www.ietf.org/mail-archive/web/tsvwg/current/msg13703.html
But then nothing else. Do you know what happened?
Thanks,
Marcelo
--
To unsubscribe from this list: send the line "unsubscribe linux-sctp" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
