From: Hal Rosenstock <hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Alex Netes <alexne-VPRAkNaXOzVWk0Htik3J/w@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: Wed, 20 Apr 2011 10:43:15 -0400 [thread overview]
Message-ID: <4DAEF103.1000706@dev.mellanox.co.il> (raw)
In-Reply-To: <20110420141713.GD28761-iQai9MGU/dyyaiaB+Ve85laTQe2KTcn/@public.gmane.org>
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.
> Moreover, if during discovery we found that SM is attached to base SP0, don't
> we want to act like the port is down?
For base SP0, PortState and PortPhysicalState are "not used" in the SM
PortInfo attribute. That means they're "vendor" specific and they should
not be relied upon to be valid.
The point of this patch is that base SP0 is always up regardless of what
PortInfo for that port says.
If SM wasn't allowed to run on base SP0, it would be a different patch:
to prohibit such a port from being used at all as the SM port so the
failure would be earlier in the code flow when the SM tries to bind to
such a port.
-- Hal
>>
>> Signed-off-by: Hal Rosenstock <hal-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
>> ---
>> diff --git a/opensm/osm_state_mgr.c b/opensm/osm_state_mgr.c
>> index 2e1ef94..dd308f2 100644
>> --- a/opensm/osm_state_mgr.c
>> +++ b/opensm/osm_state_mgr.c
>> @@ -352,7 +352,11 @@ static boolean_t state_mgr_is_sm_port_down(IN osm_sm_t * sm)
>>
>> CL_ASSERT(p_physp);
>>
>> - state = osm_physp_get_port_state(p_physp);
>> + if (p_port->p_node->sw &&
>> + !ib_switch_info_is_enhanced_port0(&p_port->p_node->sw->switch_info))
>> + state = IB_LINK_ACTIVE; /* base SP0 */
>> + else
>> + state = osm_physp_get_port_state(p_physp);
>> CL_PLOCK_RELEASE(sm->p_lock);
>>
>> Exit:
>> --
>
> -- 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
next prev parent reply other threads:[~2011-04-20 14:43 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 [this message]
[not found] ` <4DAEF103.1000706-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2011-04-21 12:22 ` Alex Netes
[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=4DAEF103.1000706@dev.mellanox.co.il \
--to=hal-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
--cc=alexne-VPRAkNaXOzVWk0Htik3J/w@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