[mojo-edk] Investigate scatter-gather syscalls for sending channel messages. |
|||||||||
Issue descriptionBoth POSIX (via sendmsg) and Windows (via WriteFileGather) support scatter-gather writes to a handle. This might be useful to avoid copies inside the EDK. We should look into this.
,
Mar 1 2017
This issue has been available for more than 365 days, and should be re-evaluated. Please re-triage this issue. The Hotlist-Recharge-Cold label is applied for tracking purposes, and should not be removed after re-triaging the issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 1 2017
Taking this so it doesn't get lost in the void. +darin FYI since we just discussed this recently and +yzshen for a bindings perspective It's not clear if we need/want vector IO now, but something to think about.
,
Mar 1 2017
+yzshen for real
,
Mar 1 2017
It seems to be a nice idea to explore. Currently our serialization code calculates size for a message before serialization. Comparing with the approach of growing-buffer-when-needed, this approach avoids copying data between buffers when growing the buffer, but it comes with the cost of walking the entire data structure to calculate size. With scatter-gather support (exposed by the mojo system API), we will be able to have the best of both approaches.
,
Apr 25 2017
,
May 29 2017
I've done some investigation into this. Unfortunately on Windows we would be forced to issue multiple Write/ReadFile calls per message as there appears to be no scatter-gather mechanism for named pipes. We'll probably get more mileage out of other optimization efforts first.
,
May 29 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 17
,
Nov 6
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by amistry@chromium.org
, Mar 1 2016