[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y+wCMY+4FqTouFih@x130>
Date: Tue, 14 Feb 2023 13:50:41 -0800
From: Saeed Mahameed <saeed@...nel.org>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Mark Bloch <mbloch@...dia.com>,
"David S. Miller" <davem@...emloft.net>,
Paolo Abeni <pabeni@...hat.com>,
Eric Dumazet <edumazet@...gle.com>,
Saeed Mahameed <saeedm@...dia.com>, netdev@...r.kernel.org,
Tariq Toukan <tariqt@...dia.com>, Roi Dayan <roid@...dia.com>,
Maor Dickman <maord@...dia.com>
Subject: Re: [net-next 01/15] net/mlx5: Lag, Let user configure multiport
eswitch
On 14 Feb 12:40, Jakub Kicinski wrote:
>On Tue, 14 Feb 2023 09:31:10 +0200 Mark Bloch wrote:
>> > Oh, the "legacy software where updating the logic isn't possible"
>> > sounds concerning. Do we know what those cases are? Can we perhaps
>> > constrain them to run on a specific version of HW (say starting with
>> > CX8 the param will no longer be there and only the right behavior will
>> > be supported upstream)?
>>
>> While I can encourage customers to update their software to deal with
>> this new mode it's up to them. As you already know, it's hard to change
>> customers infrastructure so quickly. These things take time. They plan
>> on running multiple hardware generations on top of the same software.
>> I'll keep pushing on making this mode the default one.
>
>I think we should document some time horizon. We can always push it
>back but having a concrete plan in place may motive users. Also it's
>useful to point at and say "we warned you".
>
>Doesn't have to be anything very imminent, time flies.
Makes sense, will add to documentation..
Thanks.
Powered by blists - more mailing lists