[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240913141651.30385-A-hca@linux.ibm.com>
Date: Fri, 13 Sep 2024 16:16:51 +0200
From: Heiko Carstens <hca@...ux.ibm.com>
To: "Jason A. Donenfeld" <Jason@...c4.com>
Cc: Alexander Gordeev <agordeev@...ux.ibm.com>,
Vasily Gorbik <gor@...ux.ibm.com>,
Christian Borntraeger <borntraeger@...ux.ibm.com>,
Sven Schnelle <svens@...ux.ibm.com>,
Harald Freudenberger <freude@...ux.ibm.com>,
Stefan Liebler <stli@...ux.ibm.com>, linux-kernel@...r.kernel.org,
linux-crypto@...r.kernel.org, linux-s390@...r.kernel.org
Subject: Re: [PATCH 7/7] s390/vdso: Wire up getrandom() vdso implementation
On Fri, Sep 13, 2024 at 03:53:43PM +0200, Jason A. Donenfeld wrote:
> On Fri, Sep 13, 2024 at 03:05:43PM +0200, Heiko Carstens wrote:
> > The vdso testcases vdso_test_getrandom and vdso_test_chacha pass.
>
> I'd be curious to see the results of ./vdso_test_getrandom bench-single
> and such.
It looks like this with two layers of hypervisors in between, but that
shouldn't matter too much for this type of workload:
$ ./vdso_test_getrandom bench-single
vdso: 25000000 times in 0.493703559 seconds
libc: 25000000 times in 6.371764073 seconds
syscall: 25000000 times in 6.584025337 seconds
Powered by blists - more mailing lists