public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Hal Rosenstock <hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Alex Netes <alexne-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: hal-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 2/5] opensm: change discovery order of switch data
Date: Mon, 03 Feb 2014 14:42:36 -0500	[thread overview]
Message-ID: <52EFF12C.8020502@dev.mellanox.co.il> (raw)
In-Reply-To: <1391425516-14462-2-git-send-email-alexne-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>

On 2/3/2014 6:05 AM, Alex Netes wrote:
> Previously upon receiving GetResp(NodeInfo) of a switch, SM sent
> Get(SwitchInfo) and Get(PortInfo) to all its' ports in parallel. Upon receiving
> GetResp(PortInfo) SM sends Get(PkeyTable). The problem is that we need
> SwitchInfo.PartEnforceCap value to calculate max Pkeys block, so in case
> one of the GetResp(PortInfo) arrives prior to GetResp(SwitchInfo) this
> value won't be set.
> The fix to change the discover order. Upon receiving GetResP(NodeInfo),
> SM sends Get(SwitchInfo). Upon receiving GetResp(SwitchInfo), SM sends
> Get(PortInfo port0). If we don't get GetResp(PortInfo port=0), SM will
> drop the switch, otherwise SM sends Get(PortInfo ExtPorts).
> Moreover, now SM queries for ExtPortInfo and Pkeys only for non-Down
> ports.
> 
> Signed-off-by: Alex Netes <alexne-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>

Thanks. Applied.

-- 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:[~2014-02-03 19:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-03 11:05 [PATCH 1/5] opensm/include/iba/ib_types.h: Fix shadow declaration warnings Alex Netes
     [not found] ` <1391425516-14462-1-git-send-email-alexne-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2014-02-03 11:05   ` [PATCH 2/5] opensm: change discovery order of switch data Alex Netes
     [not found]     ` <1391425516-14462-2-git-send-email-alexne-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2014-02-03 19:42       ` Hal Rosenstock [this message]
2014-02-03 11:05   ` [PATCH 3/5] opensm: Better handle topology changes in the fabric Alex Netes
     [not found]     ` <1391425516-14462-3-git-send-email-alexne-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2014-02-03 19:42       ` Hal Rosenstock
2014-02-03 11:05   ` [PATCH 4/5] opensm/osm_port_info_rcv.c: Reread pkeys from SP0 if switch rebooted during a sweep Alex Netes
     [not found]     ` <1391425516-14462-4-git-send-email-alexne-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2014-02-03 19:42       ` Hal Rosenstock
2014-02-03 11:05   ` [PATCH 5/5] opensm: Resend LFTs/VLArb/SL2VL MADs in case of error Alex Netes
     [not found]     ` <1391425516-14462-5-git-send-email-alexne-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2014-02-03 19:43       ` Hal Rosenstock
2014-02-04  5:54       ` Jens Domke
2014-02-03 19:42   ` [PATCH 1/5] opensm/include/iba/ib_types.h: Fix shadow declaration warnings Hal Rosenstock

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=52EFF12C.8020502@dev.mellanox.co.il \
    --to=hal-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
    --cc=alexne-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=hal-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