On Wed, Aug 21, 2019 at 03:56:50PM +0200, Steffan Karger wrote:
> While this sounds like something we'd like to have (i.e, feature-ACK),
> this doesn't really explain why this change resolves the issue, nor why
> this is the right fix.

As a bit of background why I assume this will fix "things" - we have a
few places in the connection sequence where we do something, and when
it's finished, set up a coarse timer to "go on with the next step" -
which always means "1 second delay" because that's how the coarse
timers work.

I've dug into this a bit when figuring out commit afb93fac803fbab7 -
which helped a bit (this was setting up an "in 1 second" coarse timer, 
which always got an extra second due to scheduling), but I'm sure there
is more room for improvement.

OTOH this is all tricky code, with client and server and tcp and udp
all intermixed.


"If was one thing all people took for granted, was conviction that if you 
 feed honest figures into a computer, honest figures come out. Never doubted 
 it myself till I met a computer with a sense of humor."
                             Robert A. Heinlein, The Moon is a Harsh Mistress

Gert Doering - Munich, Germany                             g...@greenie.muc.de

Attachment: signature.asc
Description: PGP signature

Openvpn-devel mailing list

Reply via email to