Multi-threading access to device drivers.
Garrett Wollman
wollman at khavrinen.lcs.mit.edu
Sat Nov 6 16:15:16 PST 2004
In article <10847.1099784360 at critter.freebsd.dk> you write:
>Assume a process with two threads on two CPUs, both
>doing read(fd, buf, len) at the same time.
>
>Should we let both reads into the driver at the same time ?
>
>If so, which uio_offset do we hand them ?
POSIX is quite clear on the matter:
> All of the functions chmod (), close (), fchmod (), fcntl (), fstat
> (), ftruncate (), lseek (), open (), read (), readlink (), stat (),
> symlink ( ), and write ( ) shall be atomic with respect to each other
> in the effects specified in IEEE Std 1003.1-2001 when they operate on
> regular files. If two threads each call one of these functions, each
> call shall either see all of the specified effects of the other call,
> or none of them.
(One of the "specified effects" is advancing the file offset.)
-GAWollman
--
Garrett A. Wollman | As the Constitution endures, persons in every
wollman at lcs.mit.edu | generation can invoke its principles in their own
Opinions not those of| search for greater freedom.
MIT, LCS, CRS, or NSA| - A. Kennedy, Lawrence v. Texas, 539 U.S. ___ (2003)
More information about the freebsd-arch
mailing list