From: Ivan Nardi <nardi.ivan@gmail.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Beilei Xing <beilei.xing@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
jianfeng.tan@intel.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3] net/i40e: fix allocating hash table on socket 0
Date: Mon, 20 Feb 2017 16:38:39 +0100 [thread overview]
Message-ID: <CAB6Tvp3cOdktjfkrenfLwuLuw64TJn_2awPrpVp4K079Z6rPeQ@mail.gmail.com> (raw)
In-Reply-To: <bf920cf9-33b0-eb9a-b01a-fb88b3d74661@intel.com>
Hi
I reported the same issue 2 weeks ago
http://dpdk.org/ml/archives/dev/2017-February/056930.html
You can reproduce it forcing testpmd to allocate memory only from node 1,
for example:
/tmp/testpmd -d /home/micro/lib/librte_pmd_i40e.so -c 0xFFFC000 -w
0000:81:00.0 -w 0000:81:00.1 -n 4 --socket-mem=0,8192 -- -i
--socket-num=1
Ivan
On 20 February 2017 at 15:45, Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> On 2/17/2017 8:37 AM, Beilei Xing wrote:
> > Testpmd failed to start in another hugetlbfs mount point on
> > i40e,
>
> Hi Beilei,
>
> Can you please describe the failure more. And how to reproduce it.
>
> I prefer initial patch title: "net/i40e: fix fail to start testpmd" but
> with more details about when it fails to start.
>
> the root cause is that hash table is always allocated
> > on socket 0. Fix the issue by assigning scocket id during
> > hash parameter defination.
> >
> > Fixes: 5c53c82c8174 ("net/i40e: store flow director filter")
> > Fixes: 425c3325f0b0 ("net/i40e: store tunnel filter")
> > Fixes: 078259773da9 ("net/i40e: store ethertype filter")
> >
> > Signed-off-by: Beilei Xing <beilei.xing@intel.com>
> <...>
>
next prev parent reply other threads:[~2017-02-20 15:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 2:01 [dpdk-dev] [PATCH] net/i40e: fix fail to start testpmd Beilei Xing
2017-02-15 2:42 ` [dpdk-dev] [PATCH v2] net/i40e: fix allocating hash table on random socket Beilei Xing
2017-02-17 8:37 ` [dpdk-dev] [PATCH v3] net/i40e: fix allocating hash table on socket 0 Beilei Xing
2017-02-20 14:45 ` Ferruh Yigit
2017-02-20 15:38 ` Ivan Nardi [this message]
2017-02-20 16:16 ` Ferruh Yigit
2017-02-20 16:37 ` Ferruh Yigit
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=CAB6Tvp3cOdktjfkrenfLwuLuw64TJn_2awPrpVp4K079Z6rPeQ@mail.gmail.com \
--to=nardi.ivan@gmail.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jianfeng.tan@intel.com \
--cc=jingjing.wu@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).