DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: caihe <caihe@huawei.com>, "Zhang, Jerry" <jerry.zhang@intel.com>,
	wangyunjian <wangyunjian@huawei.com>,
	"thomas.monjalon@6wind.com" <thomas.monjalon@6wind.com>,
	"zhangsha (A)" <zhangsha.zhang@huawei.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Lilijun (Jerry)" <jerry.lilijun@huawei.com>,
	Zhoujingbin <zhoujingbin@huawei.com>
Subject: Re: [dpdk-dev] 答复:  [PATCH] config: support 16 sockets server
Date: Wed, 19 Apr 2017 09:49:27 +0000	[thread overview]
Message-ID: <2601191342CEEE43887BDE71AB9772583FAEA920@IRSMSX109.ger.corp.intel.com> (raw)
In-Reply-To: <453363AE6316CC428D594009B784F9050336F47C@SZXEMI508-MBS.china.huawei.com>



> 
> We has already test on 16 node server, everything is fine, without any issue.
> 
> Testcase as follows:
>   I. with dpdk args -c 0xf, test pass
>  II. with 32 forward-lcores, each node with 2 lcores(total 16 nodes), test pass
> III. with forward lcore id greater than 128, test pass
>  IV. with forward and master lcore on node 15, test pass
> 

That's really great to hear, but why default config have to be updated?
Most people don't run dpdk on such powerful boxes, so for them
increasing these config values would be just waste of space.
Why not create your own config instead? 
Konstantin


> BRs
> Herny
> 
> -----邮件原件-----
> 发件人: Zhang, Jerry [mailto:jerry.zhang@intel.com]
> 发送时间: 2017年4月11日 16:49
> 收件人: wangyunjian; thomas.monjalon@6wind.com
> 抄送: dev@dpdk.org; Lilijun (Jerry); Zhoujingbin; caihe
> 主题: RE: [PATCH] config: support 16 sockets server
> 
> On 4/7/2017 9:30 PM, Yunjian Wang wrote:
> >Support 16 sockets server, such as HPE AH337A, Huawei kunlun server etc.
> 
> >Signed-off-by: Henry Cai <caihe@huawei.com>
> >--
> > config/common_base | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> 
> >diff --git a/config/common_base b/config/common_base index 5bdba1d..38561b6 100644
> >--- a/config/common_base
> >+++ b/config/common_base
> >@@ -88,8 +88,8 @@ CONFIG_RTE_CACHE_LINE_SIZE=64  # Compile Environment Abstraction Layer  #  CONFIG_RTE_LIBRTE_EAL=y
> >-CONFIG_RTE_MAX_LCORE=128
> >-CONFIG_RTE_MAX_NUMA_NODES=8
> >+CONFIG_RTE_MAX_LCORE=1024
> >+CONFIG_RTE_MAX_NUMA_NODES=16
> > CONFIG_RTE_MAX_MEMSEG=256
> > CONFIG_RTE_MAX_MEMZONE=2560
> > CONFIG_RTE_MAX_TAILQ=32
> >--
> 
> Did you test it and make sure that there is no issue on 16 node servers?
> 
> BRs,
>   Jerry


  reply	other threads:[~2017-04-19  9:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-19  6:23 caihe
2017-04-19  9:49 ` Ananyev, Konstantin [this message]
2017-04-30 21:01   ` Thomas Monjalon
  -- strict thread matches above, loose matches on Subject: below --
2017-04-07 13:29 [dpdk-dev] " Yunjian Wang
2017-04-11  8:49 ` Zhang, Jerry

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=2601191342CEEE43887BDE71AB9772583FAEA920@IRSMSX109.ger.corp.intel.com \
    --to=konstantin.ananyev@intel.com \
    --cc=caihe@huawei.com \
    --cc=dev@dpdk.org \
    --cc=jerry.lilijun@huawei.com \
    --cc=jerry.zhang@intel.com \
    --cc=thomas.monjalon@6wind.com \
    --cc=wangyunjian@huawei.com \
    --cc=zhangsha.zhang@huawei.com \
    --cc=zhoujingbin@huawei.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).