[PATCH] stdmem: free: only call _gcry_secmem_free if needed
Kristian Fiskerstrand
kristian.fiskerstrand at sumptuouscapital.com
Tue Oct 30 21:55:14 CET 2018
On 10/28/18 12:46 AM, Jussi Kivilinna wrote:
> Unnecessarily taking secmem lock on non-secure memory can result poor
> performance on multi-threaded workloads:
> https://marc.info/?l=gcrypt-devel&m=153424107207061&w=2
If you are making changes to the patch anyways, maybe update this
comment to use
https://lists.gnupg.org/pipermail/gcrypt-devel/2018-August/004535.html
instead so we don't rely on third party service? It was painful enough
when Gmane dissapeared.
--
----------------------------
Kristian Fiskerstrand
Blog: https://blog.sumptuouscapital.com
Twitter: @krifisk
----------------------------
Public OpenPGP keyblock at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
----------------------------
Timendi causa est nescire
The cause of fear is ignorance
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <https://lists.gnupg.org/pipermail/gcrypt-devel/attachments/20181030/abe50665/attachment.sig>
More information about the Gcrypt-devel
mailing list