Received-SPF: pass (google.com: best guess record for domain of linux-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Tue, 27 Aug 2019 21:51:18 +1000
From:   Dave Chinner <david@fromorbit.com>
To:     Joseph Qi <joseph.qi@linux.alibaba.com>
Cc:     Theodore Ts'o <tytso@mit.edu>, Andreas Dilger <adilger@dilger.ca>,
        Jan Kara <jack@suse.cz>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH 0/3] Revert parallel dio reads
Message-ID: <20190827115118.GY7777@dread.disaster.area>
References: <1566871552-60946-1-git-send-email-joseph.qi@linux.alibaba.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1566871552-60946-1-git-send-email-joseph.qi@linux.alibaba.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Sender: linux-ext4-owner@vger.kernel.org
Precedence: bulk

On Tue, Aug 27, 2019 at 10:05:49AM +0800, Joseph Qi wrote:
> This patch set is trying to revert parallel dio reads feature at present
> since it causes significant performance regression in mixed random
> read/write scenario.
> 
> Joseph Qi (3):
>   Revert "ext4: remove EXT4_STATE_DIOREAD_LOCK flag"
>   Revert "ext4: fix off-by-one error when writing back pages before dio
>     read"
>   Revert "ext4: Allow parallel DIO reads"
> 
>  fs/ext4/ext4.h        | 17 +++++++++++++++++
>  fs/ext4/extents.c     | 19 ++++++++++++++-----
>  fs/ext4/inode.c       | 47 +++++++++++++++++++++++++++++++----------------
>  fs/ext4/ioctl.c       |  4 ++++
>  fs/ext4/move_extent.c |  4 ++++
>  fs/ext4/super.c       | 12 +++++++-----
>  6 files changed, 77 insertions(+), 26 deletions(-)

Before doing this, you might want to have a chat and co-ordinate
with the folks that are currently trying to port the ext4 direct IO
code to use the iomap infrastructure:

https://lore.kernel.org/linux-ext4/20190827095221.GA1568@poseidon.bobrowski.net/T/#t

That is going to need the shared locking on read and will work just
fine with shared locking on write, too (it's the code that XFS uses
for direct IO). So it might be best here if you work towards shared
locking on the write side rather than just revert the shared locking
on the read side....

Cheers,

Dave,
-- 
Dave Chinner
david@fromorbit.com