DescriptionRevert 146792 - Lock-free GamepadSeqLock (try 2)
[Reverted due to crashing in ChromeBot with following stack:
content::internal::GamepadSeqLockBase::ReadTo+0x1a
content::GamepadSharedMemoryReader::SampleGamepads+0xaa
RendererWebKitPlatformSupportImpl::sampleGamepads+0x57
WebCore::sampleGamepads+0x3f
WebCore::NavigatorGamepad::gamepads+0x71
WebCore::NavigatorV8Internal::webkitGamepadsAttrGetter+0x45
v8::internal::JSObject::GetPropertyWithCallback+0x252]
The change
- provides an improved lock-free SeqLock implementation which eliminates any potential blocking of readers.
- provides a higher-level and simpler API as was suggested by Darin.
- ThreadSanitizer report suppressions are replaced with correct synchronization.
- eliminates nasty kMaximumContentionCount and associated histogram.
Oritignal review URL:
http://codereview.chromium.org/8772004
TBR=darin@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10704041
TBR=dvyukov@chromium.org
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=146896
Patch Set 1 #
Messages
Total messages: 2 (0 generated)
|