DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Mattias Rönnblom" <hofors@lysator.liu.se>
To: "Mattias Rönnblom" <mattias.ronnblom@ericsson.com>, dev@dpdk.org
Cc: Naga Harish K S V <s.v.naga.harish.k@intel.com>,
	Jerin Jacob <jerinj@marvell.com>,
	Peter Nilsson <peter.j.nilsson@ericsson.com>
Subject: Re: [PATCH] event/eth_tx: prefetch mbuf headers
Date: Fri, 28 Mar 2025 07:07:59 +0100	[thread overview]
Message-ID: <d0277a40-c17f-4ebf-99b3-bdb7e9190519@lysator.liu.se> (raw)
In-Reply-To: <20250328054339.489914-1-mattias.ronnblom@ericsson.com>

On 2025-03-28 06:43, Mattias Rönnblom wrote:
> Prefetch mbuf headers, resulting in ~10% throughput improvement when
> the Ethernet RX and TX Adapters are hosted on the same core (likely
> ~2x in case a dedicated TX core is used).
> 
> Signed-off-by: Mattias Rönnblom <mattias.ronnblom@ericsson.com>
> Tested-by: Peter Nilsson <peter.j.nilsson@ericsson.com>

What should be added is that what's been tested is the 
non-RTE_EVENT_TYPE_VECTOR case.

> ---
>   lib/eventdev/rte_event_eth_tx_adapter.c | 20 ++++++++++++++++++++
>   1 file changed, 20 insertions(+)
> 
> diff --git a/lib/eventdev/rte_event_eth_tx_adapter.c b/lib/eventdev/rte_event_eth_tx_adapter.c
> index 67fff8b7d6..d740ae00f9 100644
> --- a/lib/eventdev/rte_event_eth_tx_adapter.c
> +++ b/lib/eventdev/rte_event_eth_tx_adapter.c
> @@ -598,6 +598,12 @@ txa_process_event_vector(struct txa_service_data *txa,
>   	return nb_tx;
>   }
>   
> +static inline void
> +txa_prefetch_mbuf(struct rte_mbuf *mbuf)
> +{
> +	rte_mbuf_prefetch_part1(mbuf);
> +}
> +
>   static void
>   txa_service_tx(struct txa_service_data *txa, struct rte_event *ev,
>   	uint32_t n)
> @@ -608,6 +614,20 @@ txa_service_tx(struct txa_service_data *txa, struct rte_event *ev,
>   
>   	stats = &txa->stats;
>   
> +	for (i = 0; i < n; i++) {
> +		struct rte_event *event = &ev[i];
> +
> +		if (unlikely(event->event_type & RTE_EVENT_TYPE_VECTOR)) {
> +			struct rte_event_vector *vec = event->vec;
> +			struct rte_mbuf **mbufs = vec->mbufs;
> +			uint32_t k;
> +
> +			for (k = 0; k < vec->nb_elem; k++)
> +				txa_prefetch_mbuf(mbufs[k]);
> +		} else
> +			txa_prefetch_mbuf(event->mbuf);
> +	}
> +
>   	nb_tx = 0;
>   	for (i = 0; i < n; i++) {
>   		uint16_t port;


      reply	other threads:[~2025-03-28  6:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-28  5:43 Mattias Rönnblom
2025-03-28  6:07 ` Mattias Rönnblom [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=d0277a40-c17f-4ebf-99b3-bdb7e9190519@lysator.liu.se \
    --to=hofors@lysator.liu.se \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=mattias.ronnblom@ericsson.com \
    --cc=peter.j.nilsson@ericsson.com \
    --cc=s.v.naga.harish.k@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;
as well as URLs for NNTP newsgroup(s).