From: Jason Gunthorpe <jgg@ziepe.ca>
To: Jianxin Xiong <jianxin.xiong@intel.com>
Cc: linux-rdma@vger.kernel.org, dri-devel@lists.freedesktop.org,
Doug Ledford <dledford@redhat.com>,
Leon Romanovsky <leon@kernel.org>,
Sumit Semwal <sumit.semwal@linaro.org>,
Christian Koenig <christian.koenig@amd.com>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH rdma-core 3/5] pyverbs: Add dma-buf based MR support
Date: Mon, 23 Nov 2020 14:05:04 -0400 [thread overview]
Message-ID: <20201123180504.GA244516@ziepe.ca> (raw)
In-Reply-To: <1606153984-104583-4-git-send-email-jianxin.xiong@intel.com>
On Mon, Nov 23, 2020 at 09:53:02AM -0800, Jianxin Xiong wrote:
> +cdef class DmaBuf:
> + def __init__(self, size, unit=0):
> + """
> + Allocate DmaBuf object from a GPU device. This is done through the
> + DRI device interface (/dev/dri/card*). Usually this requires the
> + effective user id being root or being a member of the 'video' group.
> + :param size: The size (in number of bytes) of the buffer.
> + :param unit: The unit number of the GPU to allocate the buffer from.
> + :return: The newly created DmaBuf object on success.
> + """
> + self.dmabuf_mrs = weakref.WeakSet()
> + self.dri_fd = open('/dev/dri/card'+str(unit), O_RDWR)
> +
> + args = bytearray(32)
> + pack_into('=iiiiiiq', args, 0, 1, size, 8, 0, 0, 0, 0)
> + ioctl(self.dri_fd, DRM_IOCTL_MODE_CREATE_DUMB, args)
> + a, b, c, d, self.handle, e, self.size = unpack('=iiiiiiq', args)
> +
> + args = bytearray(12)
> + pack_into('=iii', args, 0, self.handle, O_RDWR, 0)
> + ioctl(self.dri_fd, DRM_IOCTL_PRIME_HANDLE_TO_FD, args)
> + a, b, self.fd = unpack('=iii', args)
> +
> + args = bytearray(16)
> + pack_into('=iiq', args, 0, self.handle, 0, 0)
> + ioctl(self.dri_fd, DRM_IOCTL_MODE_MAP_DUMB, args);
> + a, b, self.map_offset = unpack('=iiq', args);
Wow, OK
Is it worth using ctypes here instead? Can you at least add a comment
before each pack specifying the 'struct XXX' this is following?
Does this work with normal Intel GPUs, like in a Laptop? AMD too?
Christian, I would be very happy to hear from you that this entire
work is good for AMD as well
Edward should look through this, but I'm glad to see something like
this
Thanks,
Jason
next prev parent reply other threads:[~2020-11-23 18:05 UTC|newest]
Thread overview: 24+ 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:53 ` [PATCH rdma-core 1/5] verbs: Support dma-buf based memory region Jianxin Xiong
2020-11-23 18:01 ` Jason Gunthorpe
2020-11-24 10:31 ` Yishai Hadas
2020-11-24 18:00 ` Xiong, Jianxin
2020-11-23 17:53 ` [PATCH rdma-core 2/5] mlx5: " Jianxin Xiong
2020-11-23 18:01 ` Jason Gunthorpe
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 18:05 ` Jason Gunthorpe [this message]
2020-11-23 19:48 ` Xiong, Jianxin
2020-11-24 15:16 ` Daniel Vetter
2020-11-24 15:36 ` Jason Gunthorpe
2020-11-24 16:21 ` Xiong, Jianxin
2020-11-24 18:45 ` Xiong, Jianxin
2020-11-25 10:50 ` Daniel Vetter
2020-11-25 12:14 ` Jason Gunthorpe
2020-11-25 19:27 ` Xiong, Jianxin
2020-11-26 0:00 ` Jason Gunthorpe
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 ` [PATCH rdma-core 5/5] tests: Bug fix for get_access_flags() Jianxin Xiong
2020-11-24 20:26 ` John Hubbard
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=20201123180504.GA244516@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@intel.com \
--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 \
--cc=sumit.semwal@linaro.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