| Re: [chrony-dev] nts_ke_server calling UTI_GetRandomBytesUrandom |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-dev] nts_ke_server calling UTI_GetRandomBytesUrandom
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Tue, 2 Aug 2022 13:00:21 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1659438026; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=4obxE64Do/oHgS6hEVbBVIZfO8XEnE+Z9QCUHdlF+kU=; b=HV53bWdQBtBEbSMAfV0YtvBad365Bu1QdIgsRgWoF11VnxbySB/L6OttqFNbnBskAY+Bqw f1n+sxV908qLD4KG45B898D2CLTePGqwXpwBdMLtb0cPd6xO/5nfvEllcIrKPt4oFPjvVW VM3s7BFhXsPadF/7WOCVeh042rvbzbc=
On Mon, Aug 01, 2022 at 02:07:53AM +0000, Elliott, Robert (Servers) wrote:
> I see the glibc discussion about arc4random has led to a proposal this
> weekend to add a vDSO for the linux kernel's getrandom(). It'll be
> interesting to see if that is accepted - Linus' initial reaction was "no".
I was surprised to see they switched arc4random in glibc to
getrandom(). That has a significant performance impact on chronyd, as
it calls the function for each generated RX and TX timestamp. In my
test the maximum number of requests per second handled as a server
dropped by about 25%. That's not great.
We'll need to disable the function on Linux, at least until the vDSO
getrandom() is widely available.
--
Miroslav Lichvar
--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.