[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <x49tx3zpsfg.fsf@segfault.boston.devel.redhat.com>
Date: Mon, 22 Sep 2014 11:48:35 -0400
From: Jeff Moyer <jmoyer@...hat.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: "Elliott\, Robert \(Server Storage\)" <Elliott@...com>,
Andreas Dilger <adilger@...ger.ca>,
Milosz Tanski <milosz@...in.com>,
"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-fsdevel\@vger.kernel.org" <linux-fsdevel@...r.kernel.org>,
"linux-aio\@kvack.org" <linux-aio@...ck.org>,
Mel Gorman <mgorman@...e.de>,
Volker Lendecke <Volker.Lendecke@...net.de>,
Tejun Heo <tj@...nel.org>
Subject: Re: [RFC PATCH 0/7] Non-blockling buffered fs read (page cache only)
Christoph Hellwig <hch@...radead.org> 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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists