From: Dawid Osuchowski <dawid.osuchowski@linux.intel.com>
To: "Sanigani, SarithaX" <sarithax.sanigani@intel.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>
Cc: "Fijalkowski, Maciej" <maciej.fijalkowski@intel.com>,
"Lobakin, Aleksander" <aleksander.lobakin@intel.com>,
"Keller, Jacob E" <jacob.e.keller@intel.com>,
"Zaremba, Larysa" <larysa.zaremba@intel.com>,
"Kitszel, Przemyslaw" <przemyslaw.kitszel@intel.com>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
"Kubiak, Michal" <michal.kubiak@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v3 1/3] ice: remove legacy Rx and construct SKB
Date: Fri, 31 Oct 2025 10:29:53 +0100 [thread overview]
Message-ID: <d4fd9c18-e8bd-4dc1-bacc-51be080cc693@linux.intel.com> (raw)
In-Reply-To: <PH8PR11MB69764650A4A2EB8CCAFD5461F9F8A@PH8PR11MB6976.namprd11.prod.outlook.com>
On 2025-10-31 5:58 AM, Sanigani, SarithaX wrote:
>> -----Original Message-----
>
>> From: Intel-wired-lan <intel-wired-lan-bounces@osuosl.org<mailto:intel-wired-lan-bounces@osuosl.org>> On Behalf Of Michal Kubiak
>
>> Sent: Thursday, September 25, 2025 2:53 PM
>
>> To: intel-wired-lan@lists.osuosl.org<mailto:intel-wired-lan@lists.osuosl.org>
>
>> Cc: Fijalkowski, Maciej <maciej.fijalkowski@intel.com<mailto:maciej.fijalkowski@intel.com>>; Lobakin, Aleksander <aleksander.lobakin@intel.com<mailto:aleksander.lobakin@intel.com>>; Keller, Jacob E <jacob.e.keller@intel.com<mailto:jacob.e.keller@intel.com>>;
>
>> Zaremba, Larysa <larysa.zaremba@intel.com<mailto:larysa.zaremba@intel.com>>; netdev@vger.kernel.org<mailto:netdev@vger.kernel.org>; Kitszel, Przemyslaw <przemyslaw.kitszel@intel.com<mailto:przemyslaw.kitszel@intel.com>>; pmenzel@molgen.mpg.de<mailto:pmenzel@molgen.mpg.de>;
>
>> Nguyen, Anthony L <anthony.l.nguyen@intel.com<mailto:anthony.l.nguyen@intel.com>>; Kubiak, Michal <michal.kubiak@intel.com<mailto:michal.kubiak@intel.com>>
>
>> Subject: [Intel-wired-lan] [PATCH iwl-next v3 1/3] ice: remove legacy Rx and construct SKB
>
>>
>
>> The commit 53844673d555 ("iavf: kill 'legacy-rx' for good") removed the legacy Rx path in the iavf driver. This change applies the same rationale to the ice driver.
>
>>
>
>> The legacy Rx path relied on manual skb allocation and header copying, which has become increasingly inefficient and difficult to maintain.
>
>> With the stabilization of build_skb() and the growing adoption of features like XDP, page_pool, and multi-buffer support, the legacy approach is no longer viable.
>
>>
>
>> Key drawbacks of the legacy path included:
>
>> - Higher memory pressure due to direct page allocations and splitting;
>
>> - Redundant memcpy() operations for packet headers;
>
>> - CPU overhead from eth_get_headlen() and Flow Dissector usage;
>
>> - Compatibility issues with XDP, which imposes strict headroom and
>
>> tailroom requirements.
>
>>
>
>> The ice driver, like iavf, does not benefit from the minimal headroom savings that legacy Rx once offered, as it already splits pages into fixed halves. Removing this path simplifies the Rx logic, eliminates unnecessary branches in the hotpath, and prepares the driver for upcoming enhancements.
>
>>
>
>> In addition to removing the legacy Rx path, this change also eliminates the custom construct_skb() functions from both the standard and zero-copy (ZC) Rx paths. These are replaced with the build_skb() > and standardized xdp_build_skb_from_zc() helpers, aligning the driver with the modern XDP infrastructure and reducing code duplication.
>
>>
>
>> This cleanup also reduces code complexity and improves maintainability as we move toward a more unified and modern Rx model across drivers.
>
>>
>
>> Co-developed-by: Alexander Lobakin <aleksander.lobakin@intel.com<mailto:aleksander.lobakin@intel.com>>
>
>> Signed-off-by: Alexander Lobakin <aleksander.lobakin@intel.com<mailto:aleksander.lobakin@intel.com>>
>
>> Reviewed-by: Alexander Lobakin <aleksander.lobakin@intel.com<mailto:aleksander.lobakin@intel.com>>
>
>> Reviewed-by: Jacob Keller <jacob.e.keller@intel.com<mailto:jacob.e.keller@intel.com>>
>
>> Signed-off-by: Michal Kubiak <michal.kubiak@intel.com<mailto:michal.kubiak@intel.com>>
>
>> ---
<snip>>
> Tested-by: Saritha Sanigani <sarithax.sanigani@intel.com<mailto:sarithax.sanigani@intel.com>> (A Contingent Worker at Intel)
Hello Saritha
It seems your email client is misconfigured as this message (and the
rest of messages for this series) appear as completely separate from the
thread "ice: convert Rx path to Page Pool". This also means patchwork
did not pick up your Tested-by tags [1].
Another issue is the mangled email addresses in
Signed-off-by/Reviewed-by/Tested-by tags.
Best,
Dawid
[1]
https://patchwork.ozlabs.org/project/intel-wired-lan/patch/20250925092253.1306476-2-michal.kubiak@intel.com/
next prev parent reply other threads:[~2025-10-31 9:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 4:58 [Intel-wired-lan] [PATCH iwl-next v3 1/3] ice: remove legacy Rx and construct SKB Sanigani, SarithaX
2025-10-31 9:29 ` Dawid Osuchowski [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-25 9:22 [Intel-wired-lan] [PATCH iwl-next v3 0/3] ice: convert Rx path to Page Pool Michal Kubiak
2025-09-25 9:22 ` [Intel-wired-lan] [PATCH iwl-next v3 1/3] ice: remove legacy Rx and construct SKB Michal Kubiak
2025-10-22 23:53 ` Nowlin, Alexander
2025-10-22 23:53 ` Nowlin, Alexander
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=d4fd9c18-e8bd-4dc1-bacc-51be080cc693@linux.intel.com \
--to=dawid.osuchowski@linux.intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=larysa.zaremba@intel.com \
--cc=maciej.fijalkowski@intel.com \
--cc=michal.kubiak@intel.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=sarithax.sanigani@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 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.