From: Ritesh Harjani <riteshh@linux.ibm.com>
To: Joseph Qi <joseph.qi@linux.alibaba.com>,
jack@suse.cz, tytso@mit.edu, linux-ext4@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, mbobrowski@mbobrowski.org
Subject: Re: [PATCHv4 0/3] Fix inode_lock sequence to scale performance of DIO mixed R/W workload
Date: Fri, 6 Dec 2019 14:19:52 +0530 [thread overview]
Message-ID: <20191206084953.CEF21A405F@d06av23.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <97fe59fa-0161-c035-40d0-3a9770ab426c@linux.alibaba.com>
On 12/6/19 2:16 PM, Joseph Qi wrote:
> Tested with the following case:
>
> fio -name=parallel_dio_reads_test -filename=/mnt/nvme0n1/testfile \
> -direct=1 -iodepth=1 -thread -rw=randrw -ioengine=psync -bs=$bs \
> -size=20G -numjobs=8 -runtime=600 -group_reporting
>
> The performance result is the same as reverting parallel dio reads[1]
> or even slightly better in both bandwidth and latency, which is as
That's great!!
> expected.
>
> So, Tested-by: Joseph Qi <joseph.qi@linux.alibaba.com>
Thanks :)
-ritesh
prev parent reply other threads:[~2019-12-06 8:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 6:46 [PATCHv4 0/3] Fix inode_lock sequence to scale performance of DIO mixed R/W workload Ritesh Harjani
2019-12-05 6:46 ` [PATCHv4 1/3] ext4: fix ext4_dax_read/write inode locking sequence for IOCB_NOWAIT Ritesh Harjani
2019-12-05 6:46 ` [PATCHv4 2/3] ext4: Start with shared i_rwsem in case of DIO instead of exclusive Ritesh Harjani
2019-12-05 12:03 ` Jan Kara
2019-12-05 13:40 ` Ritesh Harjani
2019-12-05 6:46 ` [PATCHv4 3/3] ext4: Move to shared i_rwsem even without dioread_nolock mount opt Ritesh Harjani
2019-12-05 12:05 ` Jan Kara
2019-12-05 13:41 ` Ritesh Harjani
2019-12-05 13:46 ` Ritesh Harjani
2019-12-06 8:46 ` [PATCHv4 0/3] Fix inode_lock sequence to scale performance of DIO mixed R/W workload Joseph Qi
2019-12-06 8:49 ` Ritesh Harjani [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191206084953.CEF21A405F@d06av23.portsmouth.uk.ibm.com \
--to=riteshh@linux.ibm.com \
--cc=jack@suse.cz \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mbobrowski@mbobrowski.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).