Re: SRP subnet timeout

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 9/26/19 11:14 AM, Bart Van Assche wrote:

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

On 9/26/19 8:00 AM, Karandeep Chahal wrote:
I understand that you have made "SRP CM timeout dependent on subnet timeout", but my question is, why did you add "2" to the subnet timeout? How did you come up with
this number?

Forgive me but it is not obvious to me after reading the commit message.

Hi Karandeep,

I haven't done any kind of deep research to come up with that value. My goal was to preserve the CM timeout used by the SRP initiator for the default opensm subnet timeout value (18). There may be better choices for the SRP CM timeout.

Bart.

Hi Bart,

My apologies for top-posting.

The problem with adding 2 to SRP CM timeout is that it makes the SRP CM timeout value far off the subnet timeout value. Now you can either have a reasonable subnet timeout value and an unreasonable SRP CM timeout value, or an unreasonable subnet timeout and a reasonable SRP CM timeout.

-Karan




[Index of Archives]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Photo]     [Yosemite News]     [Yosemite Photos]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux