From: Thomas Monjalon <thomas@monjalon.net>
To: Joyce Kong <joyce.kong@arm.com>
Cc: dev@dpdk.org, jerin.jacob@caviumnetworks.com,
Honnappa.Nagarahalli@arm.com, gavin.hu@arm.com,
hemant.agrawal@nxp.com
Subject: Re: [dpdk-dev] [PATCH v1 0/2] change max core number to 256 for Arm64 platform
Date: Wed, 21 Nov 2018 12:13:44 +0100 [thread overview]
Message-ID: <3572730.Ena04EuRj2@xps> (raw)
In-Reply-To: <1542798625-46722-1-git-send-email-joyce.kong@arm.com>
Hi,
21/11/2018 12:10, Joyce Kong:
> v1: change the max core setting to 256 for arm64 platform
>
> Joyce Kong (2):
> config: enable more than 128 cores for Arm platform
> config: enable more than 128 cores for meson build
2 comments:
- It doesn't need to be split in 2 commits.
- Are you sure you want this change in 18.11? No risk?
next prev parent reply other threads:[~2018-11-21 11:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 11:10 Joyce Kong
2018-11-21 11:10 ` [dpdk-dev] [PATCH v1 1/2] config: enable more than 128 cores for Arm platform Joyce Kong
2018-11-21 11:10 ` [dpdk-dev] [PATCH v1 2/2] config: enable more than 128 cores for meson build Joyce Kong
2018-11-21 11:13 ` Thomas Monjalon [this message]
2018-11-21 11:41 ` [dpdk-dev] [PATCH v1 0/2] change max core number to 256 for Arm64 platform Joyce Kong (Arm Technology China)
2018-11-21 20:09 ` Stephen Hemminger
2018-11-21 11:27 ` [dpdk-dev] [PATCH v2] config: enable more than 128 cores " Joyce Kong
2018-11-21 11:34 ` Jerin Jacob
2018-11-22 7:01 ` Joyce Kong (Arm Technology China)
2018-11-22 7:01 ` [dpdk-dev] [PATCH v3] " Joyce Kong
2018-11-22 7:08 ` Jerin Jacob
2018-11-22 7:43 ` Joyce Kong (Arm Technology China)
2018-11-22 7:37 ` [dpdk-dev] [PATCH v4] " Joyce Kong
2018-11-22 11:04 ` Jerin Jacob
2018-11-23 0:49 ` 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=3572730.Ena04EuRj2@xps \
--to=thomas@monjalon.net \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=gavin.hu@arm.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=joyce.kong@arm.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).