From: Joe Damato <jdamato@fastly.com>
To: intel-wired-lan@lists.osuosl.org
Cc: netdev@vger.kernel.org, Joe Damato <jdamato@fastly.com>,
kuba@kernel.org, davem@davemloft.net
Subject: [Intel-wired-lan] [next-queue 0/3] i40e: Add an i40e_napi_poll tracepoint
Date: Wed, 5 Oct 2022 01:31:40 -0700 [thread overview]
Message-ID: <1664958703-4224-1-git-send-email-jdamato@fastly.com> (raw)
Greetings:
Debugging and tuning the NAPI and i40e NIC parameters can be a bit tricky
as there are many different options to test.
This change adds a tracepoint to i40e_napi_poll which exposes a lot of
helpful debug information for users who'd like to get a better
understanding of how their NIC is performing as they adjust various
parameters and tuning knobs.
Some tweaks to i40e to support this information are made along the way;
including a tweak to i40e_clean_tx_irq (and i40e_clean_xdp_tx_irq, etc)
which returns the actual number of packets processed.
Thanks,
Joe
Joe Damato (3):
i40e: Store the irq number in i40e_q_vector
i40e: i40e_clean_tx_irq returns work done
i40e: Add i40e_napi_poll tracepoint
drivers/net/ethernet/intel/i40e/i40e.h | 1 +
drivers/net/ethernet/intel/i40e/i40e_main.c | 1 +
drivers/net/ethernet/intel/i40e/i40e_trace.h | 50 ++++++++++++++++++++++++++++
drivers/net/ethernet/intel/i40e/i40e_txrx.c | 27 +++++++++------
drivers/net/ethernet/intel/i40e/i40e_xsk.c | 12 +++----
drivers/net/ethernet/intel/i40e/i40e_xsk.h | 2 +-
6 files changed, 75 insertions(+), 18 deletions(-)
--
2.7.4
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next reply other threads:[~2022-10-05 8:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 8:31 Joe Damato [this message]
2022-10-05 8:31 ` [Intel-wired-lan] [next-queue 1/3] i40e: Store the irq number in i40e_q_vector Joe Damato
2022-10-05 10:29 ` Maciej Fijalkowski
2022-10-05 17:00 ` Joe Damato
2022-10-05 18:25 ` Jesse Brandeburg
2022-10-05 18:40 ` Joe Damato
2022-10-05 19:37 ` Jesse Brandeburg
2022-10-06 13:06 ` Maciej Fijalkowski
2022-10-05 8:31 ` [Intel-wired-lan] [next-queue 2/3] i40e: i40e_clean_tx_irq returns work done Joe Damato
2022-10-05 8:45 ` Paul Menzel
2022-10-05 10:46 ` Maciej Fijalkowski
2022-10-05 17:50 ` Joe Damato
2022-10-05 18:33 ` Jesse Brandeburg
2022-10-05 18:47 ` Joe Damato
2022-10-05 8:31 ` [Intel-wired-lan] [next-queue 3/3] i40e: Add i40e_napi_poll tracepoint Joe Damato
2022-10-05 10:27 ` Maciej Fijalkowski
2022-10-05 17:56 ` Joe Damato
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=1664958703-4224-1-git-send-email-jdamato@fastly.com \
--to=jdamato@fastly.com \
--cc=davem@davemloft.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
/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