From: Heng Qi <hengqi@linux.alibaba.com>
To: Parav Pandit <parav@nvidia.com>
Cc: "Michael S . Tsirkin" <mst@redhat.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>,
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: Fri, 17 Mar 2023 16:38:47 +0800 [thread overview]
Message-ID: <10394600-28fa-b25b-c82d-5a541609912c@linux.alibaba.com> (raw)
In-Reply-To: <PH0PR12MB5481E500DF200DD258C151BFDCBC9@PH0PR12MB5481.namprd12.prod.outlook.com>
在 2023/3/17 上午3:55, Parav Pandit 写道:
>> From: Heng Qi <hengqi@linux.alibaba.com>
>> Sent: Thursday, March 16, 2023 9:39 AM
>> A rough description of this scene is as follows:
>> Client1 sends packets to client2, and client2 sends packets to client1
>> respectively.
>> This is called two directions, and they are in the same flow.
>> The packets in the two directions may reach the processing host through
>> different tunnels. In this scenario, we need to hash these packets to the same
>> queue for the same cpu to process, so inner symmetric hashing is required.
>>
>>
>> client1 client2
>> | |
>> | __________ |
>> +----->| tunnels |<-------+
>> |---------|
>> | |
>> | |
>> | |
>> v v
>> +-----------------+
>> | processing host |
>> +-----------------+
>>
> I understood now. The key piece is the processing host is different from clients 1 and 2, I was missing that.
> The key is there are two tunnels and processing data on the inner header for the different tunnels is your primary requirement.
> Hence inner hashing helps to serialize them.
Yes, you are right.
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
prev parent reply other threads:[~2023-03-17 8:38 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 ` [virtio-dev] " Heng Qi
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 [this message]
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=10394600-28fa-b25b-c82d-5a541609912c@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).