From: "Michael S. Tsirkin" <mst@redhat.com>
To: Yuri Benditovich <yuri.benditovich@daynix.com>
Cc: yan@daynix.com, jasowang@redhat.com, qemu-devel@nongnu.org,
dgilbert@redhat.com, quintela@redhat.com
Subject: Re: [PATCH v5 0/7] reference implementation of RSS and hash report
Date: Wed, 18 Mar 2020 05:43:07 -0400 [thread overview]
Message-ID: <20200318054245-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20200318091525.27044-1-yuri.benditovich@daynix.com>
On Wed, Mar 18, 2020 at 11:15:18AM +0200, Yuri Benditovich wrote:
> Support for VIRTIO_NET_F_RSS and VIRTIO_NET_F_HASH_REPORT
> features in QEMU for reference purpose.
> Implements Toeplitz hash calculation for incoming
> packets according to configuration provided by driver.
> Uses calculated hash for decision on receive virtqueue
> and/or reports the hash in the virtio header
>
> Changes from v4
> Use 16-bit field for indirection table length (patch 2)
> Add VMSTATE_VARRAY_UINT16_ALLOC for migration of
> indirection table (patch 6)
Attribution on 6/7 seems to be wrong. Except for that:
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
> Yuri Benditovich (7):
> virtio-net: introduce RSS and hash report features
> virtio-net: implement RSS configuration command
> virtio-net: implement RX RSS processing
> tap: allow extended virtio header with hash info
> virtio-net: reference implementation of hash report
> vmstate.h: provide VMSTATE_VARRAY_UINT16_ALLOC macro
> virtio-net: add migration support for RSS and hash report
>
> hw/net/trace-events | 3 +
> hw/net/virtio-net.c | 437 +++++++++++++++++++++++++++++++--
> include/hw/virtio/virtio-net.h | 16 ++
> include/migration/vmstate.h | 10 +
> net/tap.c | 11 +-
> 5 files changed, 449 insertions(+), 28 deletions(-)
>
> --
> 2.17.1
next prev parent reply other threads:[~2020-03-18 9:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 9:15 [PATCH v5 0/7] reference implementation of RSS and hash report Yuri Benditovich
2020-03-18 9:15 ` [PATCH v5 1/7] virtio-net: introduce RSS and hash report features Yuri Benditovich
2020-03-18 9:15 ` [PATCH v5 2/7] virtio-net: implement RSS configuration command Yuri Benditovich
2020-03-18 9:15 ` [PATCH v5 3/7] virtio-net: implement RX RSS processing Yuri Benditovich
2020-03-18 9:15 ` [PATCH v5 4/7] tap: allow extended virtio header with hash info Yuri Benditovich
2020-03-18 9:15 ` [PATCH v5 5/7] virtio-net: reference implementation of hash report Yuri Benditovich
2020-03-18 9:15 ` [PATCH v5 6/7] vmstate.h: provide VMSTATE_VARRAY_UINT16_ALLOC macro Yuri Benditovich
2020-03-18 9:42 ` Michael S. Tsirkin
2020-03-19 17:12 ` Yuri Benditovich
2020-03-19 17:55 ` Michael S. Tsirkin
2020-03-18 11:00 ` Dr. David Alan Gilbert
2020-03-18 13:02 ` Juan Quintela
2020-03-18 15:19 ` Michael S. Tsirkin
2020-03-18 9:15 ` [PATCH v5 7/7] virtio-net: add migration support for RSS and hash report Yuri Benditovich
2020-03-18 10:48 ` Dr. David Alan Gilbert
2020-03-19 17:19 ` Yuri Benditovich
2020-03-19 17:23 ` Michael S. Tsirkin
2020-03-19 17:58 ` Juan Quintela
2020-03-19 18:09 ` Dr. David Alan Gilbert
2020-03-18 9:43 ` Michael S. Tsirkin [this message]
2020-03-18 9:53 ` [PATCH v5 0/7] reference implementation of " no-reply
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=20200318054245-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=yan@daynix.com \
--cc=yuri.benditovich@daynix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.