Skip to content
Snippets Groups Projects
Commit 667b2022 authored by Bryan Bernhart's avatar Bryan Bernhart Committed by Chromium LUCI CQ
Browse files

WebNN: avoid staging buffers on first inference

Fixes an issue where a staging buffer was always created on first use because its last used fence value was initially set to UINT64_MAX which could never be considered "not in use" until a submission occurred first. Instead, this fence value should of been set the initial value of the queue's fence, which is considered "not in use" without requiring a submission first.

Bug: 358594662
Change-Id: I960d4b55f468f92a8a34bcae896816f2d5e18fc6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5777470


Commit-Queue: ningxin hu <ningxin.hu@intel.com>
Reviewed-by: default avatarningxin hu <ningxin.hu@intel.com>
Reviewed-by: default avatarRafael Cintron <rafael.cintron@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#1339981}
parent ea570c86
No related branches found
No related tags found
No related merge requests found
......@@ -52,7 +52,7 @@ class BufferImplDml final : public WebNNBufferImpl {
// The fence value used to track progress of GPU execution of commands using
// this buffer. Comparing it with the command queue's completed fence can
// indicate whether commands have completed execution.
uint64_t last_submission_fence_value_ = UINT64_MAX;
uint64_t last_submission_fence_value_ = 0;
base::WeakPtrFactory<BufferImplDml> weak_factory_{this};
};
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment