From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, santosh <santosh.shukla@caviumnetworks.com>,
olivier.matz@6wind.com
Subject: Re: [dpdk-dev] [PATCH] test/mempool_perf: improve default mempool ops selection
Date: Thu, 18 Jan 2018 08:06:01 +0530 [thread overview]
Message-ID: <20180118023559.GA7293@jerin> (raw)
In-Reply-To: <6474871.Z9h4bYXgyi@xps>
-----Original Message-----
> Date: Thu, 18 Jan 2018 00:18:47 +0100
> From: Thomas Monjalon <thomas@monjalon.net>
> To: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> Cc: dev@dpdk.org, santosh <santosh.shukla@caviumnetworks.com>,
> olivier.matz@6wind.com
> Subject: Re: [dpdk-dev] [PATCH] test/mempool_perf: improve default mempool
> ops selection
>
> 12/12/2017 16:12, santosh:
> >
> > On Sunday 19 November 2017 10:25 AM, Jerin Jacob wrote:
> > > Use of rte_eal_mbuf_default_mempool_ops() API will
> > > allow to override pool handler through "--mbuf-pool-ops-name"
> > > eal command line argument.
> > >
> > > Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> > > ---
> >
> > Acked-by: Santosh Shukla <santosh.shukla@caviumnetworks.com>
>
> Do you know why this patch is set as superseded in patchwork?
Changed back to new as it is intended to be.
It might have updated by mistake for the very similar patch heading
"test/mempool: improve default mempool ops selection"
prev parent reply other threads:[~2018-01-18 2:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-19 4:55 Jerin Jacob
2017-12-12 14:33 ` Olivier MATZ
2018-01-18 14:12 ` Thomas Monjalon
2017-12-12 15:12 ` santosh
2018-01-17 23:18 ` Thomas Monjalon
2018-01-18 2:36 ` Jerin Jacob [this message]
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=20180118023559.GA7293@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.com \
--cc=santosh.shukla@caviumnetworks.com \
--cc=thomas@monjalon.net \
/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).