patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Shahaf Shuler <shahafs@mellanox.com>
To: "Wu, Jingjing" <jingjing.wu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Thomas Monjalon <thomas@monjalon.net>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH v2] app/testpmd: support non contiguous socket ids
Date: Sun, 7 May 2017 06:06:03 +0000	[thread overview]
Message-ID: <AM4PR05MB150554A6988276FBE9467723C3E90@AM4PR05MB1505.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <9BB6961774997848B5B42BEC655768F810D624B2@SHSMSX103.ccr.corp.intel.com>

Saturday, May 6, 2017 4:41 AM, Wu, Jingjing:
> >
> > The test assumes the socket ids are contiguous. This is not
> > necessarily the case on all servers and may cause mempool creation to fail.
> >
> > Fixing it by detecting the list of valid socket ids and use it for the
> > mempool creation.
> >
> > Fixes: 7acf894d07d1 ("app/testpmd: detect numa socket count")
> >
> > CC: stable@dpdk.org
> > Signed-off-by: Shahaf Shuler <shahafs@mellanox.com>
> > ---
> > on v2:
> >  * fix minor typo on commit message : be->by.
> > ---
> >  app/test-pmd/parameters.c | 38 ++++++++++++++++++++++++++++-----
> -----
> >  app/test-pmd/testpmd.c    | 38 +++++++++++++++++++++++++++++------
> ---
> >  app/test-pmd/testpmd.h    |  4 +++-
> >  3 files changed, 60 insertions(+), 20 deletions(-)
> >

[..]

> > diff --git a/app/test-pmd/testpmd.c b/app/test-pmd/testpmd.c index
> > dfe64427d..a556a8aff 100644
> > --- a/app/test-pmd/testpmd.c
> > +++ b/app/test-pmd/testpmd.c

[..]

> > +/*
> >   * Setup default configuration.
> >   */
> >  static void
> > @@ -388,12 +405,14 @@ set_default_fwd_lcores_config(void)
> >
> >  	nb_lc = 0;
> >  	for (i = 0; i < RTE_MAX_LCORE; i++) {
> > -		sock_num = rte_lcore_to_socket_id(i) + 1;
> > -		if (sock_num > max_socket) {
> > -			if (sock_num > RTE_MAX_NUMA_NODES)
> > -				rte_exit(EXIT_FAILURE, "Total sockets
> greater
> > than %u\n", RTE_MAX_NUMA_NODES);
> > -			max_socket = sock_num;
> > +		sock_num = rte_lcore_to_socket_id(i);
> +1 is missed?

I don't think so.
On previous implementation this logic was meant to find the max_socket. 
max_socket was the first invalid socket_id and was used, for example :

if (socket_id >= max_socket) {

or

for (i = 0; i < max_socket; i++)

now, on above logic, we list the valid socket id. Therefore rte_lcore_to_socket_id return a valid id and not need to add 1.

  reply	other threads:[~2017-05-07  6:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-03 13:44 Shahaf Shuler
2017-05-06  1:41 ` Wu, Jingjing
2017-05-07  6:06   ` Shahaf Shuler [this message]
2017-05-08  0:54     ` Wu, Jingjing
2017-05-08 17:35       ` Shahaf Shuler
2017-05-09  0:43         ` Wu, Jingjing
2017-05-07 12:14 ` [dpdk-stable] [dpdk-dev] " Thomas Monjalon
2017-05-07 13:05 ` [dpdk-stable] [PATCH v3] " Shahaf Shuler
2017-05-09  7:28   ` [dpdk-stable] [PATCH v4] app/testpmd: fix mempool creation by socket id Shahaf Shuler
2017-05-09  8:54     ` Wu, Jingjing
2017-05-10 16:41       ` [dpdk-stable] [dpdk-dev] " 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=AM4PR05MB150554A6988276FBE9467723C3E90@AM4PR05MB1505.eurprd05.prod.outlook.com \
    --to=shahafs@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.com \
    --cc=stable@dpdk.org \
    --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).