Re: [PATCH RFC] tcp: use seqlock for all cached tcp_metrics

From: Julian Anastasov <ja@ssi.bg>
Date: Sun, 22 Jul 2012 12:44:28 +0300

	The ability to reclaim existing cache entries
requires metrics to be accessed with additional seqlock.
fastopen_cache tried to provide such locking for its values
but there is always the risk to access reclaimed entry.

I basically claim that accidental use of reclaimed entries
is completely harmless for everything other than fastopen.

Therefore I do not advocate adding the new overhead and complexity for
the non-fastopen cases.  It should be a completely free, lockless, and
synchornization free cache.  If we read crap metrics, so be it, maybe
the network dynamics changed to the same amount, and we would never
know the different.  Therefore, it doesn't really matter if we read
crap values for these measurements.

Thanks.