From: Arthur Kepner <akepner-sJ/iWh9BUns@public.gmane.org>
To: Sasha Khapyorsky <sashak-smomgflXvOZWk0Htik3J/w@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Dale.R.Talcott-NSQ8wuThN14@public.gmane.org
Subject: Re: [PATCH/RFC] opensm: toggle sweeping V2
Date: Mon, 24 May 2010 14:18:30 -0700 [thread overview]
Message-ID: <20100524211830.GJ2678@sgi.com> (raw)
In-Reply-To: <20100522170431.GU28549@me>
On Sat, May 22, 2010 at 08:04:31PM +0300, Sasha Khapyorsky wrote:
> .....
> I still not understand what is wrong with running OpenSM with sweep
> disabled and restarting when a fabric is ready. But anyway a new
> console command looks less aggressive for me than signaling... :)
I think that they found that restarting opensm disrupted running jobs
much more than just pausing/resuming normal sweeping. By pausing/resuming,
they were able to grow the cluster without interrupting the jobs which
were running on the old portion of the cluster.
> .....
> The questions about patch is below.
>
> > .....
> > /* do a sweep if we received a trap */
> > if (sm->p_subn->opt.sweep_on_trap) {
>
> > - /* if this is trap number 128 or run_heavy_sweep is TRUE -
> > - update the force_heavy_sweep flag of the subnet.
> > - Sweep also on traps 144 - these traps signal a change of
> > - certain port capabilities.
> > - TODO: In the future this can be changed to just getting
> > - PortInfo on this port instead of sweeping the entire subnet. */
> > - if (ib_notice_is_generic(p_ntci) &&
> > - (cl_ntoh16(p_ntci->g_or_v.generic.trap_num) == 128 ||
> > - cl_ntoh16(p_ntci->g_or_v.generic.trap_num) == 144 ||
> > - run_heavy_sweep)) {
> > - OSM_LOG(sm->p_log, OSM_LOG_VERBOSE,
> > - "Forcing heavy sweep. Received trap:%u\n",
> > + if (!sm->p_subn->sweeping_enabled) {
> > + OSM_LOG(sm->p_log, OSM_LOG_DEBUG,
> > + "sweeping disabled - ignoring trap %u\n",
> > cl_ntoh16(p_ntci->g_or_v.generic.trap_num));
>
> Isn't this case already handled in osm_state_mgr_process() and this code
> addition in osm_trap_rcv.c redundant?
It is redundant. The only reason for it is to log the additional message
about the ignored trap, instead of the less specific "sweeping disabled -
ignoring signal ...." message.
--
Arthur
--
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:[~2010-05-24 21:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 23:57 [PATCH/RFC] opensm: toggle sweeping V2 Arthur Kepner
[not found] ` <20100519235727.GP7678-sJ/iWh9BUns@public.gmane.org>
2010-05-22 17:04 ` Sasha Khapyorsky
2010-05-24 21:18 ` Arthur Kepner [this message]
[not found] ` <20100524211830.GJ2678-sJ/iWh9BUns@public.gmane.org>
2010-05-25 15:14 ` Sasha Khapyorsky
2010-05-25 16:50 ` Arthur Kepner
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=20100524211830.GJ2678@sgi.com \
--to=akepner-sj/iwh9buns@public.gmane.org \
--cc=Dale.R.Talcott-NSQ8wuThN14@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sashak-smomgflXvOZWk0Htik3J/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.