From: Thomas Monjalon <thomas@monjalon.net>
To: Yutang Jiang <jiangyutang@os.amperecomputing.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"patches@amperecomputing.com" <patches@amperecomputing.com>,
"yutang.jiang@amperecomputing.com"
<yutang.jiang@amperecomputing.com>, nd <nd@arm.com>,
"juraj.linkes@pantheon.tech" <juraj.linkes@pantheon.tech>,
nd <nd@arm.com>, Ruifeng Wang <Ruifeng.Wang@arm.com>
Subject: Re: [PATCH v2] config/arm: add Ampere Altra/AltraMax/AmpereOne platform
Date: Wed, 28 Jun 2023 00:00:43 +0200 [thread overview]
Message-ID: <2060119.K71DO8KEF6@thomas> (raw)
In-Reply-To: <AS8PR08MB7080EE664DB2450EF1F469F89E58A@AS8PR08MB7080.eurprd08.prod.outlook.com>
16/06/2023 05:17, Ruifeng Wang:
> > -----Original Message-----
> > From: Yutang Jiang <jiangyutang@os.amperecomputing.com>
> > Sent: Thursday, June 15, 2023 7:24 PM
> > To: dev@dpdk.org
> > Cc: patches@amperecomputing.com; yutang.jiang@amperecomputing.com;
> > jiangyutang@os.amperecomputing.com; Ruifeng Wang <Ruifeng.Wang@arm.com>; nd <nd@arm.com>;
> > juraj.linkes@pantheon.tech
> > Subject: [PATCH v2] config/arm: add Ampere Altra/AltraMax/AmpereOne platform
> >
> > This patch add Ampere series platform support for DPDK:
> > 1. Merging the eMAG and AmpereOne to the one struct implementer_ampere.
> > 2. The microarchitecture of Altra/AltraMax is N1, which implementer/part_number
> > is defined in arm, so the definition of RTE_MAX_LCORE/RTE_MAX_NUMA_NODES
> > refers to the quadrant sub-numa definition in AltraMax 2P system.
> > 3. Added basic definition of AmpereOne.
> >
> > Signed-off-by: Yutang Jiang <jiangyutang@os.amperecomputing.com>
>
> Acked-by: Ruifeng Wang <ruifeng.wang@arm.com>
Sorted alphabetically and applied, thanks.
prev parent reply other threads:[~2023-06-27 22:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 11:24 Yutang Jiang
2023-06-16 3:17 ` Ruifeng Wang
2023-06-27 22:00 ` 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=2060119.K71DO8KEF6@thomas \
--to=thomas@monjalon.net \
--cc=Ruifeng.Wang@arm.com \
--cc=dev@dpdk.org \
--cc=jiangyutang@os.amperecomputing.com \
--cc=juraj.linkes@pantheon.tech \
--cc=nd@arm.com \
--cc=patches@amperecomputing.com \
--cc=yutang.jiang@amperecomputing.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).