Skip to content

Commit

Permalink
Fix typos. (gpuweb#309)
Browse files Browse the repository at this point in the history
  • Loading branch information
@waywardmonkeys @kainino0x
waywardmonkeys authored and kainino0x committed May 23, 2019
1 parent 51be483 commit 4ead90f
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions design/TimelineFences.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ To simplify the validation of signal-before-wait, we can force signaled number t

Thus each fence has two pieces of internal state:
- The signaled value, the latest value passed to a signal to the fence, which is also the greatest thanks to the monotonicity
- The completed value, the value corresponding to the lastest signal operation that has been executed.
- The completed value, the value corresponding to the latest signal operation that has been executed.

The fences will require additional restrictions and operations if WebGPU has multiple queues.
These changes will be tagged with [multi-queue]
Expand Down Expand Up @@ -92,4 +92,4 @@ It makes further execution on the queue wait until the value is passed on the fe

- Should we call fences "timelines" and have them created on queues like so `queue.createTimeline()`?
- How do we wait synchronously on fences?
Maybe it chould be similar to `Atomics.wait`?
Maybe it could be similar to `Atomics.wait`?

0 comments on commit 4ead90f

Please sign in to comment.