From: "Michael S. Tsirkin" <mst@redhat.com>
To: Hawkins Jiawei <yin31149@gmail.com>
Cc: jasowang@redhat.com, eperezma@redhat.com, qemu-devel@nongnu.org,
18801353760@163.com
Subject: Re: [PATCH v3 0/3] Vhost-vdpa Shadow Virtqueue RSS Support
Date: Thu, 19 Oct 2023 14:12:09 -0400 [thread overview]
Message-ID: <20231019141200-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <cover.1693299194.git.yin31149@gmail.com>
On Tue, Aug 29, 2023 at 05:11:14PM +0800, Hawkins Jiawei wrote:
> This series enables shadowed CVQ to intercept RSS command
> through shadowed CVQ, update the virtio NIC device model
> so qemu send it in a migration, and the restore of that
> RSS state in the destination.
>
> Note that this patch should be based on
> patch "Vhost-vdpa Shadow Virtqueue Hash calculation Support" at [1].
>
> [1]. https://lore.kernel.org/all/cover.1693297766.git.yin31149@gmail.com/
dropped due to dependency.
> TestStep
> ========
> 1. test the migration using vp-vdpa device
> - For L0 guest, boot QEMU with two virtio-net-pci net device with
> `in-qemu` RSS, command line like:
> -netdev tap,vhost=off...
> -device virtio-net-pci,disable-legacy=on,disable-modern=off,
> iommu_platform=on,mq=on,ctrl_vq=on,hash=on,rss=on,guest_announce=off,
> indirect_desc=off,queue_reset=off,...
>
> - For L1 guest, apply the relative patch series and compile the
> source code, start QEMU with two vdpa device with svq mode on,
> enable the `ctrl_vq`, `mq`, `rss` features on, command line like:
> -netdev type=vhost-vdpa,x-svq=true,...
> -device virtio-net-pci,mq=on,guest_announce=off,ctrl_vq=on,
> rss=on,...
>
> - For L2 source guest, run the following bash command:
> ```bash
> #!/bin/sh
>
> ethtool -K eth0 rxhash on
> ```
>
> - Execute the live migration in L2 source monitor
>
> - Result
> * with this series, L2 QEMU can execute without
> triggering any error or warning. L0 QEMU echo
> "Can't load eBPF RSS - fallback to software RSS".
>
> ChangeLog
> =========
> v3:
> - resolve conflict with updated patch
> "Vhost-vdpa Shadow Virtqueue Hash calculation Support" in patch
> "vdpa: Restore receive-side scaling state"
>
> RFC v2: https://lore.kernel.org/all/cover.1691926415.git.yin31149@gmail.com/
> - Correct the feature usage to VIRTIO_NET_F_HASH_REPORT when
> loading the hash calculation state in
> patch "vdpa: Restore receive-side scaling state"
>
> RFC v1: https://lore.kernel.org/all/cover.1691766252.git.yin31149@gmail.com/
>
> Hawkins Jiawei (3):
> vdpa: Add SetSteeringEBPF method for NetClientState
> vdpa: Restore receive-side scaling state
> vdpa: Allow VIRTIO_NET_F_RSS in SVQ
>
> net/vhost-vdpa.c | 63 ++++++++++++++++++++++++++++++++++--------------
> 1 file changed, 45 insertions(+), 18 deletions(-)
>
> --
> 2.25.1
prev parent reply other threads:[~2023-10-19 18:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 9:11 [PATCH v3 0/3] Vhost-vdpa Shadow Virtqueue RSS Support Hawkins Jiawei
2023-08-29 9:11 ` [PATCH v3 1/3] vdpa: Add SetSteeringEBPF method for NetClientState Hawkins Jiawei
2023-08-29 9:11 ` [PATCH v3 2/3] vdpa: Restore receive-side scaling state Hawkins Jiawei
2023-08-29 9:11 ` [PATCH v3 3/3] vdpa: Allow VIRTIO_NET_F_RSS in SVQ Hawkins Jiawei
2023-10-19 18:12 ` Michael S. Tsirkin [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=20231019141200-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=18801353760@163.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yin31149@gmail.com \
/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).