From: fengchengwen <fengchengwen@huawei.com>
To: "Morten Brørup" <mb@smartsharesystems.com>,
thomas@monjalon.net, "Kevin Laatz" <kevin.laatz@intel.com>,
"Bruce Richardson" <bruce.richardson@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH v2] dmadev: add tracepoints
Date: Sat, 15 Apr 2023 08:47:44 +0800 [thread overview]
Message-ID: <dbb59fda-fd8e-b833-ef65-fa95f12e7bab@huawei.com> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35D8787A@smartserver.smartshare.dk>
Hi Morten,
Both fix in v3, thanks.
On 2023/4/14 20:46, Morten Brørup wrote:
>> From: Chengwen Feng [mailto:fengchengwen@huawei.com]
>> Sent: Friday, 14 April 2023 11.09
>>
>> Add tracepoints at important APIs for tracing support.
>>
>> Signed-off-by: Chengwen Feng <fengchengwen@huawei.com>
>>
>> ---
>> v2: Address Morten's comment:
>> Make stats_get as fast-path trace-points.
>> Place fast-path trace-point functions behind in version.map.
>
> ...
>
>> +RTE_TRACE_POINT(
>> + rte_dma_trace_vchan_status,
>
> rte_dma_trace_vchan_status should also be a FP trace point.
>
>> + RTE_TRACE_POINT_ARGS(int16_t dev_id, uint16_t vchan,
>> + enum rte_dma_vchan_status *status, int ret),
>> + int vchan_status = *status;
>> + rte_trace_point_emit_i16(dev_id);
>> + rte_trace_point_emit_u16(vchan);
>> + rte_trace_point_emit_int(vchan_status);
>> + rte_trace_point_emit_int(ret);
>> +)
>> +
>> +RTE_TRACE_POINT(
>> + rte_dma_trace_dump,
>> + RTE_TRACE_POINT_ARGS(int16_t dev_id, FILE *f, int ret),
>> + rte_trace_point_emit_i16(dev_id);
>> + rte_trace_point_emit_ptr(f);
>> + rte_trace_point_emit_int(ret);
>> +)
>> +
>> +/* Fast path trace points */
>
> Don't add the fast path trace points here. Add them to the rte_dmadev_trace_fp.h file.
>
>> +
>> +/* Called in loop in examples/dma */
>> +RTE_TRACE_POINT_FP(
>> + rte_dma_trace_stats_get,
>> + RTE_TRACE_POINT_ARGS(int16_t dev_id, uint16_t vchan,
>> + struct rte_dma_stats *stats, int ret),
>> + rte_trace_point_emit_i16(dev_id);
>> + rte_trace_point_emit_u16(vchan);
>> + rte_trace_point_emit_u64(stats->submitted);
>> + rte_trace_point_emit_u64(stats->completed);
>> + rte_trace_point_emit_u64(stats->errors);
>> + rte_trace_point_emit_int(ret);
>> +)
>
> With those two fixes, you may add:
>
> Acked-by: Morten Brørup <mb@smartsharesystems.com>
>
>
> .
>
prev parent reply other threads:[~2023-04-15 0:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 9:09 Chengwen Feng
2023-04-14 12:46 ` Morten Brørup
2023-04-15 0:47 ` fengchengwen [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=dbb59fda-fd8e-b833-ef65-fa95f12e7bab@huawei.com \
--to=fengchengwen@huawei.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=kevin.laatz@intel.com \
--cc=mb@smartsharesystems.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).