1.1 --- a/docs/wiki/Components Sat May 11 00:10:59 2024 +0200
1.2 +++ b/docs/wiki/Components Sat May 11 00:49:24 2024 +0200
1.3 @@ -348,7 +348,7 @@
1.4 Directory -> Reader1;
1.5 Reader1 -> Client2;
1.6
1.7 - Client3 -> Reader2 [label="current_region()"];
1.8 + Client3 -> Reader2 [label="refresh()"];
1.9 Reader3 -> Memory -> Client4;
1.10 }
1.11 }}}
1.12 @@ -360,7 +360,7 @@
1.13
1.14 {{{
1.15 reader = directory.opendir()
1.16 -reader.current_region()
1.17 +reader.refresh()
1.18 entries = reader.read() # this being a memory access operation
1.19 }}}
1.20
1.21 @@ -397,14 +397,13 @@
1.22 fully populated region. Naturally, the reader may not advance ahead of the
1.23 writer.
1.24
1.25 -Pipes implement the `Pipe` interface and a number of operations to support
1.26 -this interaction mechanism.
1.27 +Pipes implement a number of operations to support this interaction mechanism.
1.28
1.29 The details of an endpoint's current region can be queried using the following
1.30 -operation:
1.31 +operation from the `Flush` interface:
1.32
1.33 {{{
1.34 -current_region(inout offset_t position, out offset_t populated_size, out offset_t size)
1.35 +refresh(out offset_t position, out offset_t size, out offset_t region_size)
1.36 }}}
1.37
1.38 This provides details of the recorded access position in a region, the
1.39 @@ -413,7 +412,7 @@
1.40 the same.
1.41
1.42 Navigation to the next available region of the pipe is performed using the
1.43 -following operation:
1.44 +following operation from the `Pipe` interface:
1.45
1.46 {{{
1.47 next_region(inout offset_t populated_size, out offset_t size)