[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150127200642.441db19f@jpm-OptiPlex-GX620>
Date: Tue, 27 Jan 2015 20:06:42 +0200
From: Jack Morgenstein <jackm@....mellanox.co.il>
To: David Laight <David.Laight@...LAB.COM>
Cc: 'Amir Vadai' <amirv@...lanox.com>,
"David S. Miller" <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Or Gerlitz <ogerlitz@...lanox.com>,
Yevgeny Petrilin <yevgenyp@...lanox.com>
Subject: Re: [PATCH net-next V1 04/11] net/mlx4_core: Adjust command
timeouts to conform to the firmware spec
On Tue, 27 Jan 2015 14:30:31 +0000
David Laight <David.Laight@...LAB.COM> wrote:
> From: Amir Vadai
> > From: Jack Morgenstein <jackm@....mellanox.co.il>
> >
> > The firmware spec states that the timeout for all commands should
> > be 60 seconds.
>
> Hmmm... 60 seconds seems a long time to wait for a device to do
> something.
>
> I'll have given up and reset the machine before that expires.
>
> David
>
We have some automatic recovery features which involve resetting the
HCA upon command timeout, and we purposely give a long timeout
in order to be sure that there are no false positives
(i.e., unjustified resets).
-Jack
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists