From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 79807C05027 for ; Tue, 14 Feb 2023 21:50:48 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232064AbjBNVur (ORCPT ); Tue, 14 Feb 2023 16:50:47 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42326 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229546AbjBNVuq (ORCPT ); Tue, 14 Feb 2023 16:50:46 -0500 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3EE2976AF for ; Tue, 14 Feb 2023 13:50:45 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id E2D6BB81ECF for ; Tue, 14 Feb 2023 21:50:43 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 964FFC433EF; Tue, 14 Feb 2023 21:50:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1676411442; bh=U5rCXAJbnB4tMbYtMrhoddzf1X5kywHklQMHSj8T3j0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=IcxVVwMrn8er5Hh9POcO2kpoR+Zoautdz06kHgmG0BXAHeAuXshSbAry5ajvNPi5u J4lxqvNFz2Z0moKR/P74vPFbSgrxze6WHhEo3qSlG3FWZi1bubSH5xg43mBu5SyJFz JTchspA6yO46qU4TwHaT4v9SzwQyh2ezX+0HvTtvkCpPsD5L6e/TrQZfYvKuHuSXtB wwws++fe2NwYheaTGRtYpiF76WLuyM/f13CZa91oDRv/p4rWff6dOUdDFzdWbjEtlS ixaINaABz7OeUzyhKBHEuRF5/StLjgW9RU5jtzIZC1DZhHRbbIQo3/5N/FRNr6LjML BNpbivlDCavkw== Date: Tue, 14 Feb 2023 13:50:41 -0800 From: Saeed Mahameed To: Jakub Kicinski Cc: Mark Bloch , "David S. Miller" , Paolo Abeni , Eric Dumazet , Saeed Mahameed , netdev@vger.kernel.org, Tariq Toukan , Roi Dayan , Maor Dickman Subject: Re: [net-next 01/15] net/mlx5: Lag, Let user configure multiport eswitch Message-ID: References: <20230210221821.271571-1-saeed@kernel.org> <20230210221821.271571-2-saeed@kernel.org> <20230210200329.604e485e@kernel.org> <20230213180246.06ae4acd@kernel.org> <20230214124055.6e9df4dd@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20230214124055.6e9df4dd@kernel.org> Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org 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.