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
| ||
|
Message-ID: <b21d51b2-5480-4550-7cd6-c16060261970@linux.alibaba.com> Date: Sat, 22 Jan 2022 00:36:21 +0800 From: Guangguan Wang <guangguan.wang@...ux.alibaba.com> To: Karsten Graul <kgraul@...ux.ibm.com>, davem@...emloft.net, kuba@...nel.org Cc: linux-s390@...r.kernel.org, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [RFC PATCH net-next] net/smc: Introduce receive queue flow control support 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.
Powered by blists - more mailing lists