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: [PATCHv2] opensm: Add a rate based mechanism for SMP transactions
Date: Wed, 9 Jun 2010 17:22:39 +0300 [thread overview]
Message-ID: <20100609142239.GG20172@me> (raw)
In-Reply-To: <AANLkTinOqJRYEev6Iz0EJyuAN_N8bP1OcSEFMprMkY4Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 10:14 Wed 09 Jun , Hal Rosenstock wrote:
> >>
> >> The default in the proposed patch is that this mechanism is disabled.
> >> Are you saying to change this to have it enabled with a default
> >> timeout ?
> >
> > No, meaning that the default case is both limits are equivalent.
>
> Equivalent in what way ?
By value.
>
> > The timeout is less matter in this case.
>
> So 3 configurables rather than 2 ? max_wire_timeout_smps (for the
> second limit), max_wire_timeout (along the lines of what you propose),
> and mechanism enable/disable (default disabled).
maxsmps (already exists)
maxsmps2 (default - = maxsmps, so the mechanism is disabled)
maxsmps_timeout (optional for both disable/enable cases)
Something like this... Maybe with better names :)
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
prev parent reply other threads:[~2010-06-09 14:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-07 12:40 [PATCHv2] opensm: Add a rate based mechanism for SMP transactions Hal Rosenstock
[not found] ` <20100607124057.GA2060-Wuw85uim5zDR7s880joybQ@public.gmane.org>
2010-06-09 6:05 ` Sasha Khapyorsky
2010-06-09 10:27 ` Hal Rosenstock
[not found] ` <AANLkTimE6n2e6z1pUXQPmqX5GrdLVl2kp7bbPipDfhy2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-06-09 12:29 ` Sasha Khapyorsky
2010-06-09 13:02 ` Hal Rosenstock
[not found] ` <AANLkTin1X450bG2WvV7y8wanYSBH4JyNgNiCsj2iugL8-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-06-09 14:05 ` Sasha Khapyorsky
2010-06-09 14:14 ` Hal Rosenstock
[not found] ` <AANLkTinOqJRYEev6Iz0EJyuAN_N8bP1OcSEFMprMkY4Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-06-09 14:22 ` 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=20100609142239.GG20172@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