From: Jeff Law <jeffreyalaw@gmail.com>
To: Palmer Dabbelt <palmer@rivosinc.com>, adhemerval.zanella@linaro.org
Cc: Evan Green <evan@rivosinc.com>,
libc-alpha@sourceware.org, slewis@rivosinc.com,
Vineet Gupta <vineetg@rivosinc.com>
Subject: Re: [PATCH v2 0/3] RISC-V: ifunced memcpy using new kernel hwprobe interface
Date: Thu, 30 Mar 2023 00:20:48 -0600 [thread overview]
Message-ID: <9290df69-8946-3b67-63ea-3d386a3c30a6@gmail.com> (raw)
In-Reply-To: <mhng-070c6c08-7d42-4392-a1ac-bbe91948d105@palmer-ri-x1c9a>
On 3/29/23 13:45, Palmer Dabbelt wrote:
> It's not in for-next yet, but various patch sets / proposals have been
> on the lists for a few months and it seems like discussion on the kernel
> side has pretty much died down. That's why I was pinging the glibc side
> of things, if anyone here has comments on the interface then it's time
> to chime in. If there's no comments then we're likely to end up with
> this in the next release (so queue into for-next soon, Linus' master in
> a month or so).
Right. And I've suggested that we at least try to settle on the various
mem* and str* implementations independently of the kernel->glibc
interface question.
I don't much care how we break down the problem of selecting
implementations, just that we get started. That can and probably
should be happening in parallel with the kernel->glibc API work.
I've got some performance testing to do in this space (primarily of the
VRULL implementations). It's just going to take a long time to get the
data. And that implementation probably needs some revamping after all
the work on the mem* and str* infrastructure that landed earlier this year.
jeff
next prev parent reply other threads:[~2023-03-30 6:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 19:15 Evan Green
2023-02-21 19:15 ` [PATCH v2 1/3] riscv: Add Linux hwprobe syscall support Evan Green
2023-03-29 18:38 ` Adhemerval Zanella Netto
2023-02-21 19:15 ` [PATCH v2 2/3] riscv: Add hwprobe vdso call support Evan Green
2023-03-29 18:39 ` Adhemerval Zanella Netto
2023-02-21 19:15 ` [PATCH v2 3/3] riscv: Add and use alignment-ignorant memcpy Evan Green
2023-03-28 22:54 ` [PATCH v2 0/3] RISC-V: ifunced memcpy using new kernel hwprobe interface Palmer Dabbelt
2023-03-28 23:41 ` Adhemerval Zanella Netto
2023-03-29 0:01 ` Palmer Dabbelt
2023-03-29 19:16 ` Adhemerval Zanella Netto
2023-03-29 19:45 ` Palmer Dabbelt
2023-03-29 20:13 ` Adhemerval Zanella Netto
2023-03-30 18:31 ` Evan Green
2023-03-30 19:43 ` Adhemerval Zanella Netto
2023-03-30 6:20 ` Jeff Law [this message]
2023-03-30 18:43 ` Evan Green
2023-03-31 5:09 ` Jeff Law
2023-03-30 19:38 ` Adhemerval Zanella Netto
2023-03-31 18:07 ` Jeff Law
2023-03-31 18:34 ` Palmer Dabbelt
2023-03-31 19:32 ` Adhemerval Zanella Netto
2023-03-31 20:19 ` Jeff Law
2023-03-31 21:03 ` Palmer Dabbelt
2023-03-31 21:35 ` Jeff Law
2023-03-31 21:38 ` Palmer Dabbelt
2023-03-31 22:10 ` Jeff Law
2023-04-07 15:36 ` Palmer Dabbelt
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=9290df69-8946-3b67-63ea-3d386a3c30a6@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=adhemerval.zanella@linaro.org \
--cc=evan@rivosinc.com \
--cc=libc-alpha@sourceware.org \
--cc=palmer@rivosinc.com \
--cc=slewis@rivosinc.com \
--cc=vineetg@rivosinc.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).