There has been some griping (that hasn't yet appeared on this mailing list) that the ntirpc worker pool is too slow processing TCP output. But no specific proof.
There are several possible reasons for that, including that the work model there would be better per interface, rather than per connection. I've mentioned fair queuing before. I've made a lock-free variant for RDMA, but for TCP that requires combining the fridge thread pool with the ntirpc pool. I've had code for that sitting around since May, although it's rather bit-rotten in the meantime. I've been assuming you don't want it until the new RDMA? ------------------------------------------------------------------------------ Monitor Your Dynamic Infrastructure at Any Scale With Datadog! Get real-time metrics from all of your servers, apps and tools in one place. SourceForge users - Click here to start your Free Trial of Datadog now! http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 _______________________________________________ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
