The dst/route cache has effectively been replaced by the TCP metrics cache. Values like MSS, SRTT, and cwnd are still useful to preserve across streams between

The dst/route cache has effectively been replaced by the TCP metrics cache. Values like MSS, SRTT, and cwnd are still useful to preserve across streams between peers. See ip-tcp_metrics(8) for a decent summary. David Miller has a summary of the route cache removal in http://vger.kernel.org/~davem/columbia2012.pdf http://vger.kernel.org/~davem/columbia2012.pdf. The cache exhaustion argument was .. odd. As I recall the cache entry was created on handshake and was keyed off of src ip, dst IP, dst port. Given that the attacker can (effectively) only vary the src ip thats a lot of addresses to control. The other argument was that not hitting a cache was "only" 10% slower in microbenchmarks. Personally Im dubious of the route cache removal, though I havent tested. The 10% hit rate, as I recall, was from Google front end servers which Id expect to have a high cardinality of peers along with a simplistic route table. For servers with multiple interfaces, variable route properties, multiple tables, etc and a high packet rate a fast cache should be quite valuable.