KFIFO_IN(9) FIFO Buffer KFIFO_IN(9)NAME
kfifo_in - put data into the fifo
kfifo_in(fifo, buf, n);
address of the fifo to be used
the data to be added
number of elements to be added
This macro copies the given buffer into the fifo and returns the number of copied elements.
Note that with only one concurrent reader and one concurrent writer, you don't need extra locking to use these macro.
COPYRIGHT Kernel Hackers Manual 3.10 June 2014 KFIFO_IN(9)
Check Out this Related Man Page
fifo - Create and manipulate u-turn fifo channels
package require Tcl
package require memchan
fifo creates a stream-oriented in-memory channel and returns its handle. There is no restriction on the ultimate size of the channel, it
will always grow as much as is necessary to accomodate the data written into it.
In contrast to the channels generated by memchan a channel created here effectively represents an U-turn. All data written into it
can be read out, but only in the same order. This also means that a fifo channel is not seekable.
The channels created here can be transfered between interpreters in the same thread and between threads, but only as a whole. It is
not possible to use them to create a bi- or unidirectional connection between two interpreters.
Memory channels created by fifo provide two read-only options which can be queried via the standard fconfigure command. These are
The value of this option is the number of bytes currently stored in the queried memory channel.
The value of this option is the number of bytes currently allocated by the queried memory channel. This number is at least as big as
the value of -length.
As the channels generated by fifo grow as necessary they are always writable. This means that a writable fileevent-handler will fire con-
The channels are also readable if they contain more than zero bytes. Under this conditions a readable fileevent-handler will fire continu-
One possible application of memory channels created by memchan or fifo is as temporay storage device to collect data coming in over a pipe
or a socket. If part of the processing of the incoming data is to read and process header bytes or similar fifo are easier to use as they
do not require seeking back and forth to switch between the assimilation of headers at the beginning and writing new data at the end.
fifo2, memchan, null
channel, fifo, i/o, in-memory channel, memchan, stream
Copyright (c) 1996-2003 Andreas Kupries <firstname.lastname@example.org>
Memory channels 2.1 fifo(n)
I did my research (on google, this site and my local library) but I am *still* lost. I am trying to teach myself about `named pipes` playing around with MKFIFO (Why not?).
(1) It seems MKNOD is reserved to ROOT whereas MKFIFO is accessible to all users. Am I correct? If the answer is... (20 Replies)
I'm new to working with pipes, so I don't know whether the following is expected behaviour or a bug on the part of an application.
Since Version 0.47, Inkscape provides a non-GUI interactive shell mode of operation. I am trying to time the program's performance in converting SVG files to PNG... (1 Reply)
This is my first post, hope I am doing it right.
I have a large file, like 6 GB. Its a proxy file so vendor requested to change username from logs for saving the confidentiality of the user.
This is the script I created (With the help of Google):
tmp="echo " $5 " |... (12 Replies)