public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Hal Rosenstock <hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: "Coulter, Susan K" <skc-YOWKrPYUwWM@public.gmane.org>
Cc: "linux-rdma
	(linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org)"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: partitions / ib_read_bw
Date: Sat, 22 Jun 2013 07:56:13 -0400	[thread overview]
Message-ID: <51C590DD.3000704@dev.mellanox.co.il> (raw)
In-Reply-To: <AB9234BD-66C3-4D8E-93CA-5AF8D26818AB-YOWKrPYUwWM@public.gmane.org>

On 6/21/2013 5:48 PM, Coulter, Susan K wrote:
> 
> One of my test clusters is running with multiple partitions.
> The partitions look correct (using "smpquery pkey") and the path records look correct (using "saquery pr").
> 
> I'd like a simple user-level test to validate who is allowed to talk to who; and hoped to use ib_read_bw.
> Alas, ib_read_bw does not honor partitions.
> 
> Below is a patch I wrote to try and add pkey support to ib_read_bw.  No joy.
> 
> The server shows it is populating ibv_qp_attr with the pkey(s) of any full partition it is a member of, 
> but the client does not get that same pkey in ibv_wc.
> 
> What am I missing?

The QPs need to be bound to the proper pkey index. An additional command
line pkey parameter is needed on client and maybe also server side.
Server side pkey parameter could be avoided if QPs are initialized for
all pkeys configured.

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

      parent reply	other threads:[~2013-06-22 11:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-21 21:48 partitions / ib_read_bw Coulter, Susan K
     [not found] ` <AB9234BD-66C3-4D8E-93CA-5AF8D26818AB-YOWKrPYUwWM@public.gmane.org>
2013-06-21 23:18   ` Jason Gunthorpe
2013-06-22 11:56   ` Hal Rosenstock [this message]

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=51C590DD.3000704@dev.mellanox.co.il \
    --to=hal-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=skc-YOWKrPYUwWM@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