From: Kees Cook <keescook@chromium.org>
To: wanghongzhe <wanghongzhe@huawei.com>, luto@amacapital.net
Cc: Kees Cook <keescook@chromium.org>,
bpf@vger.kernel.org, yhs@fb.com, netdev@vger.kernel.org,
ast@kernel.org, linux-kernel@vger.kernel.org, andrii@kernel.org,
daniel@iogearbox.net, songliubraving@fb.com, kafai@fb.com,
kpsingh@kernel.org, john.fastabend@gmail.com, wad@chromium.org
Subject: Re: [PATCH v2] seccomp: Improve performace by optimizing rmb()
Date: Wed, 10 Feb 2021 12:44:07 -0800 [thread overview]
Message-ID: <161298984230.3996968.4640881413498941015.b4-ty@chromium.org> (raw)
In-Reply-To: <1612496049-32507-1-git-send-email-wanghongzhe@huawei.com>
On Fri, 5 Feb 2021 11:34:09 +0800, wanghongzhe wrote:
> According to kees's suggest, we started with the patch that just replaces
> rmb() with smp_rmb() and did a performace test with UnixBench. The results
> showed the overhead about 2.53% in rmb() test compared to the smp_rmb()
> one, in a x86-64 kernel with CONFIG_SMP enabled running inside a qemu-kvm
> vm. The test is a "syscall" testcase in UnixBench, which executes 5
> syscalls in a loop during a certain timeout (100 second in our test) and
> counts the total number of executions of this 5-syscall sequence. We set a
> seccomp filter with all allow rule for all used syscalls in this test
> (which will go bitmap path) to make sure the rmb() will be executed. The
> details for the test:
>
> [...]
Applied to for-next/seccomp, thanks!
[1/1] seccomp: Improve performace by optimizing rmb()
https://git.kernel.org/kees/c/a381b70a1cf8
--
Kees Cook
prev parent reply other threads:[~2021-02-10 20:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 3:34 [PATCH v2] seccomp: Improve performace by optimizing rmb() wanghongzhe
2021-02-10 20:44 ` Kees Cook [this message]
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=161298984230.3996968.4640881413498941015.b4-ty@chromium.org \
--to=keescook@chromium.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=wad@chromium.org \
--cc=wanghongzhe@huawei.com \
--cc=yhs@fb.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 NNTP newsgroup(s).