From: Ankur Dwivedi <adwivedi@marvell.com>
To: David Marchand <david.marchand@redhat.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"ferruh.yigit@amd.com" <ferruh.yigit@amd.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Subject: RE: [EXT] Re: [PATCH v1 1/5] mempool: remove internal tracepoints from version map
Date: Fri, 10 Feb 2023 05:32:24 +0000 [thread overview]
Message-ID: <CO3PR18MB50057594F63F6EB2528C397FDDDE9@CO3PR18MB5005.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8x_YWVjk8bW1PGe0FSVkFecUEBkf=P9-eUND2LbF_Kv+g@mail.gmail.com>
>On Thu, Feb 9, 2023 at 2:30 PM Ankur Dwivedi <adwivedi@marvell.com>
>wrote:
>>
>> The file rte_mempool_trace.h contains tracepoints which are internal
>> to the mempool library. This file is renamed to mempool_trace.h, and
>> is made an internal header. The tracepoints in this file are removed
>> from the
>
>This patch also exports this new internal header which looks wrong to me.
>See below.
>
>
>> experimental section in version.map file.
>>
>> Signed-off-by: Ankur Dwivedi <adwivedi@marvell.com>
>
>> diff --git a/lib/mempool/meson.build b/lib/mempool/meson.build index
>> b8aaa00694..29ae6d21e5 100644
>> --- a/lib/mempool/meson.build
>> +++ b/lib/mempool/meson.build
>> @@ -17,7 +17,9 @@ sources = files(
>> )
>> headers = files(
>> 'rte_mempool.h',
>> - 'rte_mempool_trace.h',
>> 'rte_mempool_trace_fp.h',
>> )
>> +driver_sdk_headers += files(
>> + 'mempool_trace.h',
>> +)
>
>driver_sdk_headers is for exporting driver headers.
Ok.
>I am not sure why you added this, can you elaborate?
I saw the changes done in lib/eventdev for eventdev_trace.h. Made similar changes for
mempool and other library.
>
>Checking with who includes this header in the whole tree:
>$ git grep include..mempool_trace
>lib/mempool/mempool_trace_points.c:#include "mempool_trace.h"
>lib/mempool/rte_mempool.c:#include "mempool_trace.h"
>lib/mempool/rte_mempool_ops.c:#include "mempool_trace.h"
>
>I see no external (from the mempool library pov) user of this header => no
>export needed.
Ok, will remove it.
>
>I did not check the rest of the series, but the same argument is likely to apply.
>
>
>Thanks.
>
>--
>David Marchand
next prev parent reply other threads:[~2023-02-10 5:32 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 13:30 [PATCH v1 0/5] " Ankur Dwivedi
2023-02-09 13:30 ` [PATCH v1 1/5] mempool: " Ankur Dwivedi
2023-02-09 14:23 ` David Marchand
2023-02-10 5:32 ` Ankur Dwivedi [this message]
2023-02-10 5:44 ` Jerin Jacob
2023-02-10 7:00 ` [EXT] " Ankur Dwivedi
2023-02-10 7:06 ` Jerin Jacob
2023-02-10 14:24 ` David Marchand
2023-02-10 15:32 ` Jerin Jacob
2023-02-14 11:37 ` Ankur Dwivedi
2023-02-20 14:18 ` David Marchand
2023-02-09 13:30 ` [PATCH v1 2/5] cryptodev: " Ankur Dwivedi
2023-02-09 13:30 ` [PATCH v1 3/5] eal: " Ankur Dwivedi
2023-02-09 13:30 ` [PATCH v1 4/5] ethdev: " Ankur Dwivedi
2023-02-09 14:13 ` Ferruh Yigit
2023-02-09 13:30 ` [PATCH v1 5/5] eventdev: " Ankur Dwivedi
2023-02-10 10:34 ` [PATCH v2 0/5] " Ankur Dwivedi
2023-02-10 10:34 ` [PATCH v2 1/5] mempool: " Ankur Dwivedi
2023-02-10 10:34 ` [PATCH v2 2/5] cryptodev: " Ankur Dwivedi
2023-02-10 10:34 ` [PATCH v2 3/5] eal: " Ankur Dwivedi
2023-02-10 10:34 ` [PATCH v2 4/5] ethdev: " Ankur Dwivedi
2023-02-10 14:19 ` David Marchand
2023-02-13 8:14 ` [EXT] " Ankur Dwivedi
2023-02-10 10:34 ` [PATCH v2 5/5] eventdev: " Ankur Dwivedi
2023-02-10 13:08 ` Jerin Jacob
2023-02-15 9:42 ` [PATCH v3 0/5] " Ankur Dwivedi
2023-02-15 9:42 ` [PATCH v3 1/5] mempool: " Ankur Dwivedi
2023-02-15 9:42 ` [PATCH v3 2/5] cryptodev: " Ankur Dwivedi
2023-02-15 9:42 ` [PATCH v3 3/5] eal: " Ankur Dwivedi
2023-02-15 9:42 ` [PATCH v3 4/5] ethdev: " Ankur Dwivedi
2023-02-15 9:42 ` [PATCH v3 5/5] eventdev: " Ankur Dwivedi
2023-02-20 14:39 ` [PATCH v3 0/5] " Thomas Monjalon
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=CO3PR18MB50057594F63F6EB2528C397FDDDE9@CO3PR18MB5005.namprd18.prod.outlook.com \
--to=adwivedi@marvell.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=jerinj@marvell.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).