Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Sasha Khapyorsky <sashak-smomgflXvOZWk0Htik3J/w@public.gmane.org>
To: Hal Rosenstock <hnrose-Wuw85uim5zDR7s880joybQ@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCHv3] opensm: Better handling of non responsive SMAs
Date: Wed, 9 Jun 2010 22:37:07 +0300	[thread overview]
Message-ID: <20100609193707.GK20172@me> (raw)
In-Reply-To: <20100609182911.GA26769-Wuw85uim5zDR7s880joybQ@public.gmane.org>

On 14:29 Wed 09 Jun     , Hal Rosenstock wrote:
> 
> In order to better handle non responsive SMAs (when link is physically up
> but the SMA does not respond), a timeout based mechanism for SMPs is added
> to better enable forward progress in a more timely fashion. So rather than
> waiting for timeouts and outstanding wire SMPs to drop below some configured
> value, there is also an additional limit introduced for transaction based SMPs.
> These timeout based SMPs are capped at a configured maximum value.
> 
> Two new options are added for this:
> max_wire_smps2 indicates the second (higher) limit of timeout based
> SMPs supported. When this limit is reached, timeout based SMPs
> are not longer sent (until the number of outstanding ones drops below
> this limit).
> max_smps_timeout indicates the number of microseconds used for the
> timeout in between sending SMPs when the oustanding wire count is above
> max_wire_smps and below max_wire_smps2. It defaults to the transaction
> timeout times the transaction retries.
> 
> The timeout based SMP mechanism can be disabled by setting max_wire_smps2 
> to the same value as max_wire_smps. This is equivalent to the (current)
> algorithm prior to this change. By default, this mechanism is disabled.
> 
> Signed-off-by: Hal Rosenstock <hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

Applied. Thanks.

Sasha
--
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:[~2010-06-09 19:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-09 18:29 [PATCHv3] opensm: Better handling of non responsive SMAs Hal Rosenstock
     [not found] ` <20100609182911.GA26769-Wuw85uim5zDR7s880joybQ@public.gmane.org>
2010-06-09 19:37   ` Sasha Khapyorsky [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=20100609193707.GK20172@me \
    --to=sashak-smomgflxvozwk0htik3j/w@public.gmane.org \
    --cc=hnrose-Wuw85uim5zDR7s880joybQ@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