From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: "Nicholas A. Bellinger" <nab-IzHhD5pYlfBP7FQvKIMDCQ@public.gmane.org>
Cc: Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org>,
linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Roland Dreier <roland-BHEL68pLQRGGvPXPguhicg@public.gmane.org>,
Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>,
Vu Pham <vu-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
David Dillow <dillowda-1Heg1YXhbW8@public.gmane.org>
Subject: Re: [PATCH] ib_srpt: Initial SRP Target merge for v3.2-rc1
Date: Wed, 19 Oct 2011 13:47:48 -0600 [thread overview]
Message-ID: <20111019194748.GA12501@obsidianresearch.com> (raw)
In-Reply-To: <1319051341.18132.53.camel-Y1+j5t8j3WgjMeEPmliV8E/sVC8ogwMJ@public.gmane.org>
On Wed, Oct 19, 2011 at 12:09:01PM -0700, Nicholas A. Bellinger wrote:
> Are sport->gid.global.interface_id going to be different for each struct
> srpt_port..?
Infiniband GID suffixes (interface_id) are not guaranteed to be
unique. The GID is expected to be unique, the portGUID (which is
sometimes the same as the interface_id) is also expected to be unique.
Jason
--
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:[~2011-10-19 19:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 1:48 [PATCH] ib_srpt: Initial SRP Target merge for v3.2-rc1 Nicholas A. Bellinger
[not found] ` <1318556901-14850-1-git-send-email-nab-IzHhD5pYlfBP7FQvKIMDCQ@public.gmane.org>
2011-10-19 17:56 ` Bart Van Assche
[not found] ` <CAO+b5-orW-iK6WiGAt8Ovd1g64e628tcOh13D5xA67SfJ-W-Vg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-10-19 18:35 ` Nicholas A. Bellinger
[not found] ` <1319049335.18132.34.camel-Y1+j5t8j3WgjMeEPmliV8E/sVC8ogwMJ@public.gmane.org>
2011-10-19 18:47 ` Bart Van Assche
[not found] ` <CAO+b5-oJ38L7t=spKQPnEZxNOA6zoqG9DA3uw9q+eOTVvELRUA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-10-19 19:09 ` Nicholas A. Bellinger
[not found] ` <1319051341.18132.53.camel-Y1+j5t8j3WgjMeEPmliV8E/sVC8ogwMJ@public.gmane.org>
2011-10-19 19:47 ` Jason Gunthorpe [this message]
[not found] ` <20111019194748.GA12501-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2011-10-20 6:22 ` Bart Van Assche
2011-10-20 6:24 ` Bart Van Assche
[not found] ` <CAO+b5-quJkZdSsAmL1gZz1V6mwB3Q8abOu_Q+96MxO89bhg6EA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-10-20 16:47 ` Roland Dreier
2011-10-20 16:49 ` Roland Dreier
2011-11-11 11:41 ` Bart Van Assche
[not found] ` <CAO+b5-oX94=81Gdr2cs0VFoF8Yb+B1DAT2Z+h2UeP6q111Rv7g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-11-12 21:31 ` Nicholas A. Bellinger
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=20111019194748.GA12501@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=bvanassche-HInyCGIudOg@public.gmane.org \
--cc=dillowda-1Heg1YXhbW8@public.gmane.org \
--cc=hch-jcswGhMUV9g@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=nab-IzHhD5pYlfBP7FQvKIMDCQ@public.gmane.org \
--cc=roland-BHEL68pLQRGGvPXPguhicg@public.gmane.org \
--cc=vu-VPRAkNaXOzVWk0Htik3J/w@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