DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Naga Harish K, S V" <s.v.naga.harish.k@intel.com>
To: "Mattias Rönnblom" <hofors@lysator.liu.se>,
	"Mattias Rönnblom" <mattias.ronnblom@ericsson.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: Jerin Jacob <jerinj@marvell.com>,
	Peter Nilsson <peter.j.nilsson@ericsson.com>
Subject: RE: [PATCH] event/eth_tx: prefetch mbuf headers
Date: Mon, 7 Jul 2025 09:00:08 +0000	[thread overview]
Message-ID: <SJ5PPF56FDAD370AD3B60F4AA326723904BA14FA@SJ5PPF56FDAD370.namprd11.prod.outlook.com> (raw)
In-Reply-To: <ff692fe7-03b5-408d-8112-5a4b30d9f96b@lysator.liu.se>



> -----Original Message-----
> From: Mattias Rönnblom <hofors@lysator.liu.se>
> Sent: Thursday, July 3, 2025 1:50 AM
> To: Naga Harish K, S V <s.v.naga.harish.k@intel.com>; Mattias Rönnblom
> <mattias.ronnblom@ericsson.com>; dev@dpdk.org
> Cc: Jerin Jacob <jerinj@marvell.com>; Peter Nilsson
> <peter.j.nilsson@ericsson.com>
> Subject: Re: [PATCH] event/eth_tx: prefetch mbuf headers
> 
> On 2025-05-27 12:55, Naga Harish K, S V wrote:
> >
> >
> >> -----Original Message-----
> >> From: Mattias Rönnblom <mattias.ronnblom@ericsson.com>
> >> Sent: Friday, March 28, 2025 11:14 AM
> >> To: dev@dpdk.org
> >> Cc: Mattias Rönnblom <hofors@lysator.liu.se>; Naga Harish K, S V
> >> <s.v.naga.harish.k@intel.com>; Jerin Jacob <jerinj@marvell.com>;
> >> Mattias Rönnblom <mattias.ronnblom@ericsson.com>; Peter Nilsson
> >> <peter.j.nilsson@ericsson.com>
> >> Subject: [PATCH] event/eth_tx: prefetch mbuf headers
> >>
> >> 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>
> >> ---
> >>   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))
> >
> >
> > This gives a branch prediction advantage to non-vector events. Is that the
> intention?
> >
> 
> Yes.

I think all event-types need to be equally weighted. My ask was to remove the "unlikely" for vector events.

> 
> >> {
> >> +			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;
> >> --
> >> 2.43.0
> >


  reply	other threads:[~2025-07-07  9:00 UTC|newest]

Thread overview: 8+ 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
2025-05-20 12:56   ` Mattias Rönnblom
2025-05-27  5:01 ` [EXTERNAL] " Jerin Jacob
2025-05-27 10:55 ` Naga Harish K, S V
2025-07-02 20:19   ` Mattias Rönnblom
2025-07-07  9:00     ` Naga Harish K, S V [this message]
2025-07-07 11:57       ` Mattias Rönnblom

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=SJ5PPF56FDAD370AD3B60F4AA326723904BA14FA@SJ5PPF56FDAD370.namprd11.prod.outlook.com \
    --to=s.v.naga.harish.k@intel.com \
    --cc=dev@dpdk.org \
    --cc=hofors@lysator.liu.se \
    --cc=jerinj@marvell.com \
    --cc=mattias.ronnblom@ericsson.com \
    --cc=peter.j.nilsson@ericsson.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).