Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp1407770pxb; Fri, 21 Jan 2022 17:58:23 -0800 (PST) X-Google-Smtp-Source: ABdhPJxnFq8ERpMOhybKkrLWdmb67et6toKzemLVZO6jszIl0iegUqFAdGlk2U4Depb673dFuOL5 X-Received: by 2002:a17:902:b696:b0:149:9e52:eda1 with SMTP id c22-20020a170902b69600b001499e52eda1mr6021761pls.174.1642816702959; Fri, 21 Jan 2022 17:58:22 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1642816702; cv=none; d=google.com; s=arc-20160816; b=t93oUI+HditnfVUG9w1vc3YedakIdmvv2WGE5EECvrRRT0XpWgFD674Q8CpK3081R/ WSmdWmg90qcbcRiHfjqFohrwuzOpCeHxTM1p7wQxuQA0SXjZ9iG9kfhPtyCYsE+wEBQT mbRDHYTMeIM1niBS0MV1oLfA5G/v/rTicwOd5/JjBXONKo9OW1pRNULdzuBRkEjeEMh9 G2mWEVCPjR+eNjnOpKgtTkCeYVx3M76bN0ZEX16VAVDce5MUNXLepfmdVhYm2hLz0s7U gHgmI+QbVlNnuSQE+EVKNSqXly8KU4xNvOdNVckpVS1PnqtCnBZEMHGdvtqOqPecJaFs 23OQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id; bh=sPenuPTGeTK424wJTXHyBIcRn6zEpZQ2eRDnU90BSdI=; b=IOXTtdN1qL4a2LiCNBcHE672OacofvD+K675dqvpf401uCN7bID6WYjYx6kUH5FS/Z YUlnPpv6OcT6PtabKQ6/Q5djVKfxIZTQlNKkkWpiNZQANJofN3cPikx0sPsO7qtioBQL +CV+pu5LKA7iaokFmyn2+k3e+574Y8bkegvr8LpvdvC34fQbXimfdvjhO/7Zpa8mCc0Z u6kuF0evRz/37eQVNoxwoG2+Y/0/qa0qgVFDHJp5V9y8TXrrL2jvJs5HOzvEpZVZsBdl fUshggCbjHgELLvlCJBlGJqY7t3C/Gg4PeUI9SzrFExttzhJzgBZF95LsunJZkH8NbCW 890A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=alibaba.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id pf11si16706188pjb.2.2022.01.21.17.58.11; Fri, 21 Jan 2022 17:58:22 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=alibaba.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1348997AbiAUQg0 (ORCPT + 99 others); Fri, 21 Jan 2022 11:36:26 -0500 Received: from out30-130.freemail.mail.aliyun.com ([115.124.30.130]:58245 "EHLO out30-130.freemail.mail.aliyun.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234718AbiAUQgY (ORCPT ); Fri, 21 Jan 2022 11:36:24 -0500 X-Alimail-AntiSpam: AC=PASS;BC=-1|-1;BR=01201311R221e4;CH=green;DM=||false|;DS=||;FP=0|-1|-1|-1|0|-1|-1|-1;HT=e01e04395;MF=guangguan.wang@linux.alibaba.com;NM=1;PH=DS;RN=6;SR=0;TI=SMTPD_---0V2SImAL_1642782981; Received: from 30.39.181.79(mailfrom:guangguan.wang@linux.alibaba.com fp:SMTPD_---0V2SImAL_1642782981) by smtp.aliyun-inc.com(127.0.0.1); Sat, 22 Jan 2022 00:36:22 +0800 Message-ID: Date: Sat, 22 Jan 2022 00:36:21 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: [RFC PATCH net-next] net/smc: Introduce receive queue flow control support Content-Language: en-US To: Karsten Graul , davem@davemloft.net, kuba@kernel.org Cc: linux-s390@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org References: <20220120065140.5385-1-guangguan.wang@linux.alibaba.com> <20da5fa9-6158-d04c-6f44-29e550ed97d0@linux.ibm.com> From: Guangguan Wang In-Reply-To: <20da5fa9-6158-d04c-6f44-29e550ed97d0@linux.ibm.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2022/1/20 19:03, Karsten Graul wrote:> > I really appreciate your effort to improve the performance and solve existing bottle necks, > but please keep in mind that the SMC module implements the IBM SMC protocol that is > described here: https://www.ibm.com/support/pages/node/6326337 > (you can find these links in the source code, too). > > Your patch makes changes that are not described in this design paper and may lead to > future incompatibilities with other platforms that support the IBM SMC protocol. > > For example: > - you start using one of the reserved bytes in struct smc_cdc_msg > - you define a new smc_llc message type 0x0A > - you change the maximum number of connections per link group from 255 to 32 > > We need to start a discussion about your (good!) ideas with the owners of the protocol. Thanks for your affirmation of my effort and looking forward to the conclusion of the protocol discussion.