From: Parav Pandit <parav@nvidia.com>
To: "virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
"mst@redhat.com" <mst@redhat.com>,
"cohuck@redhat.com" <cohuck@redhat.com>
Cc: "sburla@marvell.com" <sburla@marvell.com>,
Shahaf Shuler <shahafs@nvidia.com>,
"si-wei.liu@oracle.com" <si-wei.liu@oracle.com>,
"xuanzhuo@linux.alibaba.com" <xuanzhuo@linux.alibaba.com>
Subject: [virtio-comment] RE: [PATCH v2 0/6] virtio-net: Support flow filter for receive packets
Date: Thu, 26 Oct 2023 06:11:24 +0000 [thread overview]
Message-ID: <PH0PR12MB548100F6C19423923547CD22DCDDA@PH0PR12MB5481.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20231020123303.1209289-1-parav@nvidia.com>
> From: Parav Pandit <parav@nvidia.com>
> Sent: Friday, October 20, 2023 6:03 PM
> To: virtio-comment@lists.oasis-open.org; mst@redhat.com;
> cohuck@redhat.com
> Cc: sburla@marvell.com; Shahaf Shuler <shahafs@nvidia.com>; si-
> wei.liu@oracle.com; xuanzhuo@linux.alibaba.com; Parav Pandit
> <parav@nvidia.com>
> Subject: [PATCH v2 0/6] virtio-net: Support flow filter for receive packets
>
> Summary:
> ========
> This series improves virtio net receive packet steering to forward/steer packets
> to specific RQ.
>
> This basic functionality will enable Linux ethtool steering, Accelerated receive
> flow steering (ARFS) as starting point, and more use cases in future.
>
> Problem statement:
> ==================
> Currently packet allow/drop interface has few limitations.
>
> 1. Driver cannot add or delete an individual entry for mac and vlan.
> 2. Driver cannot select mac+vlan combination for which
> to allow/drop packet.
> 3. Driver cannot not set other commonly used packet match fields
> such as IP header fields, TCP, UDP, SCP header fields.
> 4. Driver cannot steer specific packets based on the match
> fields to specific receiveq.
> 5. Driver do not have multiple or dedicated virtqueues to
> perform flow filter requests in accelerated manner in
> the device.
>
> Solution:
> =========
> Flow filter as a generic framework to overcome above limitations.
>
> Overview:
> =========
> A flow filter defines the flow based on one or more match fields of the packet,
> defines an action like drop/forward to RQ.
>
> The flow filters are organized in flow filter groups so that their processing can be
> ordered when multiple applications wants to use it.
>
> Flow filters requests can be transported via control vq or dedicated flow filter
> virtqueue so that it does not get intermixed with other slow operations of cvq.
>
> Flow filter requirements addressed by this series is worked by virtio community
> at [1].
>
> Fixes: https://github.com/oasis-tcs/virtio-spec/issues/179
>
> This series utilizes enhancements proposed in [2] and [3].
> It uses updated control vq command format from [3].
> It uses new _DYNAMIC feature to create queues when needed and saves guest
> and device resources.
>
> [1] https://lists.oasis-open.org/archives/virtio-
> comment/202308/msg00263.html
> [2] https://lists.oasis-open.org/archives/virtio-
> comment/202310/msg00183.html
> [3] https://lists.oasis-open.org/archives/virtio-
> comment/202310/msg00047.html
I will rebase this series without depending on [2] which was abusing the init time register for dynamic things.
Please hold your review in the text around dynamic flow filter vqs until v3 of this series.
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/
prev parent reply other threads:[~2023-10-26 6:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 12:32 [virtio-comment] [PATCH v2 0/6] virtio-net: Support flow filter for receive packets Parav Pandit
2023-10-20 12:32 ` [virtio-comment] [PATCH v2 1/6] virtio-net: Add theory of operation for flow filter Parav Pandit
2023-10-20 12:32 ` [virtio-comment] [PATCH v2 2/6] virtio-net: Add flow filter capabilities read commands Parav Pandit
2023-10-20 12:33 ` [virtio-comment] [PATCH v2 3/6] virtio-net: Add flow filter group life cycle commands Parav Pandit
2023-10-20 12:33 ` [virtio-comment] [PATCH v2 4/6] virtio-net: Add flow filter transport set command Parav Pandit
2023-10-20 12:33 ` [virtio-comment] [PATCH v2 5/6] virtio-net: Add flow filter match entry, action and requests Parav Pandit
2023-10-20 12:33 ` [virtio-comment] [PATCH v2 6/6] virtio-net: Add flow filter device and driver requirements Parav Pandit
2023-10-26 6:11 ` Parav Pandit [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=PH0PR12MB548100F6C19423923547CD22DCDDA@PH0PR12MB5481.namprd12.prod.outlook.com \
--to=parav@nvidia.com \
--cc=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=sburla@marvell.com \
--cc=shahafs@nvidia.com \
--cc=si-wei.liu@oracle.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=xuanzhuo@linux.alibaba.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).