From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: virtio-comment-return-1009-cohuck=redhat.com@lists.oasis-open.org Sender: List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 91091985EA0 for ; Mon, 20 Jan 2020 16:14:49 +0000 (UTC) Date: Mon, 20 Jan 2020 11:14:37 -0500 From: "Michael S. Tsirkin" Message-ID: <20200120111335-mutt-send-email-mst@kernel.org> References: <471210655.12237442.1575436801606.JavaMail.zimbra@redhat.com> <20191211113112-mutt-send-email-mst@kernel.org> <20191211130633-mutt-send-email-mst@kernel.org> <20191212023645-mutt-send-email-mst@kernel.org> <20191213021253-mutt-send-email-mst@kernel.org> <20191213033744-mutt-send-email-mst@kernel.org> MIME-Version: 1.0 In-Reply-To: <20191213033744-mutt-send-email-mst@kernel.org> Subject: Re: [virtio-comment] Re: [PATCH] virtio-net: define feature of per-packet RSS hash delivery Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Content-Disposition: inline To: Yuri Benditovich Cc: Yuri Benditovich , virtio-comment@lists.oasis-open.org List-ID: 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 wro= te: > > > > > > 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 looki= ng 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. > >=20 > > With RSS and hash delivery we're mainly targeting virtio-net in hardwar= e. > > Auto mq is much more complicated, correct? >=20 > 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 > > > >=20 >=20 > This publicly archived list offers a means to provide input to the > OASIS Virtual I/O Device (VIRTIO) TC. >=20 > In order to verify user consent to the Feedback License terms and > to minimize spam in the list archive, subscription is required > before posting. >=20 > 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-l= ists > 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=0D OASIS Virtual I/O Device (VIRTIO) TC.=0D =0D In order to verify user consent to the Feedback License terms and=0D to minimize spam in the list archive, subscription is required=0D before posting.=0D =0D Subscribe: virtio-comment-subscribe@lists.oasis-open.org=0D Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org=0D List help: virtio-comment-help@lists.oasis-open.org=0D List archive: https://lists.oasis-open.org/archives/virtio-comment/=0D Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf= =0D List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lis= ts=0D Committee: https://www.oasis-open.org/committees/virtio/=0D Join OASIS: https://www.oasis-open.org/join/