Messages in this thread | | | Date | Thu, 5 Jun 2003 17:46:38 -0400 | From | Joe Korty <> | Subject | Re: [PATCH] [2.5] Non-blocking write can block |
| |
On Thu, Jun 05, 2003 at 03:15:19PM -0400, Richard B. Johnson wrote: > On Thu, 5 Jun 2003, Mike Fedyk wrote: > > Also, what do other UNIX OSes do? Do they have seperate semantics for > > O_NONBLOCK and O_NDELAY? If so, then it would probably be better to change > > O_NDELAY to be similar and add another feature at the same time as reducing > > platform specific codeing in userspace. > > My Sun thinks that O_NDELAY = 0x04 and O_NONBLOCK = 0x80, FWIW.
Same here on my AT&T System V ES/MP box.
As far as semantics go, the two appear to be identical except that O_NDELAY always returns 0 on a blocking condition while O_NONBLOCK usually returns EAGAIN and only occasionally returns 0.
Joe
[cc list trimmed] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |