public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Khapyorsky <sashak-smomgflXvOZWk0Htik3J/w@public.gmane.org>
To: Hal Rosenstock <hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] opensm/osm_vendor_ibumad.c: Add environment variable to change max retries
Date: Thu, 22 Oct 2009 15:50:04 +0200	[thread overview]
Message-ID: <20091022135004.GK20210@me> (raw)
In-Reply-To: <f0e08f230910220556h3d7352f4s4bd8e57c0a01a5d0-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 08:56 Thu 22 Oct     , Hal Rosenstock wrote:
> >
> > Why do you need this?
> 
> It is useful in some clusters where the default behavior is
> insufficient

I would suppose that by itself this may indicate some external issues
like bad connectivity (cabling) or similar and some investigation would
be helpful there (regardless to number of retries).

> and control over the number of retries helps and there is
> no vendor API support for this.
> 
> > And why did you choose to use environment variable and not command
> > line/config option? I think that it is less obvious.
> 
> It was modeled after OSM_UMAD_MAX_PENDING.

It was internal libvendor hack (which is also not 100% clean :))
controlling ibumad implementation specific parameter. Unlike this a
number of MAD retries (similar to MAD response timeout value) has more
generic meaning.

> It could be made a command
> line/options file item. Is that your preference ?

I think command line/config option is a way to do it.

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:[~2009-10-22 13:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-19 18:33 [PATCH] opensm/osm_vendor_ibumad.c: Add environment variable to change max retries Hal Rosenstock
     [not found] ` <20091019183342.GA28926-Wuw85uim5zDR7s880joybQ@public.gmane.org>
2009-10-22 12:24   ` Sasha Khapyorsky
2009-10-22 12:56     ` Hal Rosenstock
     [not found]       ` <f0e08f230910220556h3d7352f4s4bd8e57c0a01a5d0-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-22 13:50         ` Sasha Khapyorsky [this message]
2009-10-22 15:41           ` Hal Rosenstock
     [not found]             ` <f0e08f230910220841s220373fau2cd4e814ec77ca25-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-23 21:33               ` Sasha Khapyorsky
2009-10-23 22:02                 ` Hal Rosenstock
     [not found]                   ` <f0e08f230910231502p1758a8ag6c3852802aca40a7-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-23 22:41                     ` Sasha Khapyorsky

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=20091022135004.GK20210@me \
    --to=sashak-smomgflxvozwk0htik3j/w@public.gmane.org \
    --cc=hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@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