From: Cornelia Huck <cohuck@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
Heng Qi <hengqi@linux.alibaba.com>
Cc: virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org, Parav Pandit <parav@nvidia.com>,
Jason Wang <jasowang@redhat.com>,
Yuri Benditovich <yuri.benditovich@daynix.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Subject: [virtio-comment] Re: [PATCH v21] virtio-net: support inner header hash
Date: Tue, 04 Jul 2023 08:56:34 +0200 [thread overview]
Message-ID: <87cz18i2ql.fsf@redhat.com> (raw)
In-Reply-To: <20230703114640-mutt-send-email-mst@kernel.org>
On Mon, Jul 03 2023, "Michael S. Tsirkin" <mst@redhat.com> wrote:
> On Mon, Jul 03, 2023 at 11:27:11PM +0800, Heng Qi wrote:
>> 1. Currently, a received encapsulated packet has an outer and an inner header, but
>> the virtio device is unable to calculate the hash for the inner header. The same
>> flow can traverse through different tunnels, resulting in the encapsulated
>> packets being spread across multiple receive queues (refer to the figure below).
>> However, in certain scenarios, we may need to direct these encapsulated packets of
>> the same flow to a single receive queue. This facilitates the processing
>> of the flow by the same CPU to improve performance (warm caches, less locking, etc.).
>>
>> client1 client2
>> | +-------+ |
>> +------->|tunnels|<--------+
>> +-------+
>> | |
>> v v
>> +-----------------+
>> | monitoring host |
>> +-----------------+
>>
>> To achieve this, the device can calculate a symmetric hash based on the inner headers
>> of the same flow.
>>
>> 2. For legacy systems, they may lack entropy fields which modern protocols have in
>> the outer header, resulting in multiple flows with the same outer header but
>> different inner headers being directed to the same receive queue. This results in
>> poor receive performance.
>>
>> To address this limitation, inner header hash can be used to enable the device to advertise
>> the capability to calculate the hash for the inner packet, regaining better receive performance.
>>
>> Fixes: https://github.com/oasis-tcs/virtio-spec/issues/173
>> Signed-off-by: Heng Qi <hengqi@linux.alibaba.com>
>> Reviewed-by: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
>> Reviewed-by: Parav Pandit <parav@nvidia.com>
>
> Cornelia last minute comments before I start a vote?
Please just go ahead.
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
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-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
WARNING: multiple messages have this Message-ID (diff)
From: Cornelia Huck <cohuck@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
Heng Qi <hengqi@linux.alibaba.com>
Cc: virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org, Parav Pandit <parav@nvidia.com>,
Jason Wang <jasowang@redhat.com>,
Yuri Benditovich <yuri.benditovich@daynix.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Subject: [virtio-dev] Re: [PATCH v21] virtio-net: support inner header hash
Date: Tue, 04 Jul 2023 08:56:34 +0200 [thread overview]
Message-ID: <87cz18i2ql.fsf@redhat.com> (raw)
In-Reply-To: <20230703114640-mutt-send-email-mst@kernel.org>
On Mon, Jul 03 2023, "Michael S. Tsirkin" <mst@redhat.com> wrote:
> On Mon, Jul 03, 2023 at 11:27:11PM +0800, Heng Qi wrote:
>> 1. Currently, a received encapsulated packet has an outer and an inner header, but
>> the virtio device is unable to calculate the hash for the inner header. The same
>> flow can traverse through different tunnels, resulting in the encapsulated
>> packets being spread across multiple receive queues (refer to the figure below).
>> However, in certain scenarios, we may need to direct these encapsulated packets of
>> the same flow to a single receive queue. This facilitates the processing
>> of the flow by the same CPU to improve performance (warm caches, less locking, etc.).
>>
>> client1 client2
>> | +-------+ |
>> +------->|tunnels|<--------+
>> +-------+
>> | |
>> v v
>> +-----------------+
>> | monitoring host |
>> +-----------------+
>>
>> To achieve this, the device can calculate a symmetric hash based on the inner headers
>> of the same flow.
>>
>> 2. For legacy systems, they may lack entropy fields which modern protocols have in
>> the outer header, resulting in multiple flows with the same outer header but
>> different inner headers being directed to the same receive queue. This results in
>> poor receive performance.
>>
>> To address this limitation, inner header hash can be used to enable the device to advertise
>> the capability to calculate the hash for the inner packet, regaining better receive performance.
>>
>> Fixes: https://github.com/oasis-tcs/virtio-spec/issues/173
>> Signed-off-by: Heng Qi <hengqi@linux.alibaba.com>
>> Reviewed-by: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
>> Reviewed-by: Parav Pandit <parav@nvidia.com>
>
> Cornelia last minute comments before I start a vote?
Please just go ahead.
---------------------------------------------------------------------
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-07-04 6:56 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 15:27 [virtio-comment] [PATCH v21] virtio-net: support inner header hash Heng Qi
2023-07-03 15:27 ` [virtio-dev] " Heng Qi
2023-07-03 15:47 ` [virtio-comment] " Michael S. Tsirkin
2023-07-03 15:47 ` [virtio-dev] " Michael S. Tsirkin
2023-07-04 6:56 ` Cornelia Huck [this message]
2023-07-04 6:56 ` Cornelia Huck
2023-07-12 12:22 ` [virtio-comment] " Cornelia Huck
2023-07-12 12:22 ` [virtio-dev] " Cornelia Huck
2023-07-12 12:25 ` [virtio-comment] " Michael S. Tsirkin
2023-07-12 12:25 ` [virtio-dev] " Michael S. Tsirkin
2023-07-12 12:42 ` [virtio-comment] " Cornelia Huck
2023-07-12 12:42 ` [virtio-dev] " Cornelia Huck
2023-07-12 12:59 ` [virtio-comment] " Heng Qi
2023-07-12 12:59 ` [virtio-dev] " Heng Qi
2023-07-12 13:25 ` Cornelia Huck
2023-07-12 13:25 ` [virtio-dev] " Cornelia Huck
2023-07-12 14:54 ` [virtio-comment] " Heng Qi
2023-07-12 14:54 ` Heng Qi
2023-07-12 15:23 ` [virtio-comment] " Cornelia Huck
2023-07-12 15:23 ` [virtio-dev] " Cornelia Huck
2023-07-12 16:52 ` Parav Pandit
2023-07-12 16:52 ` [virtio-dev] " Parav Pandit
2023-07-12 22:28 ` Parav Pandit
2023-07-12 22:28 ` [virtio-dev] " Parav Pandit
2023-07-12 22:31 ` Michael S. Tsirkin
2023-07-12 22:31 ` [virtio-dev] " Michael S. Tsirkin
2023-07-12 22:35 ` Parav Pandit
2023-07-12 22:35 ` [virtio-dev] " Parav Pandit
2023-07-13 6:40 ` Heng Qi
2023-07-13 6:40 ` [virtio-dev] " 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=87cz18i2ql.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=hengqi@linux.alibaba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.