public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian <balexander-osxm6dDZNBBZx8iatJs59jGjJy/sRE9J@public.gmane.org>
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Problem Pinning Physical Memory
Date: Mon, 22 Nov 2010 18:28:47 +0000 (UTC)	[thread overview]
Message-ID: <loom.20101122T192618-795@post.gmane.org> (raw)

ibv_reg_mr works fine as long as the shared region is in RAM. However, if I
change the memory region to the physical memory on a PCI device the call to
ibv_reg_mr fails. What should I be doing to register a physical memory region?

In searching through this forum I've seen some patches relating to
reg_io_mr/dereg_io_mr. However, I don't see those changes in the 1.5.2 ofed
sources. I had hoped to try applying the patches myself but the structure of the
unchanged code in the patches appears to be different than the 1.5.2 ofed
sources. Is there another, more recent, code base that I should be using?

Thank you in advance for your time and help! 

-Brian

PS. My apologies if this appears posted twice. I waited a couple of hours for
the original to post and it didn't - despite seeing later posts appear. 

--
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-11-22 18:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-22 18:28 Brian [this message]
     [not found] ` <loom.20101122T192618-795-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2010-11-24 13:55   ` Problem Pinning Physical Memory 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
     [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.20101122T192618-795@post.gmane.org \
    --to=balexander-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