From: Stefan Hajnoczi <stefanha@redhat.com>
To: Max Gurtovoy <mgurtovoy@nvidia.com>
Cc: hch@infradead.org, mst@redhat.com,
virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
israelr@nvidia.com, nitzanc@nvidia.com, oren@nvidia.com,
linux-block@vger.kernel.org, axboe@kernel.dk
Subject: Re: [PATCH v3 1/1] virtio-blk: avoid preallocating big SGL for data
Date: Thu, 2 Sep 2021 13:21:27 +0100 [thread overview]
Message-ID: <YTDBx/E/UJZWTFlG@stefanha-x1.localdomain> (raw)
In-Reply-To: <20210901131434.31158-1-mgurtovoy@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 2254 bytes --]
On Wed, Sep 01, 2021 at 04:14:34PM +0300, Max Gurtovoy wrote:
> No need to pre-allocate a big buffer for the IO SGL anymore. If a device
> has lots of deep queues, preallocation for the sg list can consume
> substantial amounts of memory. For HW virtio-blk device, nr_hw_queues
> can be 64 or 128 and each queue's depth might be 128. This means the
> resulting preallocation for the data SGLs is big.
>
> Switch to runtime allocation for SGL for lists longer than 2 entries.
> This is the approach used by NVMe drivers so it should be reasonable for
> virtio block as well. Runtime SGL allocation has always been the case
> for the legacy I/O path so this is nothing new.
>
> The preallocated small SGL depends on SG_CHAIN so if the ARCH doesn't
> support SG_CHAIN, use only runtime allocation for the SGL.
>
> Re-organize the setup of the IO request to fit the new sg chain
> mechanism.
>
> No performance degradation was seen (fio libaio engine with 16 jobs and
> 128 iodepth):
>
> IO size IOPs Rand Read (before/after) IOPs Rand Write (before/after)
> -------- --------------------------------- ----------------------------------
> 512B 318K/316K 329K/325K
>
> 4KB 323K/321K 353K/349K
>
> 16KB 199K/208K 250K/275K
>
> 128KB 36K/36.1K 39.2K/41.7K
>
> Signed-off-by: Max Gurtovoy <mgurtovoy@nvidia.com>
> Reviewed-by: Israel Rukshin <israelr@nvidia.com>
> ---
>
> changes from V2:
> - initialize vbr->out_hdr.sector during virtblk_setup_cmd
>
> changes from V1:
> - Kconfig update (from Christoph)
> - Re-order cmd setup (from Christoph)
> - use flexible sg pointer in the cmd (from Christoph)
> - added perf numbers to commit msg (from Feng Li)
>
> ---
> drivers/block/Kconfig | 1 +
> drivers/block/virtio_blk.c | 155 +++++++++++++++++++++++--------------
> 2 files changed, 100 insertions(+), 56 deletions(-)
Hi Max,
I can run benchmark to give everyone more confidence about this change.
Should I test this version or are you still planning to make code
changes?
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-09-02 12:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 13:14 [PATCH v3 1/1] virtio-blk: avoid preallocating big SGL for data Max Gurtovoy
2021-09-01 14:50 ` Michael S. Tsirkin
2021-09-01 14:58 ` Max Gurtovoy
2021-09-01 15:27 ` Jens Axboe
2021-09-01 22:25 ` Max Gurtovoy
2021-09-02 2:08 ` Jens Axboe
2021-09-02 12:21 ` Stefan Hajnoczi [this message]
2021-09-02 12:41 ` Max Gurtovoy
2021-09-06 15:09 ` Stefan Hajnoczi
2021-09-10 6:32 ` Feng Li
2021-09-13 14:50 ` Max Gurtovoy
2021-09-14 12:22 ` Stefan Hajnoczi
2021-09-23 13:40 ` Max Gurtovoy
2021-09-23 15:37 ` Michael S. Tsirkin
2021-10-22 9:15 ` Michael S. Tsirkin
2021-10-24 14:31 ` Max Gurtovoy
2021-09-27 11:59 ` Christoph Hellwig
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=YTDBx/E/UJZWTFlG@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=israelr@nvidia.com \
--cc=kvm@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=mgurtovoy@nvidia.com \
--cc=mst@redhat.com \
--cc=nitzanc@nvidia.com \
--cc=oren@nvidia.com \
--cc=virtualization@lists.linux-foundation.org \
/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).