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
| ||
|
Date: Sun, 10 Jun 2018 03:43:05 -0700 From: Matthew Wilcox <willy@...radead.org> To: Leon Romanovsky <leon@...nel.org> Cc: hans.westgaard.ry@...cle.com, Doug Ledford <dledford@...hat.com>, Jason Gunthorpe <jgg@...lanox.com>, Matthew Wilcox <mawilcox@...rosoft.com>, linux-rdma@...r.kernel.org, HÃ¥kon Bugge <haakon.bugge@...cle.com>, Parav Pandit <parav@...lanox.com>, Jack Morgenstein <jackm@....mellanox.co.il>, Pravin Shedge <pravin.shedge4linux@...il.com>, linux-kernel@...r.kernel.org Subject: Re: [PATCH 2/2] IB/mad: Use IDR for agent IDs On Sun, Jun 10, 2018 at 09:30:28AM +0300, Leon Romanovsky wrote: > 1. IBTA spec doesn't talk at all about the size of TransactionID, more > on that in section "13.4.6.4 TRANSACTION ID USAGE", the specification > says: "The contents of the TransactionID (TID) field are implementation- > dependent. So let's don't call it mlx4 bug. I was loosely paraphrasing the original bug report; suggested rewording of the comments gratefully accepted. > 2. The current implementation means that in mlx5-only network we will > still have upto (1 << 24) TIDs. I don't know if it is really important, > but worth to mention. Actually, the TIDs will be up to 2^56. We're limited to 2^24 clients, each of which can send up to 2^32 messages.
Powered by blists - more mailing lists