From: "Michael S. Tsirkin" <mst@redhat.com>
To: Yuri Benditovich <yuri.benditovich@daynix.com>
Cc: Yan Vugenfirer <yan@daynix.com>, Jason Wang <jasowang@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH 0/3] reference implementation of RSS
Date: Sun, 8 Mar 2020 04:06:30 -0400 [thread overview]
Message-ID: <20200308040540-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAOEp5OfPkQsWs=kYzwxHA0t_gv0iFb4OD6Wppde+qo42wr-eGg@mail.gmail.com>
On Fri, Mar 06, 2020 at 11:50:30AM +0200, Yuri Benditovich wrote:
>
>
> On Fri, Mar 6, 2020 at 11:27 AM Jason Wang <jasowang@redhat.com> wrote:
>
>
> On 2020/2/27 上午1:48, Yuri Benditovich wrote:
> > Support for VIRTIO_NET_F_RSS feature in QEMU for reference
> > purpose. Implements Toeplitz hash calculation for incoming
> > packets according to configuration provided by driver.
> >
> > This series requires previously submitted and accepted
> > patch to be applied:
> > https://lists.gnu.org/archive/html/qemu-devel/2020-01/msg06448.html
> >
> > Yuri Benditovich (3):
> > virtio-net: introduce RSS RX steering feature
> > virtio-net: implement RSS configuration command
> > virtio-net: implement RX RSS processing
> >
> > hw/net/trace-events | 3 +
> > hw/net/virtio-net.c | 234
> +++++++++++++++++++-VIRTIO_NET_F_RSS
> > include/hw/virtio/virtio-net.h | 12 +
> > include/standard-headers/linux/virtio_net.h | 37 +++-
> > 4 files changed, 273 insertions(+), 13 deletions(-)
> >
>
> One question before the reviewing.
>
> Do we need to deal with migration (which I think yes)?
>
>
> I think we don't (yet) as this is a reference implementation and the main goal
> is to provide the functional reference for hardware solution.
That's fine, but then we must block migration, and add appropriate code
comments. Just silently losing data isn't a good idea.
> I agree with the general direction that for complete support of RSS and hash
> delivery the best way is to do that in kernel using bpf.
> For that, IMO, the bpf should be a part of the kernel (it uses skb fields) and
> the tap should receive just RSS parameters for it.
> At this stage we definitely will need to add migration support and propagation
> of RSS parameters.
>
>
>
> Thanks
>
>
next prev parent reply other threads:[~2020-03-08 8:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 17:48 [PATCH 0/3] reference implementation of RSS Yuri Benditovich
2020-02-26 17:48 ` [PATCH 1/3] virtio-net: introduce RSS RX steering feature Yuri Benditovich
2020-03-05 13:21 ` Michael S. Tsirkin
2020-03-06 9:29 ` Yuri Benditovich
2020-03-06 10:25 ` Michael S. Tsirkin
2020-02-26 17:48 ` [PATCH 2/3] virtio-net: implement RSS configuration command Yuri Benditovich
2020-02-26 17:48 ` [PATCH 3/3] virtio-net: implement RX RSS processing Yuri Benditovich
2020-03-05 13:20 ` Michael S. Tsirkin
2020-03-05 19:54 ` Yuri Benditovich
2020-03-05 20:02 ` Michael S. Tsirkin
2020-03-05 21:04 ` Yuri Benditovich
2020-03-05 12:57 ` [PATCH 0/3] reference implementation of RSS Yuri Benditovich
2020-03-06 9:27 ` Jason Wang
2020-03-06 9:50 ` Yuri Benditovich
2020-03-08 8:06 ` Michael S. Tsirkin [this message]
2020-03-08 9:56 ` Yuri Benditovich
2020-03-08 12:17 ` Michael S. Tsirkin
2020-03-08 12:44 ` Yuri Benditovich
2020-03-08 13:15 ` Michael S. Tsirkin
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=20200308040540-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
--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 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).