Erik Nordmark wrote:
Dan McDonald wrote:
It's hard to latch for an unconnected UDP socket where we're uttering
sendto(3SOCKET) to different peers.
Yes, but for UDP performance we want to handle the case when a socket is
repeatedly sending to the same destination differently, for instance by
caching the IRE and the source address that was selected. If/when we
fully do this, we can also latch the policy lookup.
Is this a common case, or are application writers sensible enough
to use a connected UDP socket? What's the cost/benefit analysis?
- Jeremy
_______________________________________________
networking-discuss mailing list
[email protected]
