On Fri, Sep 19, 2014 at 10:42:04AM -0400, Jonathan Corbet wrote: > - Non-blocking I/O has long been supported with a well-understood set > of operations - O_NONBLOCK and fcntl(). Why do we need a different > mechanism here - one that's only understood in the context of > buffered file I/O? I assume you didn't want to implement support > for poll() and all that, but is that a good enough reason to add a > new Linux-specific non-blocking I/O technique? The Samba usecase would be to first try the nonblocking read and only if that fails hand over to a blocking thread on the same fd. Both interleave, so it's not possible to fcntl in between. dup()ing the fd is also difficult because of the weird close() semantics regarding fcntl locks. > - Patches adding fincore() have been around since at least 2010; see, > for example, https://lwn.net/Articles/371538/ or > https://lwn.net/Articles/604640/. It seems this could be used in > favor of four new read() syscalls; is there a reason it's not > suitable for your use case? Isn't that at least racy? > - Patches adding buffered support for AIO have been around since at > least 2003 - https://lwn.net/Articles/24422/, for example. I guess > I don't really have to ask why you don't want to take that > approach! :) Well, I guess this would work for Samba. Volker -- SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen phone: +49-551-370000-0, fax: +49-551-370000-9 AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen http://www.sernet.de, mailto:kontakt@xxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
