|
From: | Simon Goldschmidt |
Subject: | [lwip-devel] [patch #9384] Partial SACK (RFC 2018) support |
Date: | Wed, 28 Jun 2017 15:46:13 -0400 (EDT) |
User-agent: | Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.109 Safari/537.36 |
Follow-up Comment #12, patch #9384 (project lwip): Re comment #10: > Would it make more sense to have a MEMP_SACK_BLOCK? Not a bad idea. However what I dislike about it is that we can come into a situation where we fail to allocate such a SACK region. Memp allocation might be slower than using the array, but all that array-moving code is not fast, either... However, the idea of somehow combining the ooseq list with the SACK list *does* make sense! Maybe we could think more about it in that direction. _______________________________________________________ Reply to this item at: <http://savannah.nongnu.org/patch/?9384> _______________________________________________ Message sent via/by Savannah http://savannah.nongnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |