From: Stephen Hemminger <stephen@networkplumber.org>
To: Ruifeng Wang <Ruifeng.Wang@arm.com>
Cc: Supriya Shekhar Mane <sm.supriya@globaledgesoft.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
Chandrakant Sharpa <s.chandrakant@globaledgesoft.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Zaheer R M <zaheer.rm@globaledgesoft.com>,
Gurusidhesh G H <gurusidhesh.gh@globaledgesoft.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
Jan Viktorin <viktorin@rehivetech.com>,
"jerinj@marvell.com" <jerinj@marvell.com>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH] Add Armv7 support
Date: Mon, 17 Jul 2023 09:50:46 -0700 [thread overview]
Message-ID: <20230717095046.22151b0a@hermes.local> (raw)
In-Reply-To: <AM5PR0802MB24652906646497615B0667A99E079@AM5PR0802MB2465.eurprd08.prod.outlook.com>
On Thu, 24 Jun 2021 06:58:15 +0000
Ruifeng Wang <Ruifeng.Wang@arm.com> wrote:
> >
> > Do you have any plan on CI?
> > I don't think DPDK Lab has Armv7 hardware to run tests.
> Yes, we do have plans for CI for armv7, We are currently conducting
> our testing with WPJ419 platform. I would like to note what all things
> that should be taken into consideration for making CI support for armv7
> related contributions.
> [Ruifeng] I think basically we should have build for armv7. And in-tree unit tests are also preferred to run.
> For traffic/performance tests, it is good to have.
>
> Aso, we would like know how the testing for armv7 was done in older
> DPDK releases, and what all things were considered, so that we can follow
> the same.
> [Ruifeng] As I know, there was no public CI for armv7 in older releases.
>
> Regards,
> Supriya Mane
This patch is over 2 years old. Has there been any progress on it?
Does it still make sense?
What is missing?
next prev parent reply other threads:[~2023-07-17 16:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 11:18 [dpdk-dev] [PATCH] Add Armv7 support s.chandrakant
2021-06-17 7:51 ` Thomas Monjalon
2021-06-18 6:19 ` Supriya Shekhar Mane
2021-06-23 6:35 ` Ruifeng Wang
2021-06-24 6:21 ` Supriya Shekhar Mane
2021-06-24 6:58 ` Ruifeng Wang
2023-07-17 16:50 ` Stephen Hemminger [this message]
2023-07-18 3:22 ` Ruifeng Wang
2021-11-16 12:13 ` Juraj Linkeš
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=20230717095046.22151b0a@hermes.local \
--to=stephen@networkplumber.org \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=gurusidhesh.gh@globaledgesoft.com \
--cc=jerinj@marvell.com \
--cc=nd@arm.com \
--cc=s.chandrakant@globaledgesoft.com \
--cc=sm.supriya@globaledgesoft.com \
--cc=thomas@monjalon.net \
--cc=viktorin@rehivetech.com \
--cc=zaheer.rm@globaledgesoft.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.