All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: caihe <caihe@huawei.com>
Cc: dev@dpdk.org, "Ananyev,
	Konstantin" <konstantin.ananyev@intel.com>,
	"Zhang, Jerry" <jerry.zhang@intel.com>,
	wangyunjian <wangyunjian@huawei.com>,
	"zhangsha (A)" <zhangsha.zhang@huawei.com>,
	"Lilijun (Jerry)" <jerry.lilijun@huawei.com>,
	Zhoujingbin <zhoujingbin@huawei.com>
Subject: Re: 答复: [PATCH] config: support 16 sockets server
Date: Sun, 30 Apr 2017 23:01:13 +0200	[thread overview]
Message-ID: <5999666.82pXL9opv5@xps> (raw)
In-Reply-To: <2601191342CEEE43887BDE71AB9772583FAEA920@IRSMSX109.ger.corp.intel.com>

19/04/2017 11:49, Ananyev, Konstantin:
> 
> > 
> > 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? 

I agree.
The default config should not set the maximum values
for the biggest machines.

Rejected

      reply	other threads:[~2017-04-30 21:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-19  6:23 答复: [PATCH] config: support 16 sockets server caihe
2017-04-19  9:49 ` Ananyev, Konstantin
2017-04-30 21:01   ` 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=5999666.82pXL9opv5@xps \
    --to=thomas@monjalon.net \
    --cc=caihe@huawei.com \
    --cc=dev@dpdk.org \
    --cc=jerry.lilijun@huawei.com \
    --cc=jerry.zhang@intel.com \
    --cc=konstantin.ananyev@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.