DPDK patches and discussions
 help / color / mirror / Atom feed
From: Olivier Matz <olivier.matz@6wind.com>
To: Andrew Rybchenko <arybchenko@solarflare.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] doc: announce API/ABI changes for mempool
Date: Wed, 31 Jan 2018 17:46:51 +0100	[thread overview]
Message-ID: <20180131164651.ne2f77ivs7brhbep@platinum> (raw)
In-Reply-To: <1516713784-11605-1-git-send-email-arybchenko@solarflare.com>

On Tue, Jan 23, 2018 at 01:23:04PM +0000, Andrew Rybchenko wrote:
> An API/ABI changes are planned for 18.05 [1]:
> 
>  * Allow to customize how mempool objects are stored in memory.
>  * Deprecate mempool XMEM API.
>  * Add mempool driver ops to get information from mempool driver and
>    dequeue contiguous blocks of objects if driver supports it.
> 
> [1] http://dpdk.org/ml/archives/dev/2018-January/088698.html
> 
> Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com>

Acked-by: Olivier Matz <olivier.matz@6wind.com>

  reply	other threads:[~2018-01-31 16:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-23 13:23 Andrew Rybchenko
2018-01-31 16:46 ` Olivier Matz [this message]
2018-02-01  6:40   ` Jerin Jacob
2018-02-01 12:53     ` Hemant Agrawal
2018-02-14 15:23       ` 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=20180131164651.ne2f77ivs7brhbep@platinum \
    --to=olivier.matz@6wind.com \
    --cc=arybchenko@solarflare.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).