On Maw, 2005-11-22 at 20:32 -0800, Mike Voytovich wrote:
> Please disregard - the user app was reading less than VMIN in the read()
> call, so I suppose the current behavior in that case would be correct
> (returning immediately with the number of bytes passed into read()
> rather than waiting for VMIN or VTIME to be met before returning).
>
> It doesn't appear that the behavior in this case is explicitly defined
> by POSIX, but it seems like a reasonable thing to do.
Its pretty well defined. It was designed to optimise block serial
operations (uucp and the like)
VMIN - number of bytes you expect this packet
VTIME - when to give up waiting
The form 0, VTIME also being used to do polling on old SYSV that lacked
select/poll
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
