From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 20B74A00C2; Thu, 6 Oct 2022 18:03:23 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id BA10140A82; Thu, 6 Oct 2022 18:03:22 +0200 (CEST) Received: from smartserver.smartsharesystems.com (smartserver.smartsharesystems.com [77.243.40.215]) by mails.dpdk.org (Postfix) with ESMTP id 6CCF440697 for ; Thu, 6 Oct 2022 18:03:21 +0200 (CEST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [PATCH v3 1/4] ethdev: add trace points Date: Thu, 6 Oct 2022 18:03:20 +0200 Message-ID: <98CBD80474FA8B44BF855DF32C47DC35D873AB@smartserver.smartshare.dk> In-Reply-To: <20221006151844.23483-2-adwivedi@marvell.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [PATCH v3 1/4] ethdev: add trace points Thread-Index: AdjZl2kTlGPCNdLSR+afvyKvrBpzegAA1q2A References: <20220929102936.5490-1-adwivedi@marvell.com> <20221006151844.23483-1-adwivedi@marvell.com> <20221006151844.23483-2-adwivedi@marvell.com> From: =?iso-8859-1?Q?Morten_Br=F8rup?= To: "Ankur Dwivedi" , Cc: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org > From: Ankur Dwivedi [mailto:adwivedi@marvell.com] > Sent: Thursday, 6 October 2022 17.19 >=20 > Add trace points for ethdev functions. >=20 > Signed-off-by: Ankur Dwivedi > --- I did my best, but this series needs review by people with direct = knowledge about the affected functions. rte_eth_call_rx/tx_callbacks() are treated as fast path functions, but I = think more functions should be too: rte_eth_tx_buffer_drop_callback() and rte_eth_tx_buffer_count_callback() = are certainly fast path functions. rte_eth_tx_done_cleanup()probably is too. rte_eth_macaddr_get() could be, but probably isn't. If treated as slow = path, it could be noted in its documentation. I don't know about rte_eth_timesync_read_rx/tx_timestamp(), = rte_eth_timesync_adjust/read/write_time() and rte_eth_read_clock().