From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Huacai Chen <chenhuacai@kernel.org>
Cc: Xi Ruoyao <xry111@xry111.site>, WANG Xuerui <kernel@xen0n.name>,
linux-crypto@vger.kernel.org, loongarch@lists.linux.dev,
Jinyang He <hejinyang@loongson.cn>,
Tiezhu Yang <yangtiezhu@loongson.cn>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re:
Date: Mon, 19 Aug 2024 13:01:48 +0000 [thread overview]
Message-ID: <ZsNCPKo9XZG52Yph@zx2c4.com> (raw)
In-Reply-To: <CAAhV-H5a42p6AAda=ncqCdmpHyc_tpXHjDVHq_F1pPZumfGeLw@mail.gmail.com>
> I don't see significant improvements about LSX here, so I prefer to
> just use the generic version to avoid complexity (I remember Linus
> said the whole of __vdso_getrandom is not very useful).
I'm inclined to feel the same way, at least for now. Let's just go with
one implementation -- the generic one -- and then we can see if
optimization really makes sense later. I suspect the large speedup we're
already getting from being in the vDSO is already sufficient for
purposes.
Regards,
Jason
next prev parent reply other threads:[~2024-08-19 13:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 11:07 Xi Ruoyao
2024-08-16 11:07 ` [PATCH v3 1/3] LoongArch: vDSO: Wire up getrandom() vDSO implementation Xi Ruoyao
2024-08-19 12:41 ` Huacai Chen
2024-08-19 13:03 ` Jason A. Donenfeld
2024-08-19 15:36 ` Xi Ruoyao
2024-08-20 0:50 ` Jinyang He
2024-08-20 1:09 ` Xi Ruoyao
2024-08-20 2:03 ` Jinyang He
2024-08-16 11:07 ` [PATCH v3 2/3] LoongArch: Perform alternative runtime patching on vDSO Xi Ruoyao
2024-08-16 11:07 ` [PATCH v3 3/3] LoongArch: vDSO: Add LSX implementation of vDSO getrandom() Xi Ruoyao
2024-08-19 12:40 ` Huacai Chen
2024-08-19 13:01 ` Jason A. Donenfeld [this message]
2024-08-19 15:22 ` Re: Xi Ruoyao
2024-08-19 15:54 ` Re: Xi Ruoyao
2024-08-19 15:22 ` Re: Xi Ruoyao
2024-08-27 9:45 ` Re: Jason A. Donenfeld
-- strict thread matches above, loose matches on Subject: below --
2022-01-13 17:53 Varun Sethi
2022-01-14 17:17 ` Fabio Estevam
2021-01-19 0:10 David Howells
2021-01-20 14:46 ` Jarkko Sakkinen
2017-11-13 14:55 Re: Amos Kalonzo
2017-05-03 6:23 Re: H.A
2017-02-23 15:09 Qin's Yanjun
[not found] <E5ACCB586875944EB0AE0E3EFA32B4F526FAD24C@exchange0.winona.edu>
2016-05-16 23:02 ` RE: Weichert, Brian
[not found] <B719EF0A9FB7A247B5147CD67A83E60E011FEB76D1@EXCH10-MB3.paterson.k12.nj.us>
2013-08-23 10:47 ` RE: Ruiz, Irma
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZsNCPKo9XZG52Yph@zx2c4.com \
--to=jason@zx2c4.com \
--cc=arnd@arndb.de \
--cc=chenhuacai@kernel.org \
--cc=hejinyang@loongson.cn \
--cc=kernel@xen0n.name \
--cc=linux-crypto@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=xry111@xry111.site \
--cc=yangtiezhu@loongson.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).