DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: vanshika.shukla@nxp.com
Cc: dev@dpdk.org, Gagandeep Singh <g.singh@nxp.com>,
	Sachin Saxena <sachin.saxena@nxp.com>,
	Apeksha Gupta <apeksha.gupta@nxp.com>
Subject: Re: [v1 03/12] net/enetc: Optimize ENETC4 data path
Date: Sun, 20 Oct 2024 17:06:58 -0700	[thread overview]
Message-ID: <20241020170658.3ebf6121@hermes.local> (raw)
In-Reply-To: <20241018072644.2379012-4-vanshika.shukla@nxp.com>

On Fri, 18 Oct 2024 12:56:35 +0530
vanshika.shukla@nxp.com wrote:

> +	while (likely(rx_frm_cnt < work_limit)) {
> +#ifdef RTE_ARCH_32
> +		rte_memcpy(&rxbd_temp, rxbd, 16);

Hardcoding size of the rx buffer descriptor is bad idea.
Why not just use structure assignment?
		rxbd_temp = *rxbd;

> +#else
> +		__uint128_t *dst128 = (__uint128_t *)&rxbd_temp;
> +		const __uint128_t *src128 = (const __uint128_t *)rxbd;
> +		*dst128 = *src128;
> +#endif

When I look at godbolt, it already does the right thing with structure
assignment, you won't need the #ifdef.


  reply	other threads:[~2024-10-21  0:07 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-18  7:26 [v1 00/12] ENETC4 PMD support vanshika.shukla
2024-10-18  7:26 ` [v1 01/12] net/enetc: Add initial ENETC4 PMD driver support vanshika.shukla
2024-10-20 23:39   ` Stephen Hemminger
2024-10-20 23:52   ` Stephen Hemminger
2024-10-18  7:26 ` [v1 02/12] net/enetc: Add RX and TX queue APIs for ENETC4 PMD vanshika.shukla
2024-10-20 23:40   ` Stephen Hemminger
2024-10-18  7:26 ` [v1 03/12] net/enetc: Optimize ENETC4 data path vanshika.shukla
2024-10-21  0:06   ` Stephen Hemminger [this message]
2024-10-18  7:26 ` [v1 04/12] net/enetc: Add TX checksum offload and RX checksum validation vanshika.shukla
2024-10-18  7:26 ` [v1 05/12] net/enetc: Add basic statistics vanshika.shukla
2024-10-18  7:26 ` [v1 06/12] net/enetc: Add packet type parsing support vanshika.shukla
2024-10-18  7:26 ` [v1 07/12] net/enetc: Add support for multiple queues with RSS vanshika.shukla
2024-10-18  7:26 ` [v1 08/12] net/enetc: Add VF to PF messaging support and primary MAC setup vanshika.shukla
2024-10-18  7:26 ` [v1 09/12] net/enetc: Add multicast and promiscuous mode support vanshika.shukla
2024-10-18  7:26 ` [v1 10/12] net/enetc: Add link speed and status support vanshika.shukla
2024-10-18  7:26 ` [v1 11/12] net/enetc: Add link status notification support vanshika.shukla
2024-10-18  7:26 ` [v1 12/12] net/enetc: Add MAC and VLAN filter support vanshika.shukla
2024-10-23  6:24 ` [v2 00/12] ENETC4 PMD support vanshika.shukla
2024-10-23  6:24   ` [v2 01/12] net/enetc: Add initial ENETC4 PMD driver support vanshika.shukla
2024-10-23  6:24   ` [v2 02/12] net/enetc: Add RX and TX queue APIs for ENETC4 PMD vanshika.shukla
2024-10-23  6:24   ` [v2 03/12] net/enetc: Optimize ENETC4 data path vanshika.shukla
2024-10-23  6:24   ` [v2 04/12] net/enetc: Add TX checksum offload and RX checksum validation vanshika.shukla
2024-10-23  6:24   ` [v2 05/12] net/enetc: Add basic statistics vanshika.shukla
2024-10-23  6:24   ` [v2 06/12] net/enetc: Add packet type parsing support vanshika.shukla
2024-10-23  6:24   ` [v2 07/12] net/enetc: Add support for multiple queues with RSS vanshika.shukla
2024-10-23  6:24   ` [v2 08/12] net/enetc: Add VF to PF messaging support and primary MAC setup vanshika.shukla
2024-10-23  6:24   ` [v2 09/12] net/enetc: Add multicast and promiscuous mode support vanshika.shukla
2024-10-23  6:24   ` [v2 10/12] net/enetc: Add link speed and status support vanshika.shukla
2024-10-23  6:24   ` [v2 11/12] net/enetc: Add link status notification support vanshika.shukla
2024-10-23  6:24   ` [v2 12/12] net/enetc: Add MAC and VLAN filter support vanshika.shukla

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=20241020170658.3ebf6121@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=apeksha.gupta@nxp.com \
    --cc=dev@dpdk.org \
    --cc=g.singh@nxp.com \
    --cc=sachin.saxena@nxp.com \
    --cc=vanshika.shukla@nxp.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 NNTP newsgroup(s).