DPDK patches and discussions
 help / color / mirror / Atom feed
From: zhoumin <zhoumin@loongson.cn>
To: David Marchand <david.marchand@redhat.com>
Cc: thomas@monjalon.net, bruce.richardson@intel.com,
	anatoly.burakov@intel.com, qiming.yang@intel.com,
	Yuying.Zhang@intel.com, jgrajcia@cisco.com,
	konstantin.v.ananyev@yandex.ru, dev@dpdk.org,
	maobibo@loongson.cn
Subject: Re: [PATCH v8 0/6] Introduce support for LoongArch architecture
Date: Thu, 6 Oct 2022 20:48:34 +0800	[thread overview]
Message-ID: <ec4a1ad5-7901-f271-b2ed-be620af00dbd@loongson.cn> (raw)
In-Reply-To: <CAJFAV8x3AQj1wahzEBiG9Zrb-b8TDtHkhFhD7hm+rtu8xq9j5Q@mail.gmail.com>

Hi, David,

It is hard to find words to express my gratitude.


On Thu, Oct 6, 2022 at 19:49, David Marchand wrote:
> Hello Min,
>
> On Tue, Oct 4, 2022 at 5:41 PM Min Zhou <zhoumin@loongson.cn> wrote:
>> Dear team,
>>
>> The following patch set is intended to support DPDK running on LoongArch
>> architecture.
>>
>> LoongArch is the general processor architecture of Loongson Corporation
>> and is a new RISC ISA, which is a bit like MIPS or RISC-V.
>>
>> The online documents of LoongArch architecture are here:
>>      https://loongson.github.io/LoongArch-Documentation/README-EN.html
>>
>> The latest build tools for LoongArch (binary) can be downloaded from:
>>      https://github.com/loongson/build-tools
>>
>> If you want to generate your own cross toolchain, you can refer to
>> this thread:
>>      https://inbox.dpdk.org/dev/53b50799-cb29-7ee6-be89-4fe21566e127@loongson.cn/T/#m1da99578f85894a4ddcd8e39d8239869e6a501d1
>>  From the link above, you can find a script to do that.
>>
>> v8:
>>      - rebase the patchset on the main repository
>>      - add meson build test for LoongArch in devtools/test-meson-builds.sh
>>      - add ccache to build configuration file
>>      - change the cpp meson variable to a c++ compiler
>>      - complete the cross compilation documentation for LoongArch, adding
>>        reference to the build script and dependency list
>>      - put the feature description for LoongArch in the EAL features list
>>        in release_22_11.rst
>>      - simplify macro definition for new added headers
>>      - put the items about LoongArch in the right place in meson.build
> Thanks for this last revision.
>
> We discussed a few things offlist, let me sumarize here for others:
> - I fixed a few style issues, re-arranged the documentation around the
> cross toolchain generation from sources,


Thanks a lot for your review and help.


> - on your side, LoongSon is building a CI system so that we have non
> regression compilation tests reports in DPDK patchwork, hopefully, by
> -rc3 time.


Yes, thanks. We will keep the deadline and try our best to provide a 
stable CI system for LoongArch.

>    As for adding more tests run by this CI, this can be discussed later,
>

Yes, thanks. There are also some important issues to discuss.


> The last build fixes for GCC 12 have been merged by Thomas.
> There is nothing blocking for merging this series.
>
> Welcome to LoongArch in DPDK!
>
> Series applied.


Thanks a lot. It is the beginning for LoongArch platform to benefit from 
DPDK community. I expect DPDK

will become more and more prosperous on LoongArch.


Thanks,

Min Zhou

>
>


      reply	other threads:[~2022-10-06 12:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-04 15:40 Min Zhou
2022-10-04 15:40 ` [PATCH v8 1/6] eal/loongarch: support " Min Zhou
2022-10-04 15:40 ` [PATCH v8 2/6] net/ixgbe: add vector stubs for LoongArch Min Zhou
2022-10-04 15:40 ` [PATCH v8 3/6] net/memif: set memfd syscall ID on LoongArch Min Zhou
2022-10-04 15:40 ` [PATCH v8 4/6] net/tap: set BPF syscall ID for LoongArch Min Zhou
2022-10-04 15:40 ` [PATCH v8 5/6] examples/l3fwd: enable LoongArch operation Min Zhou
2022-10-04 15:40 ` [PATCH v8 6/6] test/cpuflags: add test for LoongArch cpu flag Min Zhou
2022-10-06 11:49 ` [PATCH v8 0/6] Introduce support for LoongArch architecture David Marchand
2022-10-06 12:48   ` zhoumin [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=ec4a1ad5-7901-f271-b2ed-be620af00dbd@loongson.cn \
    --to=zhoumin@loongson.cn \
    --cc=Yuying.Zhang@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=jgrajcia@cisco.com \
    --cc=konstantin.v.ananyev@yandex.ru \
    --cc=maobibo@loongson.cn \
    --cc=qiming.yang@intel.com \
    --cc=thomas@monjalon.net \
    /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).