Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(513)

Issue 227133013: Mojo: Dispatcher::MessageInTransitAccess functions don't need to take the lock. (Closed)

Created:
6 years, 8 months ago by viettrungluu
Modified:
6 years, 8 months ago
Reviewers:
DaveMoore
CC:
chromium-reviews, Aaron Boodman, darin (slow to review), viettrungluu+watch_chromium.org, ben+mojo_chromium.org, abarth-chromium
Visibility:
Public.

Description

Mojo: Dispatcher::MessageInTransitAccess functions don't need to take the lock. It'd be safe for them to take the (Dispatcher) lock, since they're only called when they only have one ref (hence there's no lock ordering issue), but by the same token there's no need for them to take the lock at all. (Also add some comments so that I actually understand this. Maybe I'll even notice these comments the next time I notice this "issue".) R=davemoore@chromium.org Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=262256

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+10 lines, -12 lines) Patch
M mojo/system/dispatcher.h View 2 chunks +3 lines, -1 line 0 comments Download
M mojo/system/dispatcher.cc View 4 chunks +4 lines, -8 lines 0 comments Download
M mojo/system/message_in_transit.h View 1 chunk +1 line, -1 line 0 comments Download
M mojo/system/message_pipe_dispatcher.cc View 1 chunk +2 lines, -2 lines 0 comments Download

Messages

Total messages: 3 (0 generated)
viettrungluu
6 years, 8 months ago (2014-04-07 20:24:13 UTC) #1
DaveMoore
lgtm
6 years, 8 months ago (2014-04-07 23:05:09 UTC) #2
viettrungluu
6 years, 8 months ago (2014-04-07 23:52:42 UTC) #3
Message was sent while issue was closed.
Committed patchset #1 manually as r262256 (presubmit successful).

Powered by Google App Engine
This is Rietveld 408576698