DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: WanRenyong <wanry@yunsilicon.com>, dev@dpdk.org
Cc: thomas@monjalon.net
Subject: Re: [PATCH v2 00/19] XSC PMD for Yunsilicon NICs
Date: Wed, 11 Sep 2024 09:51:20 +0100	[thread overview]
Message-ID: <9d3586eb-027d-4d1b-9159-8c00a65158f4@amd.com> (raw)
In-Reply-To: <20240911020740.3950704-1-wanry@yunsilicon.com>

On 9/11/2024 3:07 AM, WanRenyong wrote:
> This xsc PMD (**librte_net_xsc**) provides poll mode driver for 
> Yunsilicon metaScale serials NICs.
> 
> Features:
> ---------
> - MTU update
> - TSO
> - RSS hash
> - RSS key update
> - RSS reta update
> - L3 checksum offload
> - L4 checksum offload
> - Inner L3 checksum
> - Inner L4 checksum
> - Basic stats 
> 
> Support NICs:
> -------------
> - metaScale-200S   Single QSFP56 Port 200GE SmartNIC
> - metaScale-200    Quad QSFP28 Ports 100GE SmartNIC
> - metaScale-50     Dual QSFP28 Port 25GE SmartNIC
> - metaScale-100Q   Quad QSFP28 Port 25GE SmartNIC
> 
> 
> ---
> WanRenyong (19):
>   net/xsc: add doc and minimum build framework
>   net/xsc: add log macro
>   net/xsc: add PCI device probe and remove
>   net/xsc: add xsc device init and uninit
>   net/xsc: add ioctl command interface
>   net/xsc: initialize hardware information
>   net/xsc: add representor ports probe
>   net/xsc: create eth devices for representor ports
>   net/xsc: initial representor eth device
>   net/xsc: add ethdev configure and rxtx queue setup ops
>   net/xsc: add mailbox and structure
>   net/xsc: add ethdev RSS hash ops
>   net/xsc: add ethdev start and stop ops
>   net/xsc: add ethdev Rx burst
>   net/xsc: add ethdev Tx burst
>   net/xsc: configure xsc device hardware table
>   net/xsc: add dev link and MTU ops
>   net/xsc: add dev infos get
>   net/xsc: add dev basic stats ops
>

Hi WanRenyong,

Thanks for upstreaming the driver,
I did not had a chance to check in detail yet, but when sending next
version can you please send patch series as threaded, with following
git-send-email arguments:
`--thread --no-chain-reply-to`

Or this can be added to .gitconfig as documented in [1].


Also there is new PMD upstreaming guide work in progress [2], current
version still can be useful, can you please check it.

Thanks,
ferruh


[1]
https://old.dpdk.org/dev

[2]
https://patches.dpdk.org/project/dpdk/patch/20240910145801.46186-1-nandinipersad361@gmail.com/

  reply	other threads:[~2024-09-11  8:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-11  2:07 WanRenyong
2024-09-11  8:51 ` Ferruh Yigit [this message]
2024-09-11 10:23   ` WanRenyong

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=9d3586eb-027d-4d1b-9159-8c00a65158f4@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=wanry@yunsilicon.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).