From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: Heng Qi <hengqi@linux.alibaba.com>,
Jason Wang <jasowang@redhat.com>,
Yuri Benditovich <yuri.benditovich@daynix.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
"virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>
Subject: Re: [virtio-dev] RE: [PATCH v15] virtio-net: support inner header hash
Date: Thu, 8 Jun 2023 10:47:32 -0400 [thread overview]
Message-ID: <20230608104710-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB54819986416B73C860DF7A76DC50A@PH0PR12MB5481.namprd12.prod.outlook.com>
On Thu, Jun 08, 2023 at 02:45:15PM +0000, Parav Pandit wrote:
>
> > From: Michael S. Tsirkin <mst@redhat.com>
> > Sent: Thursday, June 8, 2023 10:42 AM
>
> > > > 2. hand over to RSS the ability to specify a hash based on the outer source
> > port.
> > > > That is, we can add VIRTIO_NET_RSS_HASH_TUNNEL_SRC_PORT_UDP_{v4,
> > v6,
> > > > EX} in \field{supported_hash_types} to indicate that the hash should
> > > > be calculated using the outer source port for all UDP tunneling protocols.
> > > > This approach removes the need for \field{hash_option} and makes the
> > > > line between VIRTIO_NET_F_HASH_TUNNEL and VIRTIO_NET_F_RSS clearer.
> > > >
> > > #2 is preferred.
> > >
> > > But I must be missing something.
> > > Without VIRTIO_NET_RSS_HASH_TUNNEL_SRC_PORT_UDP_X, today if one
> > wants
> > > to do RSS based on the outer UDP ports, It is already supported by the RSS
> > (even in presence of the inner header).
> > >
> > > So why do have to introduce
> > VIRTIO_NET_RSS_HASH_TUNNEL_SRC_PORT_UDP_X?
> >
> > they want an option to ignore all other header fields.
>
> Than that looks like rss config extension on which fields of the packet to use for RSS.
yes, but also, only for specific packet type and dest port #s.
--
MST
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2023-06-08 14:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 7:16 [virtio-dev] [PATCH v15] virtio-net: support inner header hash Heng Qi
2023-06-07 19:55 ` [virtio-dev] " Parav Pandit
2023-06-08 6:40 ` Heng Qi
2023-06-08 14:26 ` Parav Pandit
2023-06-08 14:41 ` Michael S. Tsirkin
2023-06-08 14:45 ` Parav Pandit
2023-06-08 14:47 ` Michael S. Tsirkin [this message]
2023-06-08 15:29 ` Heng Qi
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=20230608104710-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=hengqi@linux.alibaba.com \
--cc=jasowang@redhat.com \
--cc=parav@nvidia.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=xuanzhuo@linux.alibaba.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