DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Stanislaw Kardach <kda@semihalf.com>
Cc: dev <dev@dpdk.org>, Frank Zhao <Frank.Zhao@starfivetech.com>,
	 Sam Grove <sam.grove@sifive.com>,
	Marcin Wojtas <mw@semihalf.com>,
	upstream@semihalf.com,
	 Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH v4 0/8] Introduce support for RISC-V architecture
Date: Wed, 8 Jun 2022 11:31:46 +0200	[thread overview]
Message-ID: <CAJFAV8wgwonNKVnTrXCYDw7Ty-OUNTWTt3YX0=Cwy66XKmSvPA@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8zN_LVSs+YLrOeSzY5aOY41oqQuES+cvsn4bcN3AQ=wsg@mail.gmail.com>

On Wed, Jun 8, 2022 at 10:41 AM David Marchand
<david.marchand@redhat.com> wrote:
> On Tue, May 31, 2022 at 4:14 PM Stanislaw Kardach <kda@semihalf.com> wrote:
> >
> > This patchset adds support for building and running DPDK on 64bit RISC-V
> > architecture. The initial support targets rv64gc (rv64imafdc) ISA and
> > was tested on SiFive Unmatched development board with the Freedom U740
> > SoC running Linux (freedom-u-sdk based kernel).
> > I have tested this codebase using DPDK unit and perf tests as well as
> > test-pmd, l2fwd and l3fwd examples.
> > The NIC attached to the DUT was Intel X520-DA2 which uses ixgbe PMD.
> > On the UIO side, since U740 does not have an IOMMU, I've used igb_uio,
> > uio_pci_generic and vfio-pci noiommu drivers.
> >
> > Functional verification done using meson tests. fast-tests suite passing with
> > the default config.
> >
> > PMD verification done using a Intel x520-DA2 NIC (ixgbe) and the test-pmd
> > application. Packet transfer checked using all UIO drivers available for
> > non-IOMMU platforms: uio_pci_generic, vfio-pci noiommu and igb_uio.
> >
> > The i40e PMD driver is disabled on RISC-V as the rv64gc ISA has no vector
> > operations.
> >
> > RISCV support is currently limited to Linux as the time measurement frequency
> > discovery is tied to reading a device-tree node via procfs.
> >
> > Clang compilation currently not supported due to issues with missing relocation
> > relaxation.
> >
> > Commit 1 introduces EAL and build system support for RISC-V architecture
> >    as well as documentation updates.
> > Commits 2-5 add missing defines and stubs to enable RISC-V operation in
> >    non-EAL parts.
> > Commit 6 adds RISC-V specific cpuflags test.
> > Commits 7-8 add RISC-V build testing to test-meson-builds.sh and github CI.
>
> Overall, the series lgtm.
> It did not get much reviews, but the porting is straightforward and
> clean enough.
>
> I'm waiting for some compilation to finish and I will merge it for 22.07-rc1.

Welcome to RISC-V in DPDK!

Let's work out the last details in -rc2.
Series applied, thanks.


-- 
David Marchand


  reply	other threads:[~2022-06-08  9:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-31 14:12 Stanislaw Kardach
2022-05-31 14:13 ` [PATCH v4 1/8] eal: add initial " Stanislaw Kardach
2022-05-31 14:13 ` [PATCH v4 2/8] net/ixgbe: enable vector stubs for RISC-V Stanislaw Kardach
2022-05-31 14:13 ` [PATCH v4 3/8] net/memif: set memfd syscall ID on RISC-V Stanislaw Kardach
2022-05-31 14:13 ` [PATCH v4 4/8] net/tap: set BPF syscall ID for RISC-V Stanislaw Kardach
2022-05-31 14:13 ` [PATCH v4 5/8] examples/l3fwd: enable RISC-V operation Stanislaw Kardach
2022-05-31 14:13 ` [PATCH v4 6/8] test/cpuflags: add test for RISC-V cpu flag Stanislaw Kardach
2022-05-31 14:13 ` [PATCH v4 7/8] devtools: add RISC-V to test-meson-builds.sh Stanislaw Kardach
2022-05-31 14:13 ` [PATCH v4 8/8] ci: add RISCV64 cross compilation job Stanislaw Kardach
2022-06-08  8:41 ` [PATCH v4 0/8] Introduce support for RISC-V architecture David Marchand
2022-06-08  9:31   ` David Marchand [this message]
2022-06-08  9:48     ` Stanisław Kardach
2022-06-08  9:51   ` Heinrich Schuchardt
2022-06-08 12:28   ` Stanisław Kardach

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='CAJFAV8wgwonNKVnTrXCYDw7Ty-OUNTWTt3YX0=Cwy66XKmSvPA@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=Frank.Zhao@starfivetech.com \
    --cc=dev@dpdk.org \
    --cc=heinrich.schuchardt@canonical.com \
    --cc=kda@semihalf.com \
    --cc=mw@semihalf.com \
    --cc=sam.grove@sifive.com \
    --cc=thomas@monjalon.net \
    --cc=upstream@semihalf.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).