From: "Samudrala, Sridhar" <sridhar.samudrala@intel.com>
To: Joe Damato <jdamato@fastly.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>
Cc: intel-wired-lan@lists.osuosl.org
Subject: Re: [Intel-wired-lan] [RFC, next-queue 0/4] i40e: Add a non-XDP i40e_napi_poll tracepoint
Date: Fri, 7 Oct 2022 16:01:50 -0500 [thread overview]
Message-ID: <06378c1a-6f0f-989f-3cc5-3348baa11860@intel.com> (raw)
In-Reply-To: <20221007205548.GA49007@fastly.com>
On 10/7/2022 3:55 PM, Joe Damato wrote:
> On Fri, Oct 07, 2022 at 01:36:20PM -0700, Jesse Brandeburg wrote:
>> On 10/7/2022 10:57 AM, Joe Damato wrote:
>>> Greetings:
>>>
>>> This is an RFC which is similar to the series up for review, except that
>>> this implementation does not touch XDP at all and adds a conditional in
>>> i40e_napi_poll to only fire the tracepoint when XDP is not enabled.
>>>
>>> This should avoid the issues that Maciej has with the naming of out
>>> parameters (since none of that code is touched in this series) and it
>>> clears the way for Maciej, Sridhar, et al to implement the XDP tracepoint.
>>>
>>> I am submitting this an alternative to what's already up for review.
>>>
>>> If you prefer to accept this code, please let me know that you want the
>>> non-XDP version and I'll submit it as the 'v4'.
>> Given the discussion, this is the series I prefer. I'm very happy to see
>> some more debugging helpers coming into the driver so thanks for your work
>> on this Joe! As for the rest of the team they seem to be fine speaking for
>> themselves, so I imagine they'll let you know :-)
>>
>> For the series:
>> Acked-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
> OK, thanks!
>
> There's a minor build failure for a format string (lu should be u) in the
> tracepoint.
>
> I'll fix that now in this series and re-send it as a v4 with a proper
> cover letter.
>
> Thanks again for your detailed feedback and review; I appreciate your time
> and energy on this.
>
> Thanks,
> Joe
Sorry for all the back and forth on this series. The tracepoint itself is definitely
useful and this series looks good.
Acked-by: Sridhar Samudrala <sridhar.samudrala@intel.com>
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
prev parent reply other threads:[~2022-10-07 21:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 17:57 [Intel-wired-lan] [RFC, next-queue 0/4] i40e: Add a non-XDP i40e_napi_poll tracepoint Joe Damato
2022-10-07 17:57 ` [Intel-wired-lan] [RFC, next-queue 1/4] i40e: Store the irq number in i40e_q_vector Joe Damato
2022-10-07 17:57 ` [Intel-wired-lan] [RFC, next-queue 2/4] i40e: Record number TXes cleaned during NAPI Joe Damato
2022-10-07 17:57 ` [Intel-wired-lan] [RFC, next-queue 3/4] i40e: Record number of RXes " Joe Damato
2022-10-07 17:57 ` [Intel-wired-lan] [RFC, next-queue 4/4] i40e: Add i40e_napi_poll tracepoint Joe Damato
2022-10-07 20:36 ` [Intel-wired-lan] [RFC, next-queue 0/4] i40e: Add a non-XDP " Jesse Brandeburg
2022-10-07 20:55 ` Joe Damato
2022-10-07 21:01 ` Samudrala, Sridhar [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=06378c1a-6f0f-989f-3cc5-3348baa11860@intel.com \
--to=sridhar.samudrala@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jdamato@fastly.com \
--cc=jesse.brandeburg@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