From: "11" <caowenbo@mucse.com>
To: "'Thomas Monjalon'" <thomas@monjalon.net>, <yaojun@mucse.com>
Cc: <dev@dpdk.org>, <ferruh.yigit@amd.com>,
<andrew.rybchenko@oktetlabs.ru>, <stephen@networkplumber.org>
Subject: RE: [PATCH v6 0/8] [v6]drivers/net Add Support mucse N10 Pmd Driver
Date: Mon, 20 Jan 2025 14:44:52 +0800 [thread overview]
Message-ID: <02457B16529DFDE4+020201db6b06$d6ec7c80$84c57580$@mucse.com> (raw)
In-Reply-To: <2381109.n0HT0TaD9V@thomas>
Hi Thomas,
I will continue to work on it on this quarter,
a more detail servial patchs will be summit after the Spring Festival.
Regards Wenbo
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: 2025年1月17日 0:50
> To: yaojun@mucse.com; Wenbo Cao <caowenbo@mucse.com>
> Cc: dev@dpdk.org; ferruh.yigit@amd.com; andrew.rybchenko@oktetlabs.ru;
> stephen@networkplumber.org
> Subject: Re: [PATCH v6 0/8] [v6]drivers/net Add Support mucse N10 Pmd Driver
>
> Hello,
>
> Is there any plan to resume this work?
>
>
> 01/09/2023 04:30, Wenbo Cao:
> > For This patchset just to support the basic chip init work and user
> > can just found the eth_dev, but can't control more.
> > For Now just support 2*10g nic,the chip can support
> > 2*10g,4*10g,4*1g,8*1g,8*10g.
> > The Feature rx side can support rx-cksum-offload,rss,vlan-filter
> > flow_clow,uncast_filter,mcast_filter,1588,Jumbo-frame
> > The Feature tx side can supprt tx-cksum-offload,tso,vxlan-tso flow
> > director base on ntuple pattern of tcp/udp/ip/ eth_hdr->type for sriov
> > is also support.
> >
> > Because of the chip desgin defect, for multiple-port mode one pci-bdf
> > will have multiple-port (max can have four ports) so this code must be
> > care of one bdf init multiple-port.
>
>
>
>
prev parent reply other threads:[~2025-01-20 6:45 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 2:30 Wenbo Cao
2023-09-01 2:30 ` [PATCH v6 1/8] net/rnp: add skeleton Wenbo Cao
2023-09-05 15:35 ` Ferruh Yigit
2023-09-06 8:15 ` 11
2024-03-29 11:28 ` Ferruh Yigit
2024-03-29 14:45 ` 11
2024-04-02 10:15 ` Ferruh Yigit
2023-09-01 2:30 ` [PATCH v6 2/8] net/rnp: add ethdev probe and remove Wenbo Cao
2023-09-05 15:36 ` Ferruh Yigit
2023-09-06 10:42 ` 11
2023-09-01 2:30 ` [PATCH v6 3/8] net/rnp: add device init and uninit Wenbo Cao
2023-09-05 15:44 ` Ferruh Yigit
2023-09-06 11:03 ` 11
2023-09-01 2:30 ` [PATCH v6 4/8] net/rnp: add mbx basic api feature Wenbo Cao
2023-09-05 15:45 ` Ferruh Yigit
2023-09-06 10:32 ` 11
2023-09-01 2:30 ` [PATCH v6 5/8] net/rnp add reset code for Chip Init process Wenbo Cao
2023-09-05 15:46 ` Ferruh Yigit
2023-09-06 9:23 ` 11
2023-09-01 2:30 ` [PATCH v6 6/8] net/rnp add port info resource init Wenbo Cao
2023-09-05 16:56 ` Ferruh Yigit
2023-09-06 9:07 ` 11
2023-09-01 2:30 ` [PATCH v6 7/8] net/rnp add devargs runtime parsing functions Wenbo Cao
2023-09-05 15:46 ` Ferruh Yigit
2023-09-06 9:13 ` 11
2023-09-01 2:30 ` [PATCH v6 8/8] net/rnp handle device interrupts Wenbo Cao
2023-09-05 15:34 ` [PATCH v6 0/8] [v6]drivers/net Add Support mucse N10 Pmd Driver Ferruh Yigit
2025-01-16 16:49 ` Thomas Monjalon
2025-01-20 6:44 ` 11 [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='02457B16529DFDE4+020201db6b06$d6ec7c80$84c57580$@mucse.com' \
--to=caowenbo@mucse.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
--cc=yaojun@mucse.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).