From: Ammar Faizi <[email protected]>
To: Guillem Jover <[email protected]>,
Stefan Hajnoczi <[email protected]>,
io-uring Mailing List <[email protected]>,
Jens Axboe <[email protected]>, Jeff Moyer <[email protected]>,
Alviro Iskandar Setiawan <[email protected]>
Subject: Re: False positives in nolibc check
Date: Wed, 21 Jun 2023 23:08:15 +0700 [thread overview]
Message-ID: <ZJMgby+JVuFP/[email protected]> (raw)
In-Reply-To: <[email protected]>
On Wed, Jun 21, 2023 at 01:51:56PM +0200, Guillem Jover wrote:
> So, I also think I'd appreciate a --use-libc mode (or similar) which I'd
> probably consider enabling for Debian.
I'll send a patch to add that mode for review tomorrow morning.
> OTOH, I've no idea how much impact that would cause to performance? Do
> any of you have numbers?
The only real *hot path* that depended on a libc function was
io_uring_submit(). It used syscall(2) function.
But now even when compiled with libc, we no longer use syscall(2),
instead we use inline assembly to invoke syscall. So there is nothing to
worry about performance here.
Side note:
liburing still uses syscall(2) on architectures other than x86, x86-64
and aarch64.
--
Ammar Faizi
next prev parent reply other threads:[~2023-06-21 16:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 13:31 False positives in nolibc check Stefan Hajnoczi
2023-06-20 14:39 ` Alviro Iskandar Setiawan
2023-06-21 9:47 ` Stefan Hajnoczi
2023-06-20 15:49 ` Ammar Faizi
2023-06-20 16:16 ` Alviro Iskandar Setiawan
2023-06-21 10:04 ` Stefan Hajnoczi
2023-06-21 10:19 ` Ammar Faizi
2023-06-21 11:51 ` Guillem Jover
2023-06-21 16:08 ` Ammar Faizi [this message]
2023-07-12 15:00 ` Stefan Hajnoczi
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=ZJMgby+JVuFP/[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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