From: Shoaib Rao <rao.shoaib@oracle.com>
To: Jason Gunthorpe <jgg@ziepe.ca>, Bob Pearson <rpearsonhpe@gmail.com>
Cc: linux-rdma@vger.kernel.org, Zhu Yanjun <zyjzyj2000@gmail.com>
Subject: Re: [PATCH v1 3/3] RDMA/rxe: Increase value of RXE_MAX_AH
Date: Mon, 21 Jun 2021 09:42:46 -0700 [thread overview]
Message-ID: <6817f1cc-d620-5908-944e-1fd61b3af61d@oracle.com> (raw)
In-Reply-To: <20210618232535.GB1096940@ziepe.ca>
On 6/18/21 4:25 PM, Jason Gunthorpe wrote:
> On Fri, Jun 18, 2021 at 01:58:48PM -0500, Bob Pearson wrote:
>> On 6/18/21 11:33 AM, Jason Gunthorpe wrote:
>>> On Thu, Jun 17, 2021 at 10:56:58PM -0500, Bob Pearson wrote:
>>>
>>>> It isn't my call. But I am in favor of tunable parameters. -- Bob Pearson
>>> Can we just delete the concept completely?
>>>
>>> Jason
>>>
>> Not sure where you are headed here. Do you mean just lift the limits
>> all together?
> Yes.. The spec doesn't have like a UCONTEXT limit for instance, and
> real HW like mlx5 has huge reported limits anyhow.
>
> Jason
So do you want me to submit a patch that removes all limits or just
these limits or something else?
Shoaib
next prev parent reply other threads:[~2021-06-21 16:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 18:25 [PATCH v1 1/3] RDMA/rxe: Increase value of RXE_MAX_UCONTEXT Rao Shoaib
2021-06-17 18:25 ` [PATCH v1 2/3] RDMA/rxe: Increase value of RXE_MAX_SRQ Rao Shoaib
2021-06-22 18:35 ` Jason Gunthorpe
2021-06-24 21:18 ` Shoaib Rao
2021-06-17 18:25 ` [PATCH v1 3/3] RDMA/rxe: Increase value of RXE_MAX_AH Rao Shoaib
2021-06-17 20:45 ` Bob Pearson
2021-06-17 22:57 ` Shoaib Rao
2021-06-18 3:56 ` Bob Pearson
2021-06-18 16:33 ` Jason Gunthorpe
2021-06-18 18:58 ` Bob Pearson
2021-06-18 23:25 ` Jason Gunthorpe
2021-06-21 16:42 ` Shoaib Rao [this message]
2021-06-24 21:21 ` Shoaib Rao
2021-06-25 5:13 ` Bob Pearson
2021-06-25 12:49 ` Jason Gunthorpe
2021-06-25 19:10 ` Shoaib Rao
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=6817f1cc-d620-5908-944e-1fd61b3af61d@oracle.com \
--to=rao.shoaib@oracle.com \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--cc=rpearsonhpe@gmail.com \
--cc=zyjzyj2000@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.