netdev - Re: [PATCH v4 1/3] Revert "net: usb: ax88179_178a: Bind only to vendor-specific interface"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <3c574f17-cd51-4897-9162-0fd4efb15383@lunn.ch>
Date: Mon, 6 Oct 2025 18:33:51 +0200
From: Andrew Lunn <andrew@...n.ch>
To: yicongsrfy@....com
Cc: oneukum@...e.com, andrew+netdev@...n.ch, davem@...emloft.net,
	edumazet@...gle.com, kuba@...nel.org, linux-usb@...r.kernel.org,
	marcan@...can.st, netdev@...r.kernel.org, pabeni@...hat.com,
	yicong@...inos.cn
Subject: Re: [PATCH v4 1/3] Revert "net: usb: ax88179_178a: Bind only to
 vendor-specific interface"

On Tue, Sep 30, 2025 at 04:07:07PM +0800, yicongsrfy@....com wrote:
> From: Yi Cong <yicong@...inos.cn>
> 
> This reverts commit c67cc4315a8e605ec875bd3a1210a549e3562ddc.
> 
> Currently, in the Linux kernel, USB NIC with ASIX chips use the cdc_ncm
> driver. However, this driver lacks functionality and performs worse than
> the vendor's proprietary driver. In my testing, I have identified the
> following issues:
> 
> 1. The cdc_ncm driver does not support changing the link speed via
>    ethtool because the corresponding callback function is set to NULL.
> 2. The CDC protocol does not support retrieving the network duplex status.
> 3. In TCP_RR and UDP_RR tests, the performance of the cdc_ncm driver
>    is significantly lower than that of the vendor's driver:
> Average of three netperf runs: `netperf -t {TCP/UDP_RR} -H serverIP -l 120`
> - cdc_ncm.ko: TCP_RR: 740, UDP_RR: 750
> - ax88179_178a.ko: TCP_RR: 8900, UDP_RR: 9200
> 
> Issues related to the vendor's driver ax88179_178a.ko will be addressed
> in the next patch.

It looks like there was a lot of discussion somewhere else, because
this patchset jumps from v1 to v4. Please don't change the email
distribution like this.

Also, please start a new thread for each version of the patchset.

      Andrew