LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
* non-blocking behaviour with multiple readers
@ 2008-02-09 12:57 Simon Richter
0 siblings, 0 replies; only message in thread
From: Simon Richter @ 2008-02-09 12:57 UTC (permalink / raw)
[please CC me, I'm not subscribed to the list]
I'm writing a driver for a pretty simple USB device, and most of what I
need I can see in similar drivers; right now I'm lifting a lot of code
In the read routine, this driver gathers a few locks, then checks
whether data is present and in the non-blocking case returns -EAGAIN,
otherwise waits for data to become available.
In the case of multiple readers, acquiring the locks might however
block, so I'm not sure whether it'd be better to check for non-blocking
first, and acquire the locks with trylock in this case, returning
-EAGAIN in case we fail to acquire any.
The semantic difference seems to be minimal: I believe that it is
acceptable to return -EAGAIN from read even if a previous poll()
suggested that the fd was now readable. Blocking on a non-blocking
read() until other tasks reading from the same fd have left the kernel
seems more like an optimization to me, saving a few syscalls if the
other reader doesn't read all the bytes.
The obvious consistency problem with multiple unsynchronized readers
aside: is that optimization worth a (short) block inside a non-blocking
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2008-02-09 13:32 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-02-09 12:57 non-blocking behaviour with multiple readers Simon Richter
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).