From: "Hunt, David" <david.hunt@intel.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org, bruce.richardson@intel.com
Subject: Re: [dpdk-dev] [PATCH v1] doc: add distributor library API change notice
Date: Thu, 9 Feb 2017 17:02:21 +0000 [thread overview]
Message-ID: <365f7928-9143-19da-9467-0a5fe2c9c7f5@intel.com> (raw)
In-Reply-To: <0b17338f-4453-5ca5-06b8-2e8c9d972680@intel.com>
On 9/2/2017 2:20 PM, Ferruh Yigit wrote:
> On 2/6/2017 8:08 AM, David Hunt wrote:
>> Given that the packet distributor library improvements (1) will
>> not be in 17.02, I plan on doing some consolidation of the
>> API for burst operation for 17.05, merging the two api's into
>> one, with options for single or burst operation.
>>
>> (1) http://dpdk.org/dev/patchwork/patch/19911/
>>
>> Signed-off-by: David Hunt <david.hunt@intel.com>
>> ---
>> doc/guides/rel_notes/deprecation.rst | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
>> index 755dc65..925e156 100644
>> --- a/doc/guides/rel_notes/deprecation.rst
>> +++ b/doc/guides/rel_notes/deprecation.rst
>> @@ -55,6 +55,12 @@ Deprecation Notices
>> and will be removed in 17.02.
>> It is replaced by ``rte_mempool_generic_get/put`` functions.
>>
>> +* lib: distributor library API will be changed to incorporate a burst-
>> + oriented API. This will include a change to ``rte_distributor_create``
>> + to specify which type of instance to create (single or burst), and
>> + additional calls for ``rte_poll_pkt_burst`` and ``rte_return_pkt_burst``,
>> + among others.
> Should new APIs (rte_poll_pkt_burst & rte_return_pkt_burst) have
> "rte_distributor_" name space? Apart from this:
>
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
Ferruh,
Thanks for the third Ack.
Thomas,
Would you prefer me to re-spin the patch after inserting
"_distributor" into
the two function names, or would you be so good as to do it during the
merge?
Regards,
Dave.
next prev parent reply other threads:[~2017-02-09 17:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 8:08 David Hunt
2017-02-07 10:50 ` Bruce Richardson
2017-02-07 17:12 ` Van Haaren, Harry
2017-02-09 14:20 ` Ferruh Yigit
2017-02-09 17:02 ` Hunt, David [this message]
2017-02-09 17:49 ` Thomas Monjalon
2017-02-13 16:29 ` 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=365f7928-9143-19da-9467-0a5fe2c9c7f5@intel.com \
--to=david.hunt@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=thomas.monjalon@6wind.com \
/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).