[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b09e799e-9d9f-ae22-1f09-babd6521b11d@kernel.dk>
Date: Tue, 18 Apr 2023 19:28:26 -0600
From: Jens Axboe <axboe@...nel.dk>
To: Dave Chinner <david@...morbit.com>,
Bernd Schubert <bschubert@....com>
Cc: Miklos Szeredi <miklos@...redi.hu>,
"Darrick J. Wong" <djwong@...nel.org>,
Christoph Hellwig <hch@...radead.org>,
"io-uring@...r.kernel.org" <io-uring@...r.kernel.org>,
"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"linux-xfs@...r.kernel.org" <linux-xfs@...r.kernel.org>,
Dharmendra Singh <dsingh@....com>
Subject: Re: [PATCH 1/2] fs: add FMODE_DIO_PARALLEL_WRITE flag
On 4/18/23 4:13?PM, Dave Chinner wrote:
>>> Without first attempting to answer those questions, I'd be reluctant
>>> to add FMODE_DIO_PARALLEL_WRITE to fuse.
>
> I'd tag it with this anyway - for the majority of apps that are
> doing concurrent DIO within EOF, shared locking is big win. If
> there's a corner case that apps trigger that is slow, deal with them
> when they are reported....
Agree, the common/fast case will be fine, which is really the most
important part.
--
Jens Axboe
Powered by blists - more mailing lists