On 7/25/18 7:39 PM, Frank Filz wrote:
I’ve put some analysis in this document:
https://docs.google.com/document/d/1E0LtMCxZngS4Ri0Q5ny_kAFbl4SFt20YATjfB...
I’ve given a bunch of folks write access so they can comment and add detail that makes
sense.
I don't see any analysis. What are you trying to accomplish?
Do you have example compounds actually sent by the Linux client
that need operations to be processed asynchronously?
Each svc_req is already async, so the only additional async
would be individual operations within a compound.
So you'd need another whole additional async layer on top of
the existing svc_req, with completions that trigger the
svc_req completion.
This isn't likely to buy you anything, other than a lot more
locking and task switches. That is, slow everything down.