public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Netes <alexne-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Hal Rosenstock <hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 1/2] opensm/osm_state_mgr.c: Don't rely on PortInfo:PortState for base SP0
Date: Thu, 21 Apr 2011 15:22:43 +0300	[thread overview]
Message-ID: <20110421122243.GA2137@calypso.voltaire.com> (raw)
In-Reply-To: <4DAEF103.1000706-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>

On 10:43 Wed 20 Apr     , Hal Rosenstock wrote:
> Hi Alex,
> 
> On 4/20/2011 10:17 AM, Alex Netes wrote:
> > Hi Hal,
> > 
> > On 09:29 Mon 18 Apr     , Hal Rosenstock wrote:
> >>
> >> For base SP0, PortState in SM PortInfo attribute is not used and base SP0
> >> is always "active". 
> > 
> > How SM can be attached to base SP0?
> 
> What precludes this ? AFAIK SM can run on any switch port 0 whether
> enhanced or base.
> 

I'm probably missing something. Base Switch Port 0 - A Switch Port 0 which is
not an Endport (IBTA p71). 
If you look further, Endport defined as a Port which can be a destination of 
LID-routed communication within the same Subnet as the sender.

How can SM be attached to a port which isn't an Endport?

-- Alex
--
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:[~2011-04-21 12:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-18 13:29 [PATCH 1/2] opensm/osm_state_mgr.c: Don't rely on PortInfo:PortState for base SP0 Hal Rosenstock
     [not found] ` <4DAC3CCC.4090101-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2011-04-20 14:17   ` Alex Netes
     [not found]     ` <20110420141713.GD28761-iQai9MGU/dyyaiaB+Ve85laTQe2KTcn/@public.gmane.org>
2011-04-20 14:43       ` Hal Rosenstock
     [not found]         ` <4DAEF103.1000706-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2011-04-21 12:22           ` Alex Netes [this message]
     [not found]             ` <20110421122243.GA2137-iQai9MGU/dyyaiaB+Ve85laTQe2KTcn/@public.gmane.org>
2011-04-21 12:48               ` Hal Rosenstock
2011-04-27 16:09   ` Alex Netes

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=20110421122243.GA2137@calypso.voltaire.com \
    --to=alexne-vpraknaxozvwk0htik3j/w@public.gmane.org \
    --cc=hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@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