DPDK patches and discussions
 help / color / mirror / Atom feed
From: "wangfeifei (J)" <wangfeifei40@huawei.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
	Feifei Wang <wff_light@vip.163.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"chenyi (CY)" <chenyi221@huawei.com>,
	"Wangxin(kunpeng)" <wangxin679@h-partners.com>,
	zengweiliang zengweiliang <zengweiliang.zengweiliang@huawei.com>,
	"Dumin(Dumin,KunPeng)" <dumin3@huawei.com>
Subject: 回复: [RFC 18/18] drivers/net: add hinic3 PMD build and doc files
Date: Sat, 19 Apr 2025 02:52:56 +0000	[thread overview]
Message-ID: <f5ef2df2fa8844c7acaac5ff1d41a826@huawei.com> (raw)
In-Reply-To: <20250418102230.1e4132a1@hermes.local>



-----邮件原件-----
发件人: Stephen Hemminger <stephen@networkplumber.org> 
发送时间: 2025年4月19日 1:23
收件人: Feifei Wang <wff_light@vip.163.com>
抄送: dev@dpdk.org; chenyi (CY) <chenyi221@huawei.com>; Wangxin(kunpeng) <wangxin679@h-partners.com>; wangfeifei (J) <wangfeifei40@huawei.com>
主题: Re: [RFC 18/18] drivers/net: add hinic3 PMD build and doc files

On Fri, 18 Apr 2025 17:06:04 +0800
Feifei Wang <wff_light@vip.163.com> wrote:

> +cflags += [
> +    '-DHW_CONVERT_ENDIAN',
> +    '-D__HINIC_HUAWEI_SECUREC__',
> +    '-fPIC',
> +    '-fstack-protector-strong',
> +]

What is this?
Should not enable PIC or stack-protector at the driver level.
I assume the other stuff is huawei specific compiler flags.

[Feifei] Got it. We will remove this, and should keep it the same as generic way.

> +if arch_subdir == 'arm' and dpdk_conf.get('RTE_ARCH_64')
> +    cflags += ['-D__ARM64_NEON__']
> +else
> +    cflags += ['-D__X86_64_SSE__']
> +endif


This should already be handled in the existing DPDK meson stuff.
Doing it at a per-driver level seems wrong.
[Feifei] Agree, the next version we will fix.

  reply	other threads:[~2025-04-19  2:53 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-18  9:05 [RFC 00/18] add hinic3 PMD driver Feifei Wang
2025-04-18  9:05 ` [RFC 01/18] net/hinic3: add intro doc for hinic3 Feifei Wang
2025-04-18  9:05 ` [RFC 02/18] net/hinic3: add basic header files Feifei Wang
2025-04-18  9:05 ` [RFC 03/18] net/hinic3: add hardware interfaces of BAR operation Feifei Wang
2025-04-18  9:05 ` [RFC 04/18] net/hinic3: add support for cmdq mechanism Feifei Wang
2025-04-18  9:05 ` [RFC 05/18] net/hinic3: add NIC event module Feifei Wang
2025-04-18  9:05 ` [RFC 06/18] net/hinic3: add eq mechanism function code Feifei Wang
2025-04-18  9:05 ` [RFC 07/18] net/hinic3: add mgmt module " Feifei Wang
2025-04-18  9:05 ` [RFC 08/18] net/hinic3: add module about hardware operation Feifei Wang
2025-04-18  9:05 ` [RFC 09/18] net/hinic3: add a NIC business configuration module Feifei Wang
2025-04-18  9:05 ` [RFC 10/18] net/hinic3: add context and work queue support Feifei Wang
2025-04-18  9:05 ` [RFC 11/18] net/hinic3: add a mailbox communication module Feifei Wang
2025-04-18  9:05 ` [RFC 12/18] net/hinic3: add device initailization Feifei Wang
2025-04-18  9:05 ` [RFC 13/18] net/hinic3: add dev ops Feifei Wang
2025-04-18  9:06 ` [RFC 14/18] net/hinic3: add Rx/Tx functions Feifei Wang
2025-04-18  9:06 ` [RFC 15/18] net/hinic3: add MML and EEPROM access feature Feifei Wang
2025-04-18  9:06 ` [RFC 16/18] net/hinic3: add RSS promiscuous ops Feifei Wang
2025-04-18  9:06 ` [RFC 17/18] net/hinic3: add FDIR flow control module Feifei Wang
2025-04-18 18:25   ` Stephen Hemminger
2025-04-18 18:27   ` Stephen Hemminger
2025-04-18 18:28   ` Stephen Hemminger
2025-04-18 18:30   ` Stephen Hemminger
2025-04-18  9:06 ` [RFC 18/18] drivers/net: add hinic3 PMD build and doc files Feifei Wang
2025-04-18 17:22   ` Stephen Hemminger
2025-04-19  2:52     ` wangfeifei (J) [this message]
2025-04-18 18:18 ` [RFC 00/18] add hinic3 PMD driver Stephen Hemminger
2025-04-19  2:44   ` 回复: " wangfeifei (J)
2025-04-18 18:20 ` Stephen Hemminger
2025-04-18 18:32 ` Stephen Hemminger
2025-04-19  3:30   ` 回复: " wangfeifei (J)

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=f5ef2df2fa8844c7acaac5ff1d41a826@huawei.com \
    --to=wangfeifei40@huawei.com \
    --cc=chenyi221@huawei.com \
    --cc=dev@dpdk.org \
    --cc=dumin3@huawei.com \
    --cc=stephen@networkplumber.org \
    --cc=wangxin679@h-partners.com \
    --cc=wff_light@vip.163.com \
    --cc=zengweiliang.zengweiliang@huawei.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).