From: Dan Jurgens <danielj@nvidia.com>
To: ALOK TIWARI <alok.a.tiwari@oracle.com>,
netdev@vger.kernel.org, mst@redhat.com, jasowang@redhat.com,
alex.williamson@redhat.com, virtualization@lists.linux.dev,
pabeni@redhat.com
Cc: parav@nvidia.com, shshitrit@nvidia.com, yohadt@nvidia.com
Subject: Re: [PATCH net-next 06/11] virtio_net: Implement layer 2 ethtool flow rules
Date: Fri, 29 Aug 2025 15:16:46 -0500 [thread overview]
Message-ID: <74dd76fc-59fd-47b2-82cb-e03b0a3aeff1@nvidia.com> (raw)
In-Reply-To: <a4532ca7-fee8-486a-9c5f-6fccb6de7b40@oracle.com>
On 8/29/25 1:39 PM, ALOK TIWARI wrote:
>
>
>> +static void calculate_flow_sizes(struct ethtool_rx_flow_spec *fs,
>> + * header for each type of header in the match critea, and each
>> header
>
> typo critea -> criteria
>
>> + * providing the mask for matching against.
>> + */
>> + calculate_flow_sizes(fs, &key_size, &classifier_size, &num_hdrs);
>> +
>> + key = kzalloc(key_size, GFP_KERNEL);
>> + if (!key)
>> + return -ENOMEM;
>> +
>> + /*
>> + * virio_net_ff_obj_ff_classifier is already included in the
>
> virio_net_ff_obj_ff_classifier -> virtio_net_ff_obj_ff_classifier
>
>> + * classifier_size.
>> + */
>> + c = kzalloc(classifier_size +
>> + sizeof(struct virtnet_classifier) -
>> + sizeof(struct virtio_net_resource_obj_ff_classifier),
>> + GFP_KERNEL);
>> + if (!c)
>> + return -ENOMEM;
>
> kfree(key) before returning -ENOMEM
>
>
> Thanks,
> Alok
>
Thanks Alok. Applied those changes for v2.
next prev parent reply other threads:[~2025-08-29 20:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 18:38 [PATCH net-next 00/11] virtio_net: Add ethtool flow rules support Daniel Jurgens
2025-08-27 18:38 ` [PATCH net-next 01/11] virtio-pci: Expose generic device capability operations Daniel Jurgens
2025-08-27 18:38 ` [PATCH net-next 02/11] virtio-pci: Expose object create and destroy API Daniel Jurgens
2025-08-27 18:38 ` [PATCH net-next 03/11] virtio_net: Create virtio_net directory Daniel Jurgens
2025-08-27 18:38 ` [PATCH net-next 04/11] virtio_net: Query and set flow filter caps Daniel Jurgens
2025-08-28 0:15 ` kernel test robot
2025-08-27 18:38 ` [PATCH net-next 05/11] virtio_net: Create a FF group for ethtool steering Daniel Jurgens
2025-08-28 20:52 ` kernel test robot
2025-08-27 18:38 ` [PATCH net-next 06/11] virtio_net: Implement layer 2 ethtool flow rules Daniel Jurgens
2025-08-28 22:27 ` kernel test robot
2025-08-29 18:39 ` ALOK TIWARI
2025-08-29 20:16 ` Dan Jurgens [this message]
2025-08-27 18:38 ` [PATCH net-next 07/11] virtio_net: Use existing classifier if possible Daniel Jurgens
2025-08-27 18:38 ` [PATCH net-next 08/11] virtio_net: Implement IPv4 ethtool flow rules Daniel Jurgens
2025-08-29 0:27 ` kernel test robot
2025-08-27 18:38 ` [PATCH net-next 09/11] virtio_net: Add support for IPv6 ethtool steering Daniel Jurgens
2025-08-27 18:38 ` [PATCH net-next 10/11] virtio_net: Add support for TCP and UDP ethtool rules Daniel Jurgens
2025-08-27 18:38 ` [PATCH net-next 11/11] virtio_net: Add get ethtool flow rules ops Daniel Jurgens
-- strict thread matches above, loose matches on Subject: below --
2025-08-28 15:05 [PATCH net-next 06/11] virtio_net: Implement layer 2 ethtool flow rules kernel test robot
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=74dd76fc-59fd-47b2-82cb-e03b0a3aeff1@nvidia.com \
--to=danielj@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=alok.a.tiwari@oracle.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=parav@nvidia.com \
--cc=shshitrit@nvidia.com \
--cc=virtualization@lists.linux.dev \
--cc=yohadt@nvidia.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.