From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <hofors@lysator.liu.se>
Received: from mail.lysator.liu.se (mail.lysator.liu.se [130.236.254.3])
 by dpdk.org (Postfix) with ESMTP id 8D4F51B4FB
 for <dev@dpdk.org>; Wed, 19 Dec 2018 11:28:32 +0100 (CET)
Received: from mail.lysator.liu.se (localhost [127.0.0.1])
 by mail.lysator.liu.se (Postfix) with ESMTP id 0C6B240004
 for <dev@dpdk.org>; Wed, 19 Dec 2018 11:28:32 +0100 (CET)
Received: by mail.lysator.liu.se (Postfix, from userid 1004)
 id EE32E4001C; Wed, 19 Dec 2018 11:28:31 +0100 (CET)
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on
 bernadotte.lysator.liu.se
X-Spam-Level: 
X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,AWL
 autolearn=disabled version=3.4.1
X-Spam-Score: -1.0
Received: from [192.168.1.59] (host-90-232-140-56.mobileonline.telia.com
 [90.232.140.56])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by mail.lysator.liu.se (Postfix) with ESMTPSA id C07CE40004;
 Wed, 19 Dec 2018 11:28:29 +0100 (CET)
To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
 Konstantin Ananyev <konstantin.ananyev@intel.com>,
 "dev@dpdk.org" <dev@dpdk.org>
Cc: nd <nd@arm.com>, "Gavin Hu (Arm Technology China)" <Gavin.Hu@arm.com>
References: <1542130061-3702-1-git-send-email-konstantin.ananyev@intel.com>
 <1542130061-3702-2-git-send-email-konstantin.ananyev@intel.com>
 <AM6PR08MB367213976F11F1C407FF195398BE0@AM6PR08MB3672.eurprd08.prod.outlook.com>
From: =?UTF-8?Q?Mattias_R=c3=b6nnblom?= <hofors@lysator.liu.se>
Message-ID: <ebc940ff-c50e-94dc-c7a6-9b1eca73ec09@lysator.liu.se>
Date: Wed, 19 Dec 2018 11:28:29 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.2.1
MIME-Version: 1.0
In-Reply-To: <AM6PR08MB367213976F11F1C407FF195398BE0@AM6PR08MB3672.eurprd08.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
Subject: Re: [dpdk-dev] [PATCH 1/2] rwlock: introduce 'try' semantics for RD
 and WR locking
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Dec 2018 10:28:32 -0000

On 2018-12-19 07:37, Honnappa Nagarahalli wrote:
>> diff --git a/lib/librte_eal/rte_eal_version.map
>> b/lib/librte_eal/rte_eal_version.map
>> index 3fe78260d..8b1593dd8 100644
>> --- a/lib/librte_eal/rte_eal_version.map
>> +++ b/lib/librte_eal/rte_eal_version.map
>> @@ -355,6 +355,8 @@ EXPERIMENTAL {
>>   	rte_mp_request_async;
>>   	rte_mp_sendmsg;
>>   	rte_option_register;
>> +	rte_rwlock_read_trylock;
>> +	rte_rwlock_write_trylock;
> I do not see the other RW lock APIs in this file.
> 

They, just like those added, are static inline functions, will not 
result in any symbols in any shared objects and thus shouldn't be in any 
version.map file.