linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Leon Romanovsky <leon@kernel.org>
Cc: hans.westgaard.ry@oracle.com,
	"Doug Ledford" <dledford@redhat.com>,
	"Jason Gunthorpe" <jgg@mellanox.com>,
	"Matthew Wilcox" <mawilcox@microsoft.com>,
	linux-rdma@vger.kernel.org,
	"Håkon Bugge" <haakon.bugge@oracle.com>,
	"Parav Pandit" <parav@mellanox.com>,
	"Jack Morgenstein" <jackm@dev.mellanox.co.il>,
	"Pravin Shedge" <pravin.shedge4linux@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] IB/mad: Use IDR for agent IDs
Date: Sun, 10 Jun 2018 03:43:05 -0700	[thread overview]
Message-ID: <20180610104305.GA9284@bombadil.infradead.org> (raw)
In-Reply-To: <20180610063028.GH12407@mtr-leonro.mtl.com>

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.

  reply	other threads:[~2018-06-10 10:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-08 17:42 [PATCH 0/2] Convert IB/mad to use an IDR for agent IDs Matthew Wilcox
2018-06-08 17:42 ` [PATCH 1/2] IB/mad: Agent registration is process context only Matthew Wilcox
2018-06-12 20:38   ` Jason Gunthorpe
2018-06-08 17:42 ` [PATCH 2/2] IB/mad: Use IDR for agent IDs Matthew Wilcox
2018-06-10  6:30   ` Leon Romanovsky
2018-06-10 10:43     ` Matthew Wilcox [this message]
2018-06-10 12:25       ` Leon Romanovsky
2018-06-10 20:30         ` Jason Gunthorpe
2018-06-11  4:34           ` Leon Romanovsky
2018-06-11  4:42             ` Jason Gunthorpe
2018-06-11  6:19               ` jackm
2018-06-11 16:19                 ` Jason Gunthorpe
2018-06-12  4:59                   ` jackm
2018-06-12 14:33                     ` Jason Gunthorpe
2018-06-12  8:50   ` jackm
2018-06-12 12:12     ` Matthew Wilcox
2018-06-12 20:33   ` Jason Gunthorpe
2018-06-13  0:07     ` Matthew Wilcox
2018-06-13  7:36       ` Leon Romanovsky
2018-06-13  7:56   ` jackm

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180610104305.GA9284@bombadil.infradead.org \
    --to=willy@infradead.org \
    --cc=dledford@redhat.com \
    --cc=haakon.bugge@oracle.com \
    --cc=hans.westgaard.ry@oracle.com \
    --cc=jackm@dev.mellanox.co.il \
    --cc=jgg@mellanox.com \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mawilcox@microsoft.com \
    --cc=parav@mellanox.com \
    --cc=pravin.shedge4linux@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).