From: Leon Romanovsky <leon@kernel.org>
To: Oded Gabbay <ogabbay@kernel.org>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
linux-rdma <linux-rdma@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: Creating new RDMA driver for habanalabs
Date: Sun, 22 Aug 2021 14:32:03 +0300 [thread overview]
Message-ID: <YSI1s7JEXRaI2zdO@unreal> (raw)
In-Reply-To: <CAFCwf12o_Hq8Ci4o1H9xvqDJT9DeVmXUc7d21EqZz1meNdU3qg@mail.gmail.com>
On Sun, Aug 22, 2021 at 12:40:26PM +0300, Oded Gabbay wrote:
> Hi Jason,
>
> I think that about a year ago we talked about the custom RDMA code of
> habanalabs. I tried to upstream it and you, rightfully, rejected that.
>
> Now that I have enough b/w to do this work, I want to start writing a
> proper RDMA driver for the habanalabs Gaudi device, which I will be
> able to upstream to the infiniband subsystem.
>
> I don't know if you remember but the Gaudi h/w is somewhat limited in
> its RDMA capabilities. We are not selling a stand-alone NIC :) We just
> use RDMA (or more precisely, ROCEv2) to connect between Gaudi devices.
>
> I'm sure I will have more specific questions down the line, but I had
> hoped you could point me to a basic/not-too-complex existing driver
> that I can use as a modern template. I'm also aware that I will need
> to write matching code in rdma-core.
drivers/infiniband/hw/efa can be seen as a good example.
>
> Also, I would like to add we will use the auxiliary bus feature to
> connect between this driver, the main (compute) driver and the
> Ethernet driver (which we are going to publish soon I hope).
>
> Thanks,
> Oded
next prev parent reply other threads:[~2021-08-22 11:32 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 [this message]
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
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=YSI1s7JEXRaI2zdO@unreal \
--to=leon@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jgg@ziepe.ca \
--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 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.