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] [thread-next>] [day] [month] [year] [list]
Message-ID: <82c37bb4-b2b0-037a-7f63-71324f493e1d@huawei.com>
Date:   Tue, 18 Apr 2023 20:11:42 +0800
From:   Yunsheng Lin <linyunsheng@...wei.com>
To:     "mengyuanlou@...-swift.com" <mengyuanlou@...-swift.com>
CC:     <netdev@...r.kernel.org>, Jiawen Wu <jiawenwu@...stnetic.com>
Subject: Re: [PATCH net-next v2 1/5] net: wangxun: libwx add tx offload
 functions

On 2023/4/18 15:00, mengyuanlou@...-swift.com wrote:
>>> + goto exit;
>>> + case htons(ETH_P_ARP):
>>> + ptype = WX_PTYPE_L2_ARP;
>>> + goto exit;
>>> + default:
>>> + ptype = WX_PTYPE_L2_MAC;
>>
>> Is it ok to set ptype to WX_PTYPE_L2_MAC for first->protocol != ETH_P_IP
>> && first->protocol != ETH_P_IPV6? Does hw need to do checksum/tso or other thing
>> about those packet? if not, setting WX_PTYPE_L2_MAC seems enough?
>>
>     • The hardware needs to parse these packets with these ptype bits.

What does hw do after parsing these packets? Updating some stats according to
the protocol type?
It seems really related to hw implementation, I am just curious if it is worth
the added overhead for driver.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ