| |||||||||||||
Kernel events without keventsKernel events without keventsPosted Mar 15, 2007 16:17 UTC (Thu) by felixfix (subscriber, #242)In reply to: Kernel events without kevents by pphaneuf Parent article: Kernel events without kevents
Multiple writers to one pipe can easily interleave. It's been a while now, but there is that message pipe, is it the ATT substitute? which only writes complete messages atomically or returns an error. But regular pipes have no guarantees, just like writing to any file. If your data crosses a block boundary, you have no guarantees, and maybe not even if you stay within block boundaries.
(Log in to post comments)
Kernel events without kevents Posted Mar 15, 2007 16:38 UTC (Thu) by pphaneuf (guest, #23480) [Link] Well, since I don't even look at the value that I read, it doesn't matter much, doesn't it? Depending on environmental constraints, I either use a pipe per signal, or the pipe is only to "wake up" the select() and I check some volatile bools that the signal handlers set to know which one it was. Furthermore, since my "messages" are a single byte (I usually use 42 as a value), and that's the granularity of a pipe, they'd still be atomic. That's if I cared about their value, of course.
|
|||||||||||||