From: Adel Belkhiri <adel.belkhiri@gmail.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>
Cc: Jerin Jacob <jerinjacobk@gmail.com>,
Thomas Monjalon <thomas@monjalon.net>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
dev@dpdk.org, Adel Belkhiri <adel.belkhiri@polymtl.ca>
Subject: Re: [PATCH v3] ethdev: optimize the activation of fast-path tracepoints
Date: Mon, 23 Sep 2024 11:27:54 -0400 [thread overview]
Message-ID: <CAMxxxdMeRXwvv5ZNQSyGXUW1VQ=XHZ2pHSh55wrCTe43aZq6iA@mail.gmail.com> (raw)
In-Reply-To: <9c2cca7a-4ab7-4c0a-a6a5-1d90dc83d5e2@amd.com>
[-- Attachment #1: Type: text/plain, Size: 703 bytes --]
Thanks to all of you. Much appreciated!
On Sat, Sep 21, 2024 at 9:07 PM Ferruh Yigit <ferruh.yigit@amd.com> wrote:
> On 9/19/2024 5:37 PM, Jerin Jacob wrote:
> > On Thu, Sep 19, 2024 at 12:16 AM Adel Belkhiri <adel.belkhiri@gmail.com>
> wrote:
> >>
> >> From: Adel Belkhiri <adel.belkhiri@polymtl.ca>
> >>
> >> Split the tracepoints rte_ethdev_trace_rx_burst and
> >> rte_eth_trace_call_rx_callbacks into two separate ones
> >> for empty and non-empty calls to avoid saturating
> >> quickly the trace buffer.
> >>
> >> Signed-off-by: Adel Belkhiri <adel.belkhiri@polymtl.ca>
> >
> > Acked-by: Jerin Jacob <jerinj@marvell.com>
> >
>
> Applied to dpdk-next-net/main, thanks.
>
[-- Attachment #2: Type: text/html, Size: 1338 bytes --]
next prev parent reply other threads:[~2024-09-23 15:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 17:58 [PATCH] ethdev: optimize " Adel Belkhiri
2024-09-13 19:47 ` Morten Brørup
2024-09-16 8:25 ` Jerin Jacob
2024-09-16 8:31 ` David Marchand
2024-09-16 8:45 ` Jerin Jacob
2024-09-18 18:45 ` [PATCH v3] ethdev: optimize the " Adel Belkhiri
2024-09-19 16:37 ` Jerin Jacob
2024-09-22 1:07 ` Ferruh Yigit
2024-09-23 15:27 ` Adel Belkhiri [this message]
2024-09-20 14:46 ` Patrick Robb
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='CAMxxxdMeRXwvv5ZNQSyGXUW1VQ=XHZ2pHSh55wrCTe43aZq6iA@mail.gmail.com' \
--to=adel.belkhiri@gmail.com \
--cc=adel.belkhiri@polymtl.ca \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=jerinjacobk@gmail.com \
--cc=thomas@monjalon.net \
/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).