diff options
| author | jam <jam@chromium.org> | 2015-07-23 16:52:38 -0700 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2015-07-23 23:53:50 +0000 |
| commit | 527a6e1b6bdf00a4d8cb020914067612b6ecde99 (patch) | |
| tree | 0158c084d627712a1905ea0d577283cd1e98b6a6 /ipc | |
| parent | f0f069a2a8b0398b58b3a39ddad928093f03ae8a (diff) | |
| download | chromium_src-527a6e1b6bdf00a4d8cb020914067612b6ecde99.zip chromium_src-527a6e1b6bdf00a4d8cb020914067612b6ecde99.tar.gz chromium_src-527a6e1b6bdf00a4d8cb020914067612b6ecde99.tar.bz2 | |
Use thread-safe send when using Mojo.
All the work was done in r325911 by morrita. It looks like when the change landed it was disabled though, so this change just turns it on.
https://groups.google.com/a/chromium.org/d/msg/mojo-dev/gSidpDqtUFE/TY5qeUlD-mIJ has more timing, but the summary is that this makes MojoChannelPerfTest.ChannelProxyPingPong faster by 15% on Windows and roughly 40% on Linux.
In total, ChannelProxyPingPong is faster using Mojo compared to Chrome IPC by roughly 70% on Windows and on Linux it's about the same or slightly faster.
BUG=472113
Review URL: https://codereview.chromium.org/1246953003
Cr-Commit-Position: refs/heads/master@{#340216}
Diffstat (limited to 'ipc')
| -rw-r--r-- | ipc/mojo/ipc_channel_mojo.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/ipc/mojo/ipc_channel_mojo.cc b/ipc/mojo/ipc_channel_mojo.cc index 4d5b815..08c3458 100644 --- a/ipc/mojo/ipc_channel_mojo.cc +++ b/ipc/mojo/ipc_channel_mojo.cc @@ -447,7 +447,7 @@ bool ChannelMojo::Send(Message* message) { } bool ChannelMojo::IsSendThreadSafe() const { - return false; + return true; } base::ProcessId ChannelMojo::GetPeerPID() const { |