Lines Matching refs:buffer
264 integers (ie. a data buffer).
594 All binding implementations can buffer exactly one outgoing message. If another
595 send function is called on the same binding while the buffer is full, the
985 a buffer that is used to store incoming messages. The dispatcher can have
999 endpoint buffer.
1003 endpoint buffer and then make the receiver dispatcher runnable (which will cause
1007 rest of the message out of the buffer and invoking appropriate user-defined
1020 receiver, where it sets up its own endpoint cap and buffer and binding struct,
1049 communication. The shared memory is split into a send buffer and a receive
1050 buffer (Figure~\ref{fig:ump}), with each entry in the buffers being the size of
1051 a cache line. The sender writes into the send buffer, and the receiver reads
1060 channel also contains an epoch flag. Every buffer entry has an epoch bit that is
1062 epoch is compared to the epoch bit of the buffer slot to be read. If it is the
1068 avoid bouncing cache lines the buffer is kept write-only for the sender and
1071 many messages are outstanding and together with knowledge of the buffer size,
1075 channel buffers, then sending a cap to the buffer along with a bind request