Lines Matching refs:a
4 Without a buffer pool, a process calls a synchronous method of the other
5 process and waits until the call finishes transferring a buffer. This adds
6 unwanted latency due to context switching. With help from a buffer pool, a
9 Passing an interface and a handle adds extra latency also. To mitigate the
11 rogue clients, FMQ is used to communicate between a buffer pool and a client
12 process. FMQ is used to send buffer ownership change status from a client
13 process to a buffer pool. Except FMQ, a buffer pool does not use any shared
18 FMQ is used to send buffer ownership status changes to a buffer pool from a
19 buffer pool client. A buffer pool synchronizes FMQ messages when there is a
24 FMQ messages are sent when a buffer is acquired or released. Also, FMQ messages
25 are sent when a buffer is transferred from a client to another client. FMQ has
26 its own ID from a buffer pool. A client is specified with the ID.
28 To transfer a buffer, a sender must send an FMQ message. The message must
29 include a receiver's ID and a transaction ID. A receiver must send the
30 transaction ID to fetch a buffer from a buffer pool. Since the sender already
32 receiver with the transaction ID. In order to prevent faking a receiver, a
33 connection to a buffer pool from client is made and kept privately. Also part of
34 transaction ID is a sender ID in order to prevent fake transactions from other
35 clients. This must be verified with an FMQ message from a buffer pool.
42 A connection to a buffer pool from a buffer pool client. The connection
47 An accessor to a buffer pool which makes a connection to the buffer pool.
52 sets up a process to be a receiver of buffers from a buffer pool. The manager
53 is unique in a process.