From: Heng Qi <hengqi@linux.alibaba.com>
To: Parav Pandit <parav@nvidia.com>, "Michael S. Tsirkin" <mst@redhat.com>
Cc: virtio-dev@lists.oasis-open.org,
virtio-comment@lists.oasis-open.org,
Jason Wang <jasowang@redhat.com>,
Yuri Benditovich <yuri.benditovich@daynix.com>,
Cornelia Huck <cohuck@redhat.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Subject: Re: [virtio-dev] Re: [virtio-comment] Re: [PATCH v10] virtio-net: support inner header hash
Date: Thu, 16 Mar 2023 21:45:27 +0800 [thread overview]
Message-ID: <e8554f9d-ebb7-5b3e-ec40-a674921775c3@linux.alibaba.com> (raw)
In-Reply-To: <11cce86e-8068-2e83-9fc5-e1b825adde29@nvidia.com>
在 2023/3/16 上午7:24, Parav Pandit 写道:
>
> On 3/15/2023 8:10 AM, Michael S. Tsirkin wrote:
>> On Tue, Mar 14, 2023 at 11:23:55PM -0400, Parav Pandit wrote:
>>> If not, for now it may be better to skip vxlan and nvegre as they
>>> inherently
>>> have unique outer header UDP src port based on the inner header.
>>
>> So what's left, GRE? GRE is actually different, in that it's not IP at
>> all.
> Sorry, I wrongly wrote nvegre above.
>
> IPoIP, GRE and NVGRE are left.
>
> vxlan and geneve has the udp src entropy.
>
>>
> Not sure I understand "its not IP at all".
>
> GRE has outer IP header + GRE header with the key to identify the flow.
> The key is effectively the hash for the flow.
>
>> So if we are talking about GRE, hash is indeed not calculated at all at
>> the moment, right?
> Hash of the outer IP header of the src and dst IP can be still
> calculated currently for GRE when the optional key is not present.
>
>> And I would say a natural first step for GRE is
>> actually adding a hash type that will support this protocol.
>>
> For GRE and NVGRE GRE_header.key as the flow/hash identifier should
> work without inner header hash.
> Older version of the GRE doesn't have key, so inner header hash is
> useful.
Yes, indeed.
The old GRE does not have keys such as flow id. Even with the new GRE,
we have no chance to use optional fields,
because we have connected with various operators, and the most basic
fields can get the best compatibility.
Thanks.
>
>> How about doing that? It seems like this should be a small step
>> and completely uncontroversial.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
---------------------------------------------------------------------
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-03-16 13:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 15:48 [virtio-dev] [PATCH v10] virtio-net: support inner header hash Heng Qi
2023-03-08 14:27 ` Heng Qi
2023-03-08 14:31 ` Michael S. Tsirkin
2023-03-14 13:59 ` [virtio-dev] " Heng Qi
2023-03-15 3:23 ` Parav Pandit
2023-03-15 12:10 ` [virtio-dev] Re: [virtio-comment] " Michael S. Tsirkin
2023-03-15 13:27 ` Heng Qi
2023-03-15 23:24 ` Parav Pandit
2023-03-16 7:36 ` Michael S. Tsirkin
2023-03-16 18:45 ` [virtio-dev] " Parav Pandit
2023-03-16 13:45 ` Heng Qi [this message]
2023-03-15 13:19 ` [virtio-dev] " Heng Qi
2023-03-15 15:09 ` Michael S. Tsirkin
2023-03-16 13:26 ` Heng Qi
2023-03-15 23:06 ` Parav Pandit
2023-03-16 13:38 ` [virtio-dev] Re: [virtio-comment] " Heng Qi
2023-03-16 19:55 ` [virtio-dev] " Parav Pandit
2023-03-17 8:38 ` 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=e8554f9d-ebb7-5b3e-ec40-a674921775c3@linux.alibaba.com \
--to=hengqi@linux.alibaba.com \
--cc=cohuck@redhat.com \
--cc=jasowang@redhat.com \
--cc=mst@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