[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <acb0fc57-5005-4422-9c42-3345e892ecb2@suse.de>
Date: Sun, 28 May 2017 21:38:27 -0500
From: Goldwyn Rodrigues <rgoldwyn@...e.de>
To: Christoph Hellwig <hch@...radead.org>
Cc: linux-fsdevel@...r.kernel.org, jack@...e.com,
linux-block@...r.kernel.org, linux-btrfs@...r.kernel.org,
linux-ext4@...r.kernel.org, linux-xfs@...r.kernel.org,
axboe@...nel.dk, linux-api@...r.kernel.org,
adam.manzanares@....com, viro@...iv.linux.org.uk
Subject: Re: [PATCH 0/10 v9] No wait AIO
On 05/28/2017 04:27 AM, Christoph Hellwig wrote:
>> Changes since v8:
>> + Err out AIO reads with -EINVAL flagged as RWF_NOWAIT
>
> Ugg, why? Reads aren't really treated any different than writes in
> the direct I/O code.
This effort focused on writes only.
>From the point of view of the application/user, reads are usually
required to complete with success. I don't see a scenario where reads()
would need the nowait feature. If there is a use case, I'd be happy to
add and support it.
--
Goldwyn
Powered by blists - more mailing lists