From: Heng Qi <hengqi@linux.alibaba.com>
To: Parav Pandit <parav@nvidia.com>, "Michael S. Tsirkin" <mst@redhat.com>
Cc: Alvaro Karsz <alvaro.karsz@solid-run.com>,
"virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
Jason Wang <jasowang@redhat.com>,
Yuri Benditovich <yuri.benditovich@daynix.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Subject: Re: [virtio-dev] Re: [PATCH v11] virtio-net: support inner header hash
Date: Thu, 23 Mar 2023 13:03:20 +0800 [thread overview]
Message-ID: <56b924db-574f-5d8e-125b-a51c45871b10@linux.alibaba.com> (raw)
In-Reply-To: <57e1cc23-ad1e-2105-20cc-35f2130dd9d0@linux.alibaba.com>
在 2023/3/23 上午11:58, Heng Qi 写道:
>
>
> 在 2023/3/23 上午11:13, Parav Pandit 写道:
>>> From: Michael S. Tsirkin <mst@redhat.com>
>>> Sent: Wednesday, March 22, 2023 12:42 PM
>>> Yes. But my point is this. Some flows can be IPv4 others IPv6.
>>> Do you see a way to have a key that will result in a symmetrical
>>> hash for both
>>> IPv4 and IPv6? Can you give an example please?
>>>
>> Heng,
>>
>> Is that the requirement to have two completely different flows (ipv,
>> ipv6) to steer to a single RQ?
>
> Michael should be talking about whether there is a symmetric key that
> can serve both IPv4 and IPv6, so that they can respectively achieve
> the purpose of symmetric hashing.
> I am not an expert in hashing, but this article [1] deduces a
> symmetric hash key, and I think it should be possible to deduce a
> specific key to meet this requirement.
Sorry for the lost link:
[1] https://www.ndsl.kaist.edu/~kyoungsoo/papers/TR-symRSS.pdf
>
> Or we should support XOR hashing.
>
> Thanks.
>
>> The requirement, what I understood, is between two directions for a
>> flow to result in a single hash value.
>
>
> ---------------------------------------------------------------------
> 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-23 5:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 11:18 [virtio-dev] [PATCH v11] virtio-net: support inner header hash Heng Qi
2023-03-20 19:43 ` [virtio-dev] " Michael S. Tsirkin
2023-03-20 21:07 ` Michael S. Tsirkin
2023-03-21 3:35 ` Jason Wang
2023-03-21 5:12 ` Heng Qi
2023-03-21 3:56 ` Heng Qi
2023-03-21 4:19 ` Parav Pandit
2023-03-21 7:37 ` Michael S. Tsirkin
2023-03-21 19:46 ` Parav Pandit
2023-03-21 21:32 ` Michael S. Tsirkin
2023-03-21 7:34 ` Michael S. Tsirkin
2023-03-21 14:49 ` Heng Qi
2023-03-21 15:58 ` Michael S. Tsirkin
2023-03-22 12:49 ` Heng Qi
2023-03-22 16:42 ` Michael S. Tsirkin
2023-03-23 3:13 ` Parav Pandit
2023-03-23 3:58 ` Heng Qi
2023-03-23 5:03 ` Heng Qi [this message]
2023-03-23 2:52 ` Jason Wang
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=56b924db-574f-5d8e-125b-a51c45871b10@linux.alibaba.com \
--to=hengqi@linux.alibaba.com \
--cc=alvaro.karsz@solid-run.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).