Hi, > > I recently introduced a fifo into my growisofs script. > > Now it is already obsolete. What a carreer. :)) > > > For a talk I gave on "introduction to pthreads" I wrote a ring buffer > program with most of the options one could want.
Isn't there anybody in the world who did not make his own fifo ? :o) But i could need a pointer to some programming hints about threads and signal handling. Especially how to keep all but a particular thread from being interrupted and jumping into the signal handler function. > I played with this a bit, if you are using higher level calls you can > replace fopen() with an open() using O_DIRECT, an fdopen() after that, Are you sure that the FILE functions like fread(), fwrite() don't spoil the success ? > The main benefit was to have less impact on > the rest of the system, the i/o in the program didn't run that much faster. A less annoyed system can possibly deliver better throughput. It is worth to further think about that. (I must get my processing pipe leaner, first.) Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]