From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Moyer Subject: Re: [RFC PATCH 0/7] Non-blockling buffered fs read (page cache only) Date: Mon, 22 Sep 2014 11:48:35 -0400 Message-ID: References: <8EC2A7F3-0E25-4054-9863-4488B8ED5C8D@dilger.ca> <94D0CD8314A33A4D9D801C0FE68B402958C81D56@G9W0745.americas.hpqcorp.net> <20140919112147.GA4639@infradead.org> Mime-Version: 1.0 Content-Type: text/plain Cc: "Elliott\, Robert \(Server Storage\)" , Andreas Dilger , Milosz Tanski , "linux-kernel\@vger.kernel.org" , "linux-fsdevel\@vger.kernel.org" , "linux-aio\@kvack.org" , Mel Gorman , Volker Lendecke , Tejun Heo To: Christoph Hellwig Return-path: In-Reply-To: <20140919112147.GA4639@infradead.org> (Christoph Hellwig's message of "Fri, 19 Sep 2014 04:21:47 -0700") Sender: owner-linux-aio@kvack.org List-Id: linux-fsdevel.vger.kernel.org Christoph Hellwig writes: > Without the atomic WRITE SCATTERED use case adding the syscalls seems > rather pointless, and I'd really avoid blocking nice software only > features like the per-I/O nonblock flag (and the similarly trivial > per-I/O sync option I have a prototype for) on it. Andreas and Zach pointed out that the scatter/gather system calls also help network file systems. I'm not yet sure how much work it would be, but it certainly seems worth considering readx/writex (or whatever we want to call them) to avoid needlessly adding a ton of system calls. Cheers, Jeff -- To unsubscribe, send a message with 'unsubscribe linux-aio' in the body to majordomo@kvack.org. For more info on Linux AIO, see: http://www.kvack.org/aio/ Don't email: aart@kvack.org