public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: lihaidong <lihaidong-6gUaA8visnnQT0dZR+AlfA@public.gmane.org>
Cc: linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Problems using krping
Date: Thu, 21 Jan 2010 08:40:33 -0600	[thread overview]
Message-ID: <4B586761.8040005@opengridcomputing.com> (raw)
In-Reply-To: <201001211807011710722-6gUaA8visnnQT0dZR+AlfA@public.gmane.org>

It appears the MLX4 driver does not support kernel mode memory regions.  
You'll have to use dma mrs or fast_reg mrs with that device.

Steve.




lihaidong wrote:
> Mr.Wise:
>  
> When using mr mode as the memory registration method, krping failed to 
> get memory region using ib_reg_phys_mr().Could you help me, please?
>  
> dmesg:
> krping_init
> krping: proc write |client,addr=10.10.10.15,mem_mode=mr,port=9999,count=1,verbose|
> client
> ipaddr (10.10.10.15)
> port 9999
> count 1
> verbose
> created cm_id ffff88013c74c800
> cma_event type 0 cma_id ffff88013c74c800 (parent)
> cma_event type 2 cma_id ffff88013c74c800 (parent)
> rdma_resolve_addr - rdma_resolve_route successful
> created pd ffff880133845280
> created cq ffff88013c1ff400
> created qp ffff88013c1ffe00
> krping: krping_setup_buffers called on cb ffff88013c59f800
> krping: recv buf dma_addr 13c59f968 size 16
> krping: recv_buf reg_mr failed
> krping: krping_setup_buffers failed: -38
> destroy cm_id ffff88013c74c800
> krping: proc write |client,addr=10.10.10.15,mem_mode=mr,port=9999,count=1,verbose|
> client
> ipaddr (10.10.10.15)
> port 9999
> count 1
> verbose
> created cm_id ffff88013c59f800
> cma_event type 0 cma_id ffff88013c59f800 (parent)
> cma_event type 2 cma_id ffff88013c59f800 (parent)
> rdma_resolve_addr - rdma_resolve_route successful
> created pd ffff88012f5964a0
> created cq ffff88012faee400
> created qp ffff88012faeec00
> krping: krping_setup_buffers called on cb ffff88013c71d400
> krping: recv buf dma_addr 13c71d568 size 16
> krping: recv_buf reg_mr failed
> krping: krping_setup_buffers failed: -38
> destroy cm_id ffff88013c59f800
>  
>  
> echo "client,addr=10.10.10.15,mem_mode=mr,port=9999,count=1" > /proc/krping 
>
> echo "server,addr=10.10.10.15,mem_mode=mr,port=9999" > /proc/krping
>  
> Using OFED-1.5 ofa_kernel-1.5
> HardWare:Mellanox Technologies MT26428 [ConnectX VPI PCIe 2.0 5GT/s - IB QDR / 10GigE] 
>
> put krping source files into drivers/infiniband/hw/mlx4
>  
> 2010-01-21
> ------------------------------------------------------------------------
> lihaidong

--
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-01-21 14:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201001211807011710722@inspur.com>
     [not found] ` <201001211807011710722-6gUaA8visnnQT0dZR+AlfA@public.gmane.org>
2010-01-21 14:40   ` Steve Wise [this message]
     [not found] ` <201001221533186875550@inspur.com>
     [not found]   ` <201001221533186875550-6gUaA8visnnQT0dZR+AlfA@public.gmane.org>
2010-01-22 15:16     ` Problems using krping Steve Wise
     [not found]   ` <201001242242553436345@inspur.com>
     [not found]     ` <201001242242553436345-6gUaA8visnnQT0dZR+AlfA@public.gmane.org>
2010-01-24 21:44       ` Steve Wise
     [not found]     ` <201001251036131874884@inspur.com>
     [not found]       ` <201001251036131874884-6gUaA8visnnQT0dZR+AlfA@public.gmane.org>
2010-01-25  3:28         ` Steve Wise
     [not found]       ` <201001261339589687690@inspur.com>
     [not found]         ` <201001261339589687690-6gUaA8visnnQT0dZR+AlfA@public.gmane.org>
2010-01-26 15:01           ` Steve Wise
     [not found]       ` <201001262046537030587@inspur.com>
     [not found]         ` <201001262046537030587-6gUaA8visnnQT0dZR+AlfA@public.gmane.org>
2010-01-26 15:02           ` Steve Wise

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=4B586761.8040005@opengridcomputing.com \
    --to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
    --cc=lihaidong-6gUaA8visnnQT0dZR+AlfA@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