From: Jerin Jacob <jerinj@marvell.com>
To: "Mattias Rönnblom" <mattias.ronnblom@ericsson.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Naga Harish K S V" <s.v.naga.harish.k@intel.com>
Cc: "Mattias Rönnblom" <hofors@lysator.liu.se>,
"Peter Nilsson" <peter.j.nilsson@ericsson.com>
Subject: RE: [EXTERNAL] [PATCH] event/eth_tx: prefetch mbuf headers
Date: Tue, 27 May 2025 05:01:24 +0000 [thread overview]
Message-ID: <BY3PR18MB4785641F294E9E1A653DF328C864A@BY3PR18MB4785.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20250328054339.489914-1-mattias.ronnblom@ericsson.com>
[-- Attachment #1: Type: text/html, Size: 8086 bytes --]
next prev parent reply other threads:[~2025-05-27 5:01 UTC|newest]
Thread overview: 5+ 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 ` Jerin Jacob [this message]
2025-05-27 10:55 ` Naga Harish K, S V
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=BY3PR18MB4785641F294E9E1A653DF328C864A@BY3PR18MB4785.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=dev@dpdk.org \
--cc=hofors@lysator.liu.se \
--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).