All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Jianxin Xiong <jianxin.xiong@intel.com>,
	Leon Romanovsky <leon@kernel.org>,
	linux-rdma@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Doug Ledford <dledford@redhat.com>,
	Daniel Vetter <daniel.vetter@intel.com>,
	Christian Koenig <christian.koenig@amd.com>
Subject: Re: [PATCH rdma-core 3/5] pyverbs: Add dma-buf based MR support
Date: Tue, 24 Nov 2020 11:36:26 -0400	[thread overview]
Message-ID: <20201124153626.GG5487@ziepe.ca> (raw)
In-Reply-To: <20201124151658.GT401619@phenom.ffwll.local>

On Tue, Nov 24, 2020 at 04:16:58PM +0100, Daniel Vetter wrote:

> Compute is the worst, because opencl is widely considered a mistake (maybe
> opencl 3 is better, but nvidia is stuck on 1.2). The actually used stuff is
> cuda (nvidia-only), rocm (amd-only) and now with intel also playing we
> have xe (intel-only).

> It's pretty glorious :-/

I enjoyed how the Intel version of CUDA is called "OneAPI" not "Third
API" ;)

Hopefuly xe compute won't leave a lot of half finished abandoned
kernel code like Xeon Phi did :(

> Also I think we discussed this already, but for actual p2p the intel
> patches aren't in upstream yet. We have some internally, but with very
> broken locking (in the process of getting fixed up, but it's taking time).

Someone needs to say this test works on a real system with an
unpatched upstream driver.

I thought AMD had the needed parts merged?

Jason

WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Leon Romanovsky <leon@kernel.org>,
	linux-rdma@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Doug Ledford <dledford@redhat.com>,
	Daniel Vetter <daniel.vetter@intel.com>,
	Christian Koenig <christian.koenig@amd.com>,
	Jianxin Xiong <jianxin.xiong@intel.com>
Subject: Re: [PATCH rdma-core 3/5] pyverbs: Add dma-buf based MR support
Date: Tue, 24 Nov 2020 11:36:26 -0400	[thread overview]
Message-ID: <20201124153626.GG5487@ziepe.ca> (raw)
In-Reply-To: <20201124151658.GT401619@phenom.ffwll.local>

On Tue, Nov 24, 2020 at 04:16:58PM +0100, Daniel Vetter wrote:

> Compute is the worst, because opencl is widely considered a mistake (maybe
> opencl 3 is better, but nvidia is stuck on 1.2). The actually used stuff is
> cuda (nvidia-only), rocm (amd-only) and now with intel also playing we
> have xe (intel-only).

> It's pretty glorious :-/

I enjoyed how the Intel version of CUDA is called "OneAPI" not "Third
API" ;)

Hopefuly xe compute won't leave a lot of half finished abandoned
kernel code like Xeon Phi did :(

> Also I think we discussed this already, but for actual p2p the intel
> patches aren't in upstream yet. We have some internally, but with very
> broken locking (in the process of getting fixed up, but it's taking time).

Someone needs to say this test works on a real system with an
unpatched upstream driver.

I thought AMD had the needed parts merged?

Jason
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2020-11-24 15:36 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-23 17:52 [PATCH rdma-core 0/5] Add user space dma-buf support Jianxin Xiong
2020-11-23 17:52 ` Jianxin Xiong
2020-11-23 17:53 ` [PATCH rdma-core 1/5] verbs: Support dma-buf based memory region Jianxin Xiong
2020-11-23 17:53   ` Jianxin Xiong
2020-11-23 18:01   ` Jason Gunthorpe
2020-11-23 18:01     ` Jason Gunthorpe
2020-11-24 10:31   ` Yishai Hadas
2020-11-24 10:31     ` Yishai Hadas
2020-11-24 18:00     ` Xiong, Jianxin
2020-11-24 18:00       ` Xiong, Jianxin
2020-11-23 17:53 ` [PATCH rdma-core 2/5] mlx5: " Jianxin Xiong
2020-11-23 17:53   ` Jianxin Xiong
2020-11-23 18:01   ` Jason Gunthorpe
2020-11-23 18:01     ` Jason Gunthorpe
2020-11-23 19:40     ` Xiong, Jianxin
2020-11-23 19:40       ` Xiong, Jianxin
2020-11-23 17:53 ` [PATCH rdma-core 3/5] pyverbs: Add dma-buf based MR support Jianxin Xiong
2020-11-23 17:53   ` Jianxin Xiong
2020-11-23 18:05   ` Jason Gunthorpe
2020-11-23 18:05     ` Jason Gunthorpe
2020-11-23 19:48     ` Xiong, Jianxin
2020-11-23 19:48       ` Xiong, Jianxin
2020-11-24 15:16     ` Daniel Vetter
2020-11-24 15:16       ` Daniel Vetter
2020-11-24 15:36       ` Jason Gunthorpe [this message]
2020-11-24 15:36         ` Jason Gunthorpe
2020-11-24 16:21         ` Xiong, Jianxin
2020-11-24 16:21           ` Xiong, Jianxin
2020-11-24 18:45       ` Xiong, Jianxin
2020-11-24 18:45         ` Xiong, Jianxin
2020-11-25 10:50         ` Daniel Vetter
2020-11-25 10:50           ` Daniel Vetter
2020-11-25 12:14           ` Jason Gunthorpe
2020-11-25 12:14             ` Jason Gunthorpe
2020-11-25 19:27             ` Xiong, Jianxin
2020-11-25 19:27               ` Xiong, Jianxin
2020-11-26  0:00               ` Jason Gunthorpe
2020-11-26  0:00                 ` Jason Gunthorpe
2020-11-26  0:43                 ` Xiong, Jianxin
2020-11-26  0:43                   ` Xiong, Jianxin
2020-11-23 17:53 ` [PATCH rdma-core 4/5] tests: Add tests for dma-buf based memory regions Jianxin Xiong
2020-11-23 17:53   ` Jianxin Xiong
2020-11-23 17:53 ` [PATCH rdma-core 5/5] tests: Bug fix for get_access_flags() Jianxin Xiong
2020-11-23 17:53   ` Jianxin Xiong
2020-11-24 20:26   ` John Hubbard
2020-11-24 20:26     ` John Hubbard
2020-11-24 20:43     ` Xiong, Jianxin
2020-11-24 20:43       ` Xiong, Jianxin

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=20201124153626.GG5487@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=christian.koenig@amd.com \
    --cc=daniel.vetter@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=dledford@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jianxin.xiong@intel.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.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.