Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265092AbTFEVdN (ORCPT ); Thu, 5 Jun 2003 17:33:13 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265148AbTFEVdN (ORCPT ); Thu, 5 Jun 2003 17:33:13 -0400 Received: from mail.ccur.com ([208.248.32.212]:30724 "EHLO exchange.ccur.com") by vger.kernel.org with ESMTP id S265092AbTFEVdM (ORCPT ); Thu, 5 Jun 2003 17:33:12 -0400 Date: Thu, 5 Jun 2003 17:46:38 -0400 From: Joe Korty To: "Richard B. Johnson" Cc: Linux Kernel Mailing List Subject: Re: [PATCH] [2.5] Non-blocking write can block Message-ID: <20030605214638.GA19229@tsunami.ccur.com> Reply-To: joe.korty@ccur.com References: <11E89240C407D311958800A0C9ACF7D1A33EBD@EXCHANGE> <20030605183408.GB3291@matchmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 959 Lines: 25 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/