From: "Wu, Jingjing" <jingjing.wu@intel.com>
To: "Pei, Yulong" <yulong.pei@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH v5] app/testpmd: fix port_numa and ring_numa not initialize issue
Date: Sat, 6 May 2017 00:52:16 +0000 [thread overview]
Message-ID: <9BB6961774997848B5B42BEC655768F810D623C3@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1493807387-135918-1-git-send-email-yulong.pei@intel.com>
> -----Original Message-----
> From: Pei, Yulong
> Sent: Wednesday, May 3, 2017 6:30 PM
> To: dev@dpdk.org
> Cc: Wu, Jingjing <jingjing.wu@intel.com>; thomas@monjalon.net
> Subject: [PATCH v5] app/testpmd: fix port_numa and ring_numa not initialize
> issue
>
> Previous numa_support = 0 by default, it need to add --numa to testpmd
> command line to enable numa, so port_numa and ring_numa were initialized at
> function launch_args_parse(), now testpmd change numa_support = 1 as default,
> so port_numa and ring_numa also need to initialize by default, otherwise port-
> >socket_id will be probed to wrong value.
>
> Fixes: 999b2ee0fe45 ("app/testpmd: enable NUMA support by default")
>
> Signed-off-by: Yulong Pei <yulong.pei@intel.com>
Acked-by: Jingjing Wu <jingjing.wu@intel.com>
next prev parent reply other threads:[~2017-05-06 0:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 2:01 [dpdk-dev] [PATCH v4] app/testpmd: initialize port_numa and ring_numa Yulong Pei
2017-04-28 8:30 ` Wu, Jingjing
2017-05-01 13:35 ` Thomas Monjalon
2017-05-03 10:27 ` [dpdk-dev] [PATCH] app/testpmd: fix port_numa and ring_numa not initialize issue Yulong Pei
2017-05-03 10:29 ` [dpdk-dev] [PATCH v5] " Yulong Pei
2017-05-06 0:52 ` Wu, Jingjing [this message]
2017-05-06 8:30 ` 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=9BB6961774997848B5B42BEC655768F810D623C3@SHSMSX103.ccr.corp.intel.com \
--to=jingjing.wu@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
--cc=yulong.pei@intel.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).