> On Jul 6, 2016, at 15:53, J. Bruce Fields <bfields@xxxxxxxxxxxx> wrote: > > On Fri, Jun 24, 2016 at 10:55:51AM -0400, Trond Myklebust wrote: >> Instead of trying (and failing) to predict how much writeable socket space >> will be available to the RPC call, just fall back to the simple model of >> deferring processing until the socket is uncongested. >> >> If a limit is neeeded, then set the hard per-connection limit. > > I was hoping this would be an opportunity to get rid of even more code, > but there's still the udp case. Do we actually need that? > I wasn’t really too concerned about UDP; I consider it to be legacy code. That said, I’d argue the existing system make a little more sense in the case of UDP as you don’t have any equivalent of the TCP window size. That means the socket buffer sizes are predictable, and so are more easily modelled as a pipeline. Cheers Trond -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
