DPDK patches and discussions
 help / color / mirror / Atom feed
From: Olivier Matz <olivier.matz@6wind.com>
To: Shreyansh Jain <shreyansh.jain@nxp.com>
Cc: <dev@dpdk.org>, <thomas.monjalon@6wind.com>,
	<hemant.agrawal@nxp.com>, <david.hunt@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3 3/3] mempool: introduce stack mempool driver
Date: Fri, 31 Mar 2017 15:50:00 +0200	[thread overview]
Message-ID: <20170331155000.02a859bb@platinum> (raw)
In-Reply-To: <1490938537-1177-3-git-send-email-shreyansh.jain@nxp.com>

On Fri, 31 Mar 2017 11:05:37 +0530, Shreyansh Jain <shreyansh.jain@nxp.com> wrote:
> Moved from lib/librte_mempool, stack mempool handler is an independent
> driver.
> Shared builds would now require to link in librte_mempool_stack for
> "stack" mempool handler.
> 
> Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com>

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

  reply	other threads:[~2017-03-31 13:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <11490938158-936-1-git-send-email-shreyansh.jain@nxp.com>
2017-03-31  5:35 ` [dpdk-dev] [PATCH v3 1/3] mempool: fix segfault when shared mempool handler not linked Shreyansh Jain
2017-03-31  5:35   ` [dpdk-dev] [PATCH v3 2/3] mempool: introduce ring mempool driver Shreyansh Jain
2017-03-31 13:49     ` Olivier Matz
2017-03-31  5:35   ` [dpdk-dev] [PATCH v3 3/3] mempool: introduce stack " Shreyansh Jain
2017-03-31 13:50     ` Olivier Matz [this message]
2017-03-31  5:41   ` [dpdk-dev] [PATCH v3 1/3] mempool: fix segfault when shared mempool handler not linked Shreyansh Jain
2017-03-31 13:44     ` Olivier Matz
2017-03-31 13:49   ` Olivier Matz
2017-04-03 16:58     ` 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=20170331155000.02a859bb@platinum \
    --to=olivier.matz@6wind.com \
    --cc=david.hunt@intel.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=shreyansh.jain@nxp.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).