From: "Michael S. Tsirkin" <mst@redhat.com>
To: Yuri Benditovich <yuri.benditovich@daynix.com>
Cc: Yuri Benditovich <ybendito@redhat.com>,
virtio-comment@lists.oasis-open.org
Subject: Re: [virtio-comment] Re: [PATCH] virtio-net: define feature of per-packet RSS hash delivery
Date: Mon, 20 Jan 2020 11:14:37 -0500 [thread overview]
Message-ID: <20200120111335-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20191213033744-mutt-send-email-mst@kernel.org>
On Fri, Dec 13, 2019 at 03:38:11AM -0500, Michael S. Tsirkin wrote:
> On Fri, Dec 13, 2019 at 10:21:53AM +0200, Yuri Benditovich wrote:
> > On Fri, Dec 13, 2019 at 9:16 AM Michael S. Tsirkin <mst@redhat.com> wrote:
> > >
> > > On Fri, Dec 13, 2019 at 06:34:39AM +0200, Yuri Benditovich wrote:
> > > >
> > > > So there are 2 possible profiles of devices that 'do not have RSS' but
> > > > deliver hash:
> > > > 1. The device is in general can do RSS, but has only one pair of
> > > > queues and does only hash calculation
> > > > 2. The device has multiple queues but is configured to do auto
> > > > steering and we want also hash from it.
> > > >
> > > > My impression is that case 2 is rather academic one (at least looking forward).
> > > > Do you agree?
> > >
> > > I am not sure I agree. auto mq is much easier to configure than RSS
> > > so I image it's useful even if one wants hash.
> >
> > With RSS and hash delivery we're mainly targeting virtio-net in hardware.
> > Auto mq is much more complicated, correct?
>
> Hardware implementing it exists, it's not too hard, just some tables
> to maintain.
So what is the resolution here? To me it seems easier to just allow
this than worry whether it's useful. And devices that do not
want to support some combinations, don't have to, right?
> > >
> > > --
> > > MST
> > >
>
>
> This publicly archived list offers a means to provide input to the
> OASIS Virtual I/O Device (VIRTIO) TC.
>
> In order to verify user consent to the Feedback License terms and
> to minimize spam in the list archive, subscription is required
> before posting.
>
> Subscribe: virtio-comment-subscribe@lists.oasis-open.org
> Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
> List help: virtio-comment-help@lists.oasis-open.org
> List archive: https://lists.oasis-open.org/archives/virtio-comment/
> Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
> List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
> Committee: https://www.oasis-open.org/committees/virtio/
> Join OASIS: https://www.oasis-open.org/join/
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
next prev parent reply other threads:[~2020-01-20 16:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 18:32 [virtio-comment] [PATCH] virtio-net: define feature of per-packet RSS hash delivery Yuri Benditovich
2019-12-03 20:25 ` [virtio-comment] " Michael S. Tsirkin
2019-12-04 5:20 ` Yuri Benditovich
2019-12-11 16:34 ` Michael S. Tsirkin
2019-12-11 17:41 ` Yuri Benditovich
2019-12-11 18:20 ` Michael S. Tsirkin
2019-12-12 3:48 ` Yuri Benditovich
2019-12-12 7:43 ` Michael S. Tsirkin
2019-12-13 4:34 ` Yuri Benditovich
2019-12-13 7:15 ` Michael S. Tsirkin
2019-12-13 8:21 ` Yuri Benditovich
2019-12-13 8:38 ` Michael S. Tsirkin
2020-01-20 16:14 ` Michael S. Tsirkin [this message]
2020-01-20 16:27 ` Yuri Benditovich
2020-01-20 22:00 ` 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=20200120111335-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=ybendito@redhat.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.