[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200627065104.GA20157@infradead.org>
Date: Sat, 27 Jun 2020 07:51:04 +0100
From: Christoph Hellwig <hch@...radead.org>
To: Kanchan Joshi <joshi.k@...sung.com>
Cc: Christoph Hellwig <hch@...radead.org>, axboe@...nel.dk,
viro@...iv.linux.org.uk, bcrl@...ck.org, asml.silence@...il.com,
Damien.LeMoal@....com, linux-fsdevel@...r.kernel.org,
mb@...htnvm.io, linux-kernel@...r.kernel.org, linux-aio@...ck.org,
io-uring@...r.kernel.org, linux-block@...r.kernel.org,
selvakuma.s1@...sung.com, nj.shetty@...sung.com,
javier.gonz@...sung.com, Arnav Dawn <a.dawn@...sung.com>
Subject: Re: [PATCH v2 1/2] fs,block: Introduce RWF_ZONE_APPEND and handling
in direct IO path
On Sat, Jun 27, 2020 at 02:45:14AM +0530, Kanchan Joshi wrote:
> For block IO path (which is the scope of this patchset) there is no
> probelm in using RWF_APPEND for zone-append, because it does not do
> anything for block device. We can use that, avoiding introduction of
> RWF_ZONE_APPEND in user-space.
No, you are not just touching the block I/O path. This is all over the
general file code, and all RWF_* flag are about file I/O.
Powered by blists - more mailing lists