RTAI API 5.1
|
SCB stand for Shared (memory) Circular Buffer. More...
Functions | |
if (suprt > 1000) | |
Allocate and initialize a shared memory circular buffer. More... | |
return (lbyte >=fbyte ? lbyte - fbyte :size+lbyte - fbyte) | |
Reset a shared memory circular buffer. More... | |
return (fbyte<=lbyte ? size+fbyte - lbyte :size - lbyte) | |
Get the number of bytes avaiable in a shared memory circular buffer. More... | |
if (msg_size > 0 &&((lbyte -=fbyte) >=0 ? lbyte :size+lbyte) >=msg_size) | |
Gets (receives) a message, only if the whole message can be passed all at once. More... | |
if (msg_size > 0 &&((fbyte -=lbyte)<=0 ? size+fbyte :fbyte) > msg_size) | |
Puts (sends) a message, only if the whole message can be passed all at once. More... | |
SCB stand for Shared (memory) Circular Buffer.
It is a non blocking implementation for just a single writer (producer) and reader (consumer) and, under such a constraint, it can be a specific substitute for RTAI mailboxes. There are other constraints that must be satisfied, so it cannot be a general substitute for the more flexible RTAI mailboxes. In fact it provides just functions corresponding to RTAI mailboxes non blocking atomic send/receive of messages, i.e. the equivalents of rt_mbx_send_if and rt_mbx_receive_if. Moreover the circular buffer size must be >= to the largest message to be sent/received. At least the double of the largest message to be sent/received is strongly recommended. Thus sending/receiving a message either succeeds of fails. However thanks to the use of shared memory it should be more efficient than mailboxes in atomic exchanges of messages from kernel to user space. So it is a good candidate for supporting drivers development.
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/.
if | ( | msg_size | , |
0 && | (fbyte -=lbyte)<=0 ? size+fbyte :fbyte, | ||
msg_size | |||
) |
Puts (sends) a message, only if the whole message can be passed all at once.
rt_scb_put tries to atomically send the message msg of msg_size bytes to the shared memory circular buffer scb. It returns immediately and the caller is never blocked.
if | ( | msg_size | , |
0 &&((lbyte -=fbyte) >=0 ? lbyte :size+lbyte) >= | msg_size | ||
) |
Gets (receives) a message, only if the whole message can be passed all at once.
eavedrops a message.
rt_scb_get tries to atomically receive the message msg of msg_size bytes from the shared memory circular buffer scb. It returns immediately and the caller is never blocked.
rt_scb_evdrp atomically spies the message msg of msg_size bytes from the shared memory circular buffer scb. It returns immediately and the caller is never blocked. It is like rt_scb_get but leaves the message in the shared memory circular buffer.
if | ( | suprt | , |
1000 | |||
) |
Allocate and initialize a shared memory circular buffer.
rt_scb_init is used to allocate and/or initialize a shared memory circular buffer.
name | is an unsigned long identifier; |
size | is the size of the circular buffer. |
suprt | is the kernel allocation method to be used, it can be:
|
Since an unsigned long can be a clumsy identifier, services are provided to convert 6 characters identifiers to unsigned long, and vice versa.
It must be remarked that only the very first call does a real allocation, any following call to allocate with the same name, from anywhere, will just increase the usage count and map the circular buffer to the user space, or return the related pointer to the already allocated buffer in kernel/user space. In any case the functions return a pointer to the circular buffer, appropriately mapped to the memory space in use. So if one is really sure that the named circular buffer has been initted already parameters "size" and "suprt" are not used and can be assigned any value.
return | ( | fbyte<=lbyte ? size+fbyte - lbyte :size - | lbyte | ) |
Get the number of bytes avaiable in a shared memory circular buffer.
rt_scb_bytes is used to get the number of bytes avaiable in a shared memory circular buffer; legacy alias for rt_scb_avbs.
scb | is the pointer handle returned when the buffer was initted. |
rt_scb_frbs is used to get the number of free bytes space avaiable in a shared memory circular buffer.
scb | is the pointer handle returned when the buffer was initted. |
return | ( | lbyte >=fbyte ? lbyte - fbyte :size+lbyte - | fbyte | ) |
Reset a shared memory circular buffer.
rt_scb_reset reinitializes a shared memory circular buffer.
scb | is the pointer returned when the buffer was initted. Free a shared memory circular buffer. |
rt_scb_delete is used to release a previously allocated shared memory circular buffer.
name | is the unsigned long identifier used when the buffer was allocated; |
Analogously to what done by all the named allocation functions the freeing calls have just the effect of decrementing a usage count, unmapping any user space shared memory being freed, till the last is done, as that is the one the really frees any allocated memory.
No need to call this function if you provided your own memory for the circular buffer. Get the number of bytes avaiable in a shared memory circular buffer.
rt_scb_avbs is used to get the number of bytes avaiable in a shared memory circular buffer.
scb | is the pointer handle returned when the buffer was initted. |