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
Subject: Re: [PATCH 1/1] Initiate heavy sweep in MFTSubnSet fails during idle time process
Date: Sun, 15 May 2011 10:14:08 +0300 [thread overview]
Message-ID: <20110515071408.GA30064@calypso.voltaire.com> (raw)
In-Reply-To: <4DCE950C.60303-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
Hi Hal,
On 10:43 Sat 14 May , Hal Rosenstock wrote:
> Hi Alex,
>
> On 5/12/2011 12:14 PM, Alex Netes wrote:
> > MFTSubnSet failed MADs may leave temporary MC loops in the fabric.
> > In order to eliminate this faulty state as quick as possible it's a good
> > thing to initiate a heavy sweep immediately and to wait for the next light
> > sweep.
> >
> > Signed-off-by: Alex Netes <alexne-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
> > ---
> > opensm/osm_state_mgr.c | 7 +++++++
> > 1 files changed, 7 insertions(+), 0 deletions(-)
> >
> > diff --git a/opensm/osm_state_mgr.c b/opensm/osm_state_mgr.c
> > index dd308f2..aa71b03 100644
> > --- a/opensm/osm_state_mgr.c
> > +++ b/opensm/osm_state_mgr.c
> > @@ -1434,6 +1434,13 @@ static void do_process_mgrp_queue(osm_sm_t * sm)
> > osm_mcast_mgr_process(sm);
> > wait_for_pending_transactions(&sm->p_subn->p_osm->stats);
> > }
> > +
> > + /* if one or more MFTSubnSet MADs fails
> > + * during idle process time initiate heavy sweep */
> > + if (sm->p_subn->force_heavy_sweep
> > + || sm->p_subn->subnet_initialization_error)
> > + osm_sm_signal(sm, OSM_SIGNAL_SWEEP);
>
> subnet_initialization_error is more than just set MFT failures. Should
> it be narrowed down to just those failures ?
>
Do you mean, just resend the MFTs without causing heavy sweep?
> Also, while this looks like it would fix the scenario you mention,
> couldn't this change cause a continual heavy sweep ?
>
Yes. This can cause continual heavy sweep. But this would happen anyway. This
patch initiate heavy sweep immediately and without it, the heavy sweep would be
started on the next light sweep. In both cases you can end up in heavy sweep
loop.
> -- Hal
>
> > +
> > }
> >
> > void osm_state_mgr_process(IN osm_sm_t * sm, IN osm_signal_t signal)
>
> --
> 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
--
-- 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
prev parent reply other threads:[~2011-05-15 7:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 16:14 [PATCH 1/1] Initiate heavy sweep in MFTSubnSet fails during idle time process Alex Netes
[not found] ` <20110512161443.GC22389-iQai9MGU/dyyaiaB+Ve85laTQe2KTcn/@public.gmane.org>
2011-05-14 14:43 ` Hal Rosenstock
[not found] ` <4DCE950C.60303-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2011-05-15 7:14 ` Alex Netes [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=20110515071408.GA30064@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