[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aDDN7qfX-hG3FVub@x130>
Date: Fri, 23 May 2025 12:35:10 -0700
From: "saeed@...nel.org" <saeed@...nel.org>
To: Cosmin Ratiu <cratiu@...dia.com>
Cc: "kuba@...nel.org" <kuba@...nel.org>,
"andrew+netdev@...n.ch" <andrew+netdev@...n.ch>,
"hawk@...nel.org" <hawk@...nel.org>,
"davem@...emloft.net" <davem@...emloft.net>,
"john.fastabend@...il.com" <john.fastabend@...il.com>,
"leon@...nel.org" <leon@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"edumazet@...gle.com" <edumazet@...gle.com>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"ast@...nel.org" <ast@...nel.org>,
"pabeni@...hat.com" <pabeni@...hat.com>,
"richardcochran@...il.com" <richardcochran@...il.com>,
Dragos Tatulea <dtatulea@...dia.com>,
Mark Bloch <mbloch@...dia.com>,
"bpf@...r.kernel.org" <bpf@...r.kernel.org>,
Tariq Toukan <tariqt@...dia.com>,
Saeed Mahameed <saeedm@...dia.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Gal Pressman <gal@...dia.com>,
"daniel@...earbox.net" <daniel@...earbox.net>,
Moshe Shemesh <moshe@...dia.com>
Subject: Re: [PATCH net-next V2 11/11] net/mlx5e: Support ethtool
tcp-data-split settings
On 23 May 16:17, Cosmin Ratiu wrote:
>On Thu, 2025-05-22 at 16:19 -0700, Saeed Mahameed wrote:
>> >
>> > The kernel_param->tcp_data_split here is the user config, right?
>> > It would be cleaner to not support setting SPLIT_DISABLED.
>> > Nothing requires that, you can support just setting AUTO and
>> > ENABLED.
>> >
>>
>> I think I agree, AUTO might require some extra work on the driver
>> side to
>> figure out current internal mode, but it actually makes more sense
>> than
>> just doing "UNKNOWN", UKNOWN here means that HW GRO needs to be
>> enabled
>> when disabling TCP HDR split, and we still don't know if that will
>> work..
>>
>> Cosmin will you look into this ?
>
>Yes, I will address all comments from this round by the next
>submission.
>
I thought about it, maybe we should simplify mlx5:
when hw_gro is not enabled mlx5 should fail tcp_data_split ethtool
settings, and when hw_gro is enabled setting tcp_data_split on mlx5 should
be a no-op.
I think verbosity is important here as mlx5 doesn't support plain
tcp_data_split, it must come with gro_hw ..
reporting tcp_data_split in mlx5 can remain the same as before the series.
We might need to update some tests and script to try hw_gro if enabling
just tcp_data_split didn't work.
for the AUTO state I really have no clue what it means and I think we
should avoid it.
>Cosmin.
Powered by blists - more mailing lists