From: Thomas Monjalon <thomas@monjalon.net>
To: Andriy Berestovskyy <Andriy.Berestovskyy@caviumnetworks.com>
Cc: dev@dpdk.org, "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Subject: Re: [dpdk-dev] [PATCH 1/5] examples/ip_pipeline: add support for more than 32 CPUs
Date: Fri, 21 Apr 2017 02:16:12 +0200 [thread overview]
Message-ID: <2519560.lxHOCiCOis@xps> (raw)
In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D8912652784549@IRSMSX108.ger.corp.intel.com>
31/03/2017 16:17, Dumitrescu, Cristian:
> > -----Original Message-----
> > From: Andriy Berestovskyy
> > [mailto:Andriy.Berestovskyy@caviumnetworks.com]
> > Sent: Friday, March 31, 2017 2:37 PM
> > To: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>
> > Cc: dev@dpdk.org
> > Subject: [PATCH 1/5] examples/ip_pipeline: add support for more than 32
> > CPUs
> >
> > At the moment ip_pipeline example uses 32 during the initialization,
> > which leads to an error on systems with more than 32 CPUs.
> >
> > Signed-off-by: Andriy Berestovskyy
> > <Andriy.Berestovskyy@caviumnetworks.com>
> > ---
>
> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Series applied, thanks
prev parent reply other threads:[~2017-04-21 0:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 13:36 Andriy Berestovskyy
2017-03-31 13:36 ` [dpdk-dev] [PATCH 2/5] examples/ip_pipeline: avoid panic if link up/down is not supported Andriy Berestovskyy
2017-03-31 14:17 ` Dumitrescu, Cristian
2017-03-31 13:36 ` [dpdk-dev] [PATCH 3/5] port: use mbuf alloc bulk instead of mempool Andriy Berestovskyy
2017-03-31 14:18 ` Dumitrescu, Cristian
2017-03-31 13:36 ` [dpdk-dev] [PATCH 4/5] port: fix file descriptor reader Andriy Berestovskyy
2017-03-31 14:18 ` Dumitrescu, Cristian
2017-03-31 13:36 ` [dpdk-dev] [PATCH 5/5] port: minor typo Andriy Berestovskyy
2017-03-31 14:18 ` Dumitrescu, Cristian
2017-03-31 14:17 ` [dpdk-dev] [PATCH 1/5] examples/ip_pipeline: add support for more than 32 CPUs Dumitrescu, Cristian
2017-04-21 0:16 ` Thomas Monjalon [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=2519560.lxHOCiCOis@xps \
--to=thomas@monjalon.net \
--cc=Andriy.Berestovskyy@caviumnetworks.com \
--cc=cristian.dumitrescu@intel.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).