Date: Sat, 11 Jun 2005 07:10:21 -0700 From: Alfred Perlstein <alfred@freebsd.org> To: Brian Fundakowski Feldman <green@freebsd.org> Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/nfsclient nfs_bio.c nfs_vfsops.c nfsargs.h nfsmount.h src/sys/sys buf.h bufobj.h src/sys/kern vfs_bio.c Message-ID: <20050611141021.GD17867@elvis.mu.org> In-Reply-To: <20050611064956.GC66188@green.homeunix.org> References: <200506102350.j5ANofFM008212@repoman.freebsd.org> <20050611034930.GY17867@elvis.mu.org> <20050611064956.GC66188@green.homeunix.org>
next in thread | previous in thread | raw e-mail | index | archive | help
* Brian Fundakowski Feldman <green@freebsd.org> [050610 23:49] wrote: > On Fri, Jun 10, 2005 at 08:49:30PM -0700, Alfred Perlstein wrote: > > Returning EAGAIN from a disk IO seems bogus, are you sure it makes > > sense to do that when IO_NDELAY is set? Shouldn't it just be ignored > > like other FSes do? > > Well, it's not disk IO, it's network IO. I figure if you set that > flag you should expect commensurate error return values. This is > conceivably a useful behavior, and POSIX does not forbid it, so I just > made the judgement call to not deny the functionality. > > Would you actually be surprised to get EAGAIN if you requested > non-blocking access to a file stream, ignoring the fact that it just > happens to not have been done already for other S_ISREG file streams? How does one poll(2) or kqueue(2) to determine when EAGAIN will "go away" ? Maybe I'm misreading the code, but it appears that O_FSYNC writes on a non-blocking write will _always_ return EAGAIN? So when is it safe to "AGAIN"? :) -- - Alfred Perlstein - email: bright@mu.org cell: 408-480-4684
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050611141021.GD17867>