public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cook <acook-osxm6dDZNBBZx8iatJs59jGjJy/sRE9J@public.gmane.org>
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Problem Pinning Physical Memory
Date: Wed, 1 Dec 2010 15:30:45 +0000 (UTC)	[thread overview]
Message-ID: <loom.20101201T162410-279@post.gmane.org> (raw)
In-Reply-To: 4CF55DF2.1030507@opengridcomputing.com

Tom Tucker <tom@...> writes:

> What I implemented was support for mmap'd memory. In practical terms for 
> your application you would write a driver that supported the mmap file op. 
> The driver's mmap routine would ioremap the pci memory of interest and 
> stuff it in the provided vma. The user-mode app then ibv_reg_mr the 
> address and length returned by mmap.
> 
> Make sense?

I believe so.  Something along these lines has already been implemented for the
device with which I am working, but was failing due to lacking your patch.

I am not able to find the patch that you submitted (bad search terms?).  I also
am having a difficult time tracking down (with any certainty) the sources that
your patch would be made against.

If you could provide lines to both I would greatly appreciate it.

Thanks.

-- Alan


--
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

  reply	other threads:[~2010-12-01 15:30 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
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 [this message]
     [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=loom.20101201T162410-279@post.gmane.org \
    --to=acook-osxm6ddznbbzx8iatjs59jgjjy/sre9j@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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