From: Tom Tucker <tom-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
Cc: Jason Gunthorpe
<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>,
Eli Cohen <eli-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>,
Brian
<balexander-osxm6dDZNBBZx8iatJs59jGjJy/sRE9J@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Problem Pinning Physical Memory
Date: Mon, 29 Nov 2010 11:13:45 -0600 [thread overview]
Message-ID: <4CF3DF49.8000605@opengridcomputing.com> (raw)
In-Reply-To: <4CF3DE7D.4060105-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
On 11/29/10 11:10 AM, Steve Wise wrote:
>
>
> On 11/24/2010 11:42 AM, Jason Gunthorpe wrote:
>>
>> The last time this came up I said that the kernel side of ibv_reg_mr
>> should do the right thing for all types of memory that are mmap'd into
>> a process and I still think that is true. RDMA to device memory could
>> be very useful and with things like GEM managing the allocation of
>> device (video) memory to userspace, so it can be done safely.
>>
>> Jason
>
> Tom posted changes to support this a while back. Tom, do you have an
> updated patch series for this support?
>
Yes. I removed the new verb and followed Jason's recommendation of adding
this support to the core reg_mr support. I used the type bits in the vma
struct to determine the type of memory being registered and just did the
"right thing."
I'll repost in the the next day or two.
Tom
> Steve.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-11-29 17:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 18:28 Problem Pinning Physical Memory Brian
[not found] ` <loom.20101122T192618-795-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2010-11-24 13:55 ` Eli Cohen
2010-11-24 17:42 ` Jason Gunthorpe
[not found] ` <20101124174245.GA25325-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2010-11-29 17:10 ` Steve Wise
[not found] ` <4CF3DE7D.4060105-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2010-11-29 17:13 ` Tom Tucker [this message]
2010-11-30 15:24 ` Alan Cook
[not found] ` <loom.20101130T160950-109-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2010-11-30 20:26 ` Tom Tucker
2010-12-01 15:30 ` Alan Cook
[not found] ` <loom.20101201T162410-279-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2010-12-02 7:19 ` Or Gerlitz
[not found] ` <4CF7487C.3080209-smomgflXvOZWk0Htik3J/w@public.gmane.org>
2010-12-02 16:09 ` Alan Cook
2010-11-26 14:08 ` Brian
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=4CF3DF49.8000605@opengridcomputing.com \
--to=tom-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
--cc=balexander-osxm6dDZNBBZx8iatJs59jGjJy/sRE9J@public.gmane.org \
--cc=eli-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
--cc=jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.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