From: David Marchand <david.marchand@redhat.com>
To: vivkong@ca.ibm.com
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [RFC 00/12] introduce s390x architecture
Date: Wed, 15 May 2019 14:45:06 +0200 [thread overview]
Message-ID: <CAJFAV8yaH5vnOt2sL1-M9FX3Zw5EK6G-44-fQajB6hypapG12g@mail.gmail.com> (raw)
Message-ID: <20190515124506.fOG0gU0rI3iRDNw8npPiORCL5HHq1-nBkiOuVSh1WOs@z> (raw)
In-Reply-To: <CAJFAV8wpLG+YAz5WOqW6qRHcHvZMjDSrUr4P9Q=cMzpgd_G0sg@mail.gmail.com>
Hello,
On Thu, Apr 11, 2019 at 9:45 AM David Marchand <david.marchand@redhat.com>
wrote:
> Hello,
>
> On Tue, Apr 9, 2019 at 9:06 PM Vivian Kong <vivkong@gmail.com> wrote:
>
>> To build and run DPDK on Linux on IBM Z (s390x), big endian support
>> is added and s390x vector intrinics are used in the implementation
>>
>
> intrinsics*
>
> of DPDK libraries.
>>
>> I appreciate your feedback.
>>
>
> Quick check since this is not 19.05 material.
>
> - New files should be Copyright 2019.
> - Avoid copy/paste from Power, noticed a reference to Power in the config
> file.
> - Configuration files are stacked, only enable/disable the needed parts in
> the specific s390 file
> - Meson must be added.
> - No need to add dead code, remove the commented code like:
> //#define dsb(opt) asm volatile("" : : : "memory")
> - Comments using // are banned.
> - No need to introduce a RTE_ACL_CLASSIFY_S390X to map to the scalar code.
> Just avoid the SSE code to be selected in the build framework (iiuc).
> - Avoid introducing empty lines
>
>
> Run check scripts from devtools before submitting:
>
> [dmarchan@dmarchan dpdk]$ ./devtools/checkpatches.sh
>
> ### mk: introduce s390x architecture
>
> WARNING:NO_AUTHOR_SIGN_OFF: Missing Signed-off-by: line by nominal patch
> author 'Vivian Kong <vivkong@gmail.com>'
>
> total: 0 errors, 1 warnings, 61 lines checked
>
> ### eal: add support for s390x architecture
>
> WARNING:NO_AUTHOR_SIGN_OFF: Missing Signed-off-by: line by nominal patch
> author 'Vivian Kong <vivkong@gmail.com>'
>
> total: 0 errors, 1 warnings, 601 lines checked
>
> ### acl: add support for s390x architecture
>
> WARNING:NO_AUTHOR_SIGN_OFF: Missing Signed-off-by: line by nominal patch
> author 'Vivian Kong <vivkong@gmail.com>'
>
> total: 0 errors, 1 warnings, 208 lines checked
>
> ### lpm: add support for s390x architecture
>
> WARNING:NO_AUTHOR_SIGN_OFF: Missing Signed-off-by: line by nominal patch
> author 'Vivian Kong <vivkong@gmail.com>'
>
> total: 0 errors, 1 warnings, 203 lines checked
>
> ### examples/l3fwd: add support for s390x architecture
>
> WARNING:NO_AUTHOR_SIGN_OFF: Missing Signed-off-by: line by nominal patch
> author 'Vivian Kong <vivkong@gmail.com>'
>
> total: 0 errors, 1 warnings, 410 lines checked
>
> ### net/i40e: add support for s390x architecture
>
> WARNING:NO_AUTHOR_SIGN_OFF: Missing Signed-off-by: line by nominal patch
> author 'Vivian Kong <vivkong@gmail.com>'
>
> total: 0 errors, 1 warnings, 0 checks, 647 lines checked
>
> ### test: add support for s390x architecture
>
> WARNING:NO_AUTHOR_SIGN_OFF: Missing Signed-off-by: line by nominal patch
> author 'Vivian Kong <vivkong@gmail.com>'
>
> total: 0 errors, 1 warnings, 192 lines checked
>
> ### hash: add support for s390x architecture
>
> WARNING:NO_AUTHOR_SIGN_OFF: Missing Signed-off-by: line by nominal patch
> author 'Vivian Kong <vivkong@gmail.com>'
>
> total: 0 errors, 1 warnings, 16 lines checked
>
> ### doc: introduce s390x architecture
>
> WARNING:COMMIT_MESSAGE: Missing commit description - Add an appropriate one
>
> WARNING:NO_AUTHOR_SIGN_OFF: Missing Signed-off-by: line by nominal patch
> author 'Vivian Kong <vivkong@gmail.com>'
>
> total: 0 errors, 2 warnings, 24 lines checked
>
> ### ethdev: add cast for bus_device
>
> WARNING:COMMIT_MESSAGE: Missing commit description - Add an appropriate one
>
> WARNING:NO_AUTHOR_SIGN_OFF: Missing Signed-off-by: line by nominal patch
> author 'Vivian Kong <vivkong@gmail.com>'
>
> total: 0 errors, 2 warnings, 8 lines checked
>
> ### mbuf: trivial fix
>
> WARNING:COMMIT_MESSAGE: Missing commit description - Add an appropriate one
>
> WARNING:NO_AUTHOR_SIGN_OFF: Missing Signed-off-by: line by nominal patch
> author 'Vivian Kong <vivkong@gmail.com>'
>
> total: 0 errors, 2 warnings, 8 lines checked
>
> ### test: miscellaneous test fixes
>
> WARNING:NO_AUTHOR_SIGN_OFF: Missing Signed-off-by: line by nominal patch
> author 'Vivian Kong <vivkong@gmail.com>'
>
> total: 0 errors, 1 warnings, 32 lines checked
>
> 0/12 valid patch
>
We are now post 19.05.
This is the right time to propose new features/architectures.
If you want to post a new series, please take into account the previous
comments.
Thanks.
--
David Marchand
next prev parent reply other threads:[~2019-05-15 12:45 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 19:06 Vivian Kong
2019-04-09 19:06 ` Vivian Kong
2019-04-09 19:06 ` [dpdk-dev] [RFC 01/12] mk: " Vivian Kong
2019-04-09 19:06 ` Vivian Kong
2019-04-09 19:38 ` Luca Boccassi
2019-04-09 19:38 ` Luca Boccassi
2019-04-10 16:50 ` Vivian Kong
2019-04-10 16:50 ` Vivian Kong
2019-04-09 19:06 ` [dpdk-dev] [RFC 02/12] eal: add support for " Vivian Kong
2019-04-09 19:06 ` Vivian Kong
2019-04-09 19:06 ` [dpdk-dev] [RFC 03/12] acl: " Vivian Kong
2019-04-09 19:06 ` Vivian Kong
2019-04-09 19:06 ` [dpdk-dev] [RFC 04/12] lpm: " Vivian Kong
2019-04-09 19:06 ` Vivian Kong
2019-04-09 19:06 ` [dpdk-dev] [RFC 05/12] examples/l3fwd: " Vivian Kong
2019-04-09 19:06 ` Vivian Kong
2019-04-09 19:06 ` [dpdk-dev] [RFC 06/12] net/i40e: " Vivian Kong
2019-04-09 19:06 ` Vivian Kong
2019-04-09 19:06 ` [dpdk-dev] [RFC 07/12] test: " Vivian Kong
2019-04-09 19:06 ` Vivian Kong
2019-04-09 19:06 ` [dpdk-dev] [RFC 08/12] hash: " Vivian Kong
2019-04-09 19:06 ` Vivian Kong
2019-04-15 20:43 ` Dharmik Thakkar
2019-04-15 20:43 ` Dharmik Thakkar
2019-04-09 19:06 ` [dpdk-dev] [RFC 09/12] doc: introduce " Vivian Kong
2019-04-09 19:06 ` Vivian Kong
2019-04-09 20:12 ` Thomas Monjalon
2019-04-09 20:12 ` Thomas Monjalon
2019-04-10 16:52 ` Vivian Kong
2019-04-10 16:52 ` Vivian Kong
2019-04-09 19:06 ` [dpdk-dev] [RFC 10/12] ethdev: add cast for bus_device Vivian Kong
2019-04-09 19:06 ` Vivian Kong
2019-04-09 20:14 ` Thomas Monjalon
2019-04-09 20:14 ` Thomas Monjalon
2019-04-10 2:41 ` Stephen Hemminger
2019-04-10 2:41 ` Stephen Hemminger
2019-04-10 17:10 ` Vivian Kong
2019-04-10 17:10 ` Vivian Kong
2019-04-09 19:06 ` [dpdk-dev] [RFC 11/12] mbuf: trivial fix Vivian Kong
2019-04-09 19:06 ` Vivian Kong
2019-04-09 20:13 ` Thomas Monjalon
2019-04-09 20:13 ` Thomas Monjalon
2019-04-09 19:06 ` [dpdk-dev] [RFC 12/12] test: miscellaneous test fixes Vivian Kong
2019-04-09 19:06 ` Vivian Kong
2019-04-09 20:25 ` [dpdk-dev] [RFC 00/12] introduce s390x architecture Thomas Monjalon
2019-04-09 20:25 ` Thomas Monjalon
2019-04-10 17:09 ` Vivian Kong
2019-04-10 17:09 ` Vivian Kong
2019-04-10 17:43 ` Thomas Monjalon
2019-04-10 17:43 ` Thomas Monjalon
2019-04-10 19:15 ` Vivian Kong
2019-04-10 19:15 ` Vivian Kong
2019-04-10 19:46 ` Thomas Monjalon
2019-04-10 19:46 ` Thomas Monjalon
2019-04-10 20:45 ` Vivian Kong
2019-04-10 20:45 ` Vivian Kong
2019-04-10 20:31 ` David Christensen
2019-04-10 20:31 ` David Christensen
2019-04-10 20:46 ` Thomas Monjalon
2019-04-10 20:46 ` Thomas Monjalon
2019-04-10 21:03 ` David Christensen
2019-04-10 21:03 ` David Christensen
2019-04-10 21:45 ` Pradeep Satyanarayana
2019-04-10 21:45 ` Pradeep Satyanarayana
2019-04-11 6:59 ` Thomas Monjalon
2019-04-11 6:59 ` Thomas Monjalon
2019-04-11 15:57 ` Pradeep Satyanarayana
2019-04-11 15:57 ` Pradeep Satyanarayana
[not found] ` <OFB9049735.7E51096E-ON882583D9.00574783-882583D9.00579FE2@LocalDomain>
2019-04-18 21:06 ` Pradeep Satyanarayana
2019-04-18 21:06 ` Pradeep Satyanarayana
2019-04-18 21:18 ` Thomas Monjalon
2019-04-18 21:18 ` Thomas Monjalon
2019-04-11 7:45 ` David Marchand
2019-04-11 7:45 ` David Marchand
2019-05-15 12:45 ` David Marchand [this message]
2019-05-15 12:45 ` David Marchand
2020-02-18 21:03 ` Thomas Monjalon
2020-02-20 0:20 ` Pradeep Satyanarayana
2020-02-21 13:33 ` Vivian Kong
2021-03-24 21:40 ` Thomas Monjalon
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=CAJFAV8yaH5vnOt2sL1-M9FX3Zw5EK6G-44-fQajB6hypapG12g@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=vivkong@ca.ibm.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).