From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Liu Xiaofeng <xiaofeng.liu@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] app/testpmd: check socket id validity
Date: Wed, 30 Apr 2014 14:24:28 +0200 [thread overview]
Message-ID: <1940594.10Qg9mfMu6@xps13> (raw)
In-Reply-To: <1397569899-18315-1-git-send-email-david.marchand@6wind.com>
2014-04-15 15:51, David Marchand:
> From: Liu Xiaofeng <xiaofeng.liu@6wind.com>
>
> Now socket id is from device's numa_node, if it is invalid, just set it to 0
> as default to avoid crash which will be caused by the reference to
> port_per_socket[socket_id].
>
> Also one warning is displayed to user that port-numa-config and
> ring-numa-config parameters should be used along with --numa for NUMA mode.
>
> A check for NUMA_NO_CONFIG was also missing from init_fwd_stream().
>
> Signed-off-by: Liu Xiaofeng <xiaofeng.liu@6wind.com>
Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
Applied for version 1.6.0r2.
Thanks
--
Thomas
prev parent reply other threads:[~2014-04-30 12:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 13:51 David Marchand
2014-04-30 12:24 ` 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=1940594.10Qg9mfMu6@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=xiaofeng.liu@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).