[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170419110313.GA17342@quack2.suse.cz>
Date: Wed, 19 Apr 2017 13:03:13 +0200
From: Jan Kara <jack@...e.cz>
To: Goldwyn Rodrigues <rgoldwyn@...e.de>
Cc: Christoph Hellwig <hch@...radead.org>,
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,
sagi@...mberg.me, avi@...lladb.com, axboe@...nel.dk,
linux-api@...r.kernel.org, willy@...radead.org,
tom.leiming@...il.com
Subject: Re: [PATCH 2/8] nowait aio: Introduce RWF_NOWAIT
On Wed 19-04-17 05:30:24, Goldwyn Rodrigues wrote:
>
>
> On 04/19/2017 01:39 AM, Christoph Hellwig wrote:
> >
> >> @@ -1593,6 +1593,11 @@ static int io_submit_one(struct kioctx *ctx, struct iocb __user *user_iocb,
> >> }
> >>
> >> req->common.ki_flags |= iocb_rw_flags(iocb->aio_rw_flags);
> >> + if ((req->common.ki_flags & IOCB_NOWAIT) &&
> >> + !(req->common.ki_flags & IOCB_DIRECT)) {
> >> + ret = -EINVAL;
> >> + goto out_put_req;
> >> + }
> >
> > Wrong indentation. Also I think this should be EOPNOTSUPP here.
> >
>
> Do we plan to add support for nowait in buffered I/O in the future? It
> is just too complicated. EINVAL suits best in this case.
Well, it may be complicated in the current implementation but IMO it makes
sense to ask for such functionality (see e.g. patches for non-blocking
buffered reads that were flying around year or two ago). So I agree with
Christoph that EOPNOTSUPP is more logical.
Honza
--
Jan Kara <jack@...e.com>
SUSE Labs, CR
Powered by blists - more mailing lists