From: Seebs <seebs@seebs.net>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH][RFC] pseudo: intercept syscall() and return ENOTSUP for renameat2
Date: Wed, 4 Apr 2018 16:45:05 -0500 [thread overview]
Message-ID: <20180404164505.00553b97@seebsdell> (raw)
In-Reply-To: <39787e20-0d21-00bd-a5bb-73faa52c0839@gmail.com>
On Wed, 4 Apr 2018 14:28:11 -0700
Khem Raj <raj.khem@gmail.com> wrote:
> what is the performance impact of adding another stack frame and
> function call in the chain here. Do we have data ?
Very close to unmeasurable, because *almost nothing ever uses syscall*.
This is used only for the case where someone is explicitly calling
syscall(), not for any other system call use case. And my
implementation (which is not the same as this one) also overrides the
wrapper generation, so there's no standard pseudo wrapper overhead
(which is several times larger and involves mutexes and signal mask
changing), it's just passing the call on unless it's SYS_renameat2.
-s
next prev parent reply other threads:[~2018-04-04 21:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 15:48 [PATCH][RFC] pseudo: intercept syscall() and return ENOTSUP for renameat2 Ross Burton
2018-03-27 15:53 ` Seebs
2018-03-27 16:02 ` ✗ patchtest: failure for " Patchwork
2018-03-27 22:43 ` [PATCH][RFC] " Andre McCurdy
2018-03-28 9:15 ` Burton, Ross
2018-03-31 4:15 ` Andre McCurdy
2018-03-31 5:06 ` Seebs
2018-03-31 6:02 ` Andre McCurdy
2018-03-31 15:35 ` Seebs
2018-03-31 15:58 ` Bruce Ashfield
2018-03-31 13:12 ` Richard Purdie
2018-03-31 15:39 ` Seebs
2018-03-31 21:03 ` Joshua Watt
2018-03-31 21:16 ` Seebs
2018-04-02 22:20 ` Richard Purdie
2018-04-04 21:28 ` Khem Raj
2018-04-04 21:45 ` Seebs [this message]
2018-04-05 0:29 ` Khem Raj
2018-04-04 21:51 ` Andre McCurdy
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=20180404164505.00553b97@seebsdell \
--to=seebs@seebs.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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