From: "Michael S. Tsirkin" <mst@redhat.com>
To: David Wei <dw@davidwei.uk>
Cc: Parav Pandit <parav@nvidia.com>,
virtio-comment@lists.linux.dev, cohuck@redhat.com,
hengqi@linux.alibaba.com, sburla@marvell.com, shahafs@nvidia.com,
si-wei.liu@oracle.com, peter.hilber@opensynergy.com,
jasowang@redhat.com, xuanzhuo@linux.alibaba.com
Subject: Re: [PATCH v11 00/13] flow filter using basic facilities of capability and resource objects
Date: Mon, 3 Mar 2025 14:59:38 -0500 [thread overview]
Message-ID: <20250303145911-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <691016c0-b8e4-48f0-a26b-45296102f501@davidwei.uk>
On Mon, Mar 03, 2025 at 11:10:12AM -0800, David Wei wrote:
> On 2024-06-04 06:28, Parav Pandit wrote:
> > Summary:
> > ========
> > This series improves virtio net receive packet steering to
> > direct packets to a specific RQ.
> >
> > This basic functionality will enable Linux ethtool steering,
> > and accelerated receive flow steering (ARFS) as a starting point,
> > and more use cases in future.
> >
> > It is using new virtio basic facilities of capability and
> > resource objects described later in this cover letter.
> >
> > Those interested only in the capability and resource object facilities
> > can jump in the cover leter to "Overview of capability and resource objects".
> >
>
> Hi folks, what is the state of this virtio spec update adding flow
> steering?
>
> I added io_uring zero copy receive which got merged recently. This
> feature requires hardware flow steering and RSS contexts to work. I'm
> targeting bnxt and mlx5 for real hardware support but would also like to
> add it to virtio. This will be useful for VMs as well as testing w/o
> needing real hardware.
>
> I checked https://github.com/oasis-tcs/virtio-spec but don't see the
> patches committed.
>
> Thanks,
> David
Given no one objects, the thing to do is to ask for a vote.
--
MST
next prev parent reply other threads:[~2025-03-03 19:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 13:28 [PATCH v11 00/13] flow filter using basic facilities of capability and resource objects Parav Pandit
2024-06-04 13:28 ` [PATCH v11 01/13] admin: Introduce self group Parav Pandit
2024-06-04 13:28 ` [PATCH v11 02/13] admin: Use already defined names for the legacy commands Parav Pandit
2024-06-04 13:28 ` [PATCH v11 03/13] admin: Add theory of operation for capability admin commands Parav Pandit
2024-06-04 13:28 ` [PATCH v11 04/13] admin: Prepare table for multipage listing Parav Pandit
2024-06-04 13:28 ` [PATCH v11 05/13] admin: Add capability admin commands Parav Pandit
2024-06-04 13:28 ` [PATCH v11 06/13] admin: Add theory of operation for device resource objects Parav Pandit
2024-06-04 13:28 ` [PATCH v11 07/13] admin: Add device resource objects admin commands Parav Pandit
2024-06-04 13:28 ` [PATCH v11 08/13] virtio-net: Add theory of operation for flow filter Parav Pandit
2024-06-04 13:28 ` [PATCH v11 09/13] virtio-net: Add flow filter capability Parav Pandit
2025-11-18 22:09 ` Michael S. Tsirkin
2025-11-19 3:31 ` Parav Pandit
2024-06-04 13:29 ` [PATCH v11 10/13] virtio-net: Add flow filter group, classifier and rule resource objects Parav Pandit
2024-06-04 13:29 ` [PATCH v11 11/13] virtio-net: Add flow filter device and driver requirements Parav Pandit
2024-06-04 13:29 ` [PATCH v11 12/13] newdevice: Improve the appendix chapter heading to reflect the content Parav Pandit
2024-06-04 13:29 ` [PATCH v11 13/13] newdevice: Extend informative guidance on capability, resource objects Parav Pandit
2024-06-04 17:16 ` [EXTERNAL] [PATCH v11 00/13] flow filter using basic facilities of capability and " Satananda Burla
[not found] ` <691016c0-b8e4-48f0-a26b-45296102f501@davidwei.uk>
2025-03-03 19:59 ` Michael S. Tsirkin [this message]
[not found] ` <8aafe201-db57-4ab0-868e-2216b2d03987@davidwei.uk>
2025-03-04 8:50 ` Michael S. Tsirkin
2025-03-04 3:48 ` Parav Pandit
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=20250303145911-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=dw@davidwei.uk \
--cc=hengqi@linux.alibaba.com \
--cc=jasowang@redhat.com \
--cc=parav@nvidia.com \
--cc=peter.hilber@opensynergy.com \
--cc=sburla@marvell.com \
--cc=shahafs@nvidia.com \
--cc=si-wei.liu@oracle.com \
--cc=virtio-comment@lists.linux.dev \
--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 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.