-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
So, I managed to figure out why the patch I posted yesterday wasn't
working for me. It would appear that in comparing transport timeouts,
to_increment is only used when to_exponential is false. nfs uses
to_exponential = 1, and doens't set to_increment at all. I didn't catch
this earlier because I likely had slab debugging on and instead of
to_increment being garbage values, it was the test pattern (a5a5a5a5).
Anyhow, here is an updated version of the patch which does the timeout
comparison the right way. Works for me in a not-so-tested environment.
- --
Mike Waychison
Sun Microsystems, Inc.
1 (650) 352-5299 voice
1 (416) 202-8336 voice
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTICE: The opinions expressed in this email are held by me,
and may not represent the views of Sun Microsystems, Inc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBuJgOdQs4kOxk3/MRAr/jAJ9ogzmFQ2iCZGbvvdc/EYewbWjmdACdHI7A
5Uay1xrNaYhGzDY1rft2EVY=
=ndVJ
-----END PGP SIGNATURE-----