From: "Plachno, Lukasz" <lukasz.plachno@intel.com>
To: Alexander Lobakin <aleksander.lobakin@intel.com>
Cc: pmenzel@molgen.mpg.de, brett.creeley@amd.com,
netdev@vger.kernel.org,
Jakub Buchocki <jakubx.buchocki@intel.com>,
intel-wired-lan@lists.osuosl.org, horms@kernel.org,
Mateusz Pacuszka <mateuszx.pacuszka@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v5 2/2] ice: Implement 'flow-type ether' rules
Date: Thu, 8 Feb 2024 12:56:23 +0100 [thread overview]
Message-ID: <8e4148bf-71b1-48dd-a2a4-84a46f2cd66e@intel.com> (raw)
In-Reply-To: <9deb3115-eb04-4b18-90de-c884b91dc101@intel.com>
On 2/7/2024 3:07 PM, Alexander Lobakin wrote:
> From: Lukasz Plachno <lukasz.plachno@intel.com>
> Date: Tue, 6 Feb 2024 17:33:37 +0100
>
>> From: Jakub Buchocki <jakubx.buchocki@intel.com>
>>
>> Add support for 'flow-type ether' Flow Director rules via ethtool.
>>
>> Create packet segment info for filter configuration based on ethtool
>> command parameters. Reuse infrastructure already created for
>> ipv4 and ipv6 flows to convert packet segment into
>> extraction sequence, which is later used to program the filter
>> inside Flow Director block of the Rx pipeline.
>
> [...]
>
>> diff --git a/drivers/net/ethernet/intel/ice/ice_fdir.c b/drivers/net/ethernet/intel/ice/ice_fdir.c
>> index 1f7b26f38818..5fe0bad00fd7 100644
>> --- a/drivers/net/ethernet/intel/ice/ice_fdir.c
>> +++ b/drivers/net/ethernet/intel/ice/ice_fdir.c
>> @@ -4,6 +4,8 @@
>> #include "ice_common.h"
>>
>> /* These are training packet headers used to program flow director filters. */
>> +static const u8 ice_fdir_eth_pkt[22] = {0};
>
> I believe this zeroing is not needed, just declare it and the compiler
> will zero it automatically.
>
{0}; will be removed in V6
> [...]
>
>> @@ -97,6 +100,12 @@ struct ice_rx_flow_userdef {
>> u16 flex_fltr;
>> };
>>
>> +struct ice_fdir_eth {
>> + u8 dst[ETH_ALEN];
>> + u8 src[ETH_ALEN];
>> + __be16 type;
>> +};
>
> This is clearly `struct ethhdr`, please remove this duplicating
> definition and just use the generic structure.
>
I will fix that in V6, thank you for catching that.
Regards,
Łukasz
prev parent reply other threads:[~2024-02-08 12:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 16:33 [Intel-wired-lan] [PATCH iwl-next v5 0/2] ice: Support flow director ether type filters Lukasz Plachno
2024-02-06 16:33 ` [Intel-wired-lan] [PATCH iwl-next v5 1/2] ice: Remove unnecessary argument from ice_fdir_comp_rules() Lukasz Plachno
2024-02-06 16:33 ` [Intel-wired-lan] [PATCH iwl-next v5 2/2] ice: Implement 'flow-type ether' rules Lukasz Plachno
2024-02-07 14:07 ` Alexander Lobakin
2024-02-08 11:56 ` Plachno, Lukasz [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=8e4148bf-71b1-48dd-a2a4-84a46f2cd66e@intel.com \
--to=lukasz.plachno@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=brett.creeley@amd.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jakubx.buchocki@intel.com \
--cc=mateuszx.pacuszka@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=przemyslaw.kitszel@intel.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