DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Eelco Chaudron" <echaudro@redhat.com>
To: "David Marchand" <david.marchand@redhat.com>
Cc: cristian.dumitrescu@intel.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 3/3] lib/librte_meter: update abi to include new rfc4115 function
Date: Wed, 28 Nov 2018 10:27:04 +0100	[thread overview]
Message-ID: <EF77C808-9618-4EA4-A48C-3C6DF9419DBC@redhat.com> (raw)
In-Reply-To: <CAJFAV8zUyBqEovvaChs3TO+Ah15T3davXPPkpDzzE2-fMQGD2g@mail.gmail.com>



On 28 Nov 2018, at 9:38, David Marchand wrote:

> Hello Eelco,
>
> On Tue, Nov 27, 2018 at 4:22 PM Eelco Chaudron <echaudro@redhat.com> 
> wrote:
>
>> Update the ABI to include the new RFC4115 meter functions
>> ---
>>  lib/librte_meter/Makefile              |    2 +-
>>  lib/librte_meter/meson.build           |    2 +-
>>  lib/librte_meter/rte_meter_version.map |    9 +++++++++
>>  3 files changed, 11 insertions(+), 2 deletions(-)
>>
>> diff --git a/lib/librte_meter/Makefile b/lib/librte_meter/Makefile
>> index 2dc071e8e..79ad79744 100644
>> --- a/lib/librte_meter/Makefile
>> +++ b/lib/librte_meter/Makefile
>> @@ -16,7 +16,7 @@ LDLIBS += -lrte_eal
>>
>>  EXPORT_MAP := rte_meter_version.map
>>
>> -LIBABIVER := 2
>> +LIBABIVER := 3
>>
>>  #
>>  # all source are stored in SRCS-y
>>
>
> As far as I understood the policy around the EXPERIMENTAL section, you
> don't need to bump the library version.

Thought I would add the new function as none experimental, i.e. next 
version, but checkpatch did not allow me to do this.

Tried to find info on what the right process was, as these functions are 
just another meter implementation using similar existing APIs. If anyone 
has any background on this please point me to it.

I changed the library version as an existing data structure changed 
(which in theory should not change the location of the data), but the 
ABI check popped warnings so I decided to increase the version.

>
> + you should squash this into the first patch.

I’ll do this on the next version.

Thanks,

Eelco

  parent reply	other threads:[~2018-11-28  9:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-27 15:20 [dpdk-dev] [PATCH 0/3] lib/librte_meter: add RFC4115 trTCM meter support Eelco Chaudron
2018-11-27 15:21 ` [dpdk-dev] [PATCH 1/3] " Eelco Chaudron
2018-11-27 15:21 ` [dpdk-dev] [PATCH 2/3] test/test_meter: update meter test to include RFC4115 meters Eelco Chaudron
2018-11-27 15:21 ` [dpdk-dev] [PATCH 3/3] lib/librte_meter: update abi to include new rfc4115 function Eelco Chaudron
     [not found]   ` <CAJFAV8zUyBqEovvaChs3TO+Ah15T3davXPPkpDzzE2-fMQGD2g@mail.gmail.com>
2018-11-28  9:27     ` Eelco Chaudron [this message]
2018-11-28 10:09       ` Thomas Monjalon
2018-11-28 12:40         ` Eelco Chaudron
2018-11-28 12:51           ` Thomas Monjalon
2018-11-28 13:17             ` Eelco Chaudron

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=EF77C808-9618-4EA4-A48C-3C6DF9419DBC@redhat.com \
    --to=echaudro@redhat.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    /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).