public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Oded Gabbay <ogabbay@kernel.org>
Cc: linux-rdma <linux-rdma@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: Creating new RDMA driver for habanalabs
Date: Fri, 8 Jul 2022 10:29:16 -0300	[thread overview]
Message-ID: <20220708132916.GA4459@ziepe.ca> (raw)
In-Reply-To: <CAFCwf10rGdOx94bOOW8vfuW73H_KFKPu2tg2Hpduzd+1OjnVOw@mail.gmail.com>

On Thu, Jul 07, 2022 at 12:30:03PM +0300, Oded Gabbay wrote:
> > >    These limitations are not relevant to a deployment where all the NICs are
> > >    Gaudi NICs, because we can use a single rkey for all MRs.
> >
> > Er, that is weird, did you mean to say you have only one MR per PD and
> > that it always has a fixed value?

> Not exactly. We have multiple MRs per PD, but the driver assigns the
> same rkey (fixed value) for all created MRs. Our h/w matches the rkey
> with the one that is written in the QP. The rkey is not part of the actual
> MMU translation that is done inside our h/w. The MMU translation is
> done using the PD (we call it ASID - address space ID) and Address.

I don't understand this at all - how can you have multiple MRs if
there is only one ASID per PD? The MR is logically the ASID since the
MR is the verbs model for MMU translation.

So, if you have one ASID per PD and multiple MRs, what are the MRs
supposed to be?

Jason

  reply	other threads:[~2022-07-08 13:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-22  9:40 Creating new RDMA driver for habanalabs Oded Gabbay
2021-08-22 11:32 ` Leon Romanovsky
2021-08-22 22:31 ` Jason Gunthorpe
2021-08-23  8:53   ` Oded Gabbay
2021-08-23 13:04     ` Jason Gunthorpe
2021-08-23 14:19       ` Oded Gabbay
2022-07-06  8:59         ` Oded Gabbay
2022-07-06 16:24           ` Jason Gunthorpe
2022-07-07  9:30             ` Oded Gabbay
2022-07-08 13:29               ` Jason Gunthorpe [this message]
2022-07-10  7:30                 ` Oded Gabbay
2022-07-21 18:42                   ` Jason Gunthorpe

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=20220708132916.GA4459@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=ogabbay@kernel.org \
    /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