On 2022年07月21日 00:33, David Marchand wrote:
Hello, On Mon, Jun 6, 2022 at 3:11 PM Min Zhou <[email protected]> wrote:Dear team, The following patch set is intended to support DPDK running on LoongArch architecture. LoongArch is the general processor architecture of Loongson and is a new RISC ISA, which is a bit like MIPS or RISC-V. The online documents of LoongArch are here: https://loongson.github.io/LoongArch-Documentation/README-EN.html The latest cross compile tool chain can be downloaded from: https://github.com/loongson/build-tools v3: - add URL for cross compile tool chain - remove rte_lpm_lsx.h which was a dummy vector implementation because there is already a scalar implementation, thanks to Michal Mazurek - modify the name of compiler for cross compiling - remove useless variable in meson.build v2: - use standard atomics of toolchain to implement atomic operations - implement spinlock based on standard atomicsThanks for porting DPDK to a new architecture. I am unsure of what this architecture status is wrt to the upstream Linux kernel and wrt to main distributions support. Could you give some details?
The upstream Linux kernel has merged the majority of the LoongArch architecture code for Linux 5.19, including the final system call interface and all core functionality. However, It still misses some patches to add support for other subsystems, which currently under review. Due to some of the code not yet passing review, Linux 5.19 cannot boot on LoongArch system. Presumably by the time of the Linux 5.20 kernel cycle later this summer the rest of the required driver support will pass review to yield a bootable LoongArch system. The GLIBC LoongArch support is likely to be mainlined for GLIBC 2.36 on or around August 1st, 2022. The LoongArch port for GCC has been merged for GCC 12. For lacking the complete upstream support for these significant projects, there is no main distribution yet for upstream Linux kernel of LoongArch.
Otherwise, I did not look at the series yet, but it needs to be rebased on the main repository, there have been quite some changes since this original submission.
I have rebased the patchset on the main repository and will send it later.
How will this architecture be integrated wrt CI: GHA? sending your hw to UNH lab? or maybe do you have plans for your own CI servers?
There are some public repositories that all have loongson branches maintained by ourselves, which will be submit to upstream project, under Loongson organization on github: https://github.com/loongson. We can build a CI server that can be accessed externally based on these repositories. However, I want to know how to integrate the CI server we build into the patch review process of DPDK.
-- Thanks, Min Zhou
