From: Dave Hansen <dave.hansen@intel.com>
To: kernel test robot <yi1.lai@intel.com>,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
x86@kernel.org, Daniel Borkmann <daniel@iogearbox.net>,
Dave Hansen <dave.hansen@linux.intel.com>
Subject: Re: [linus:master] [x86/bugs] a3af84b0fa: stress-ng.seccomp.ops_per_sec 95.7% regression
Date: Wed, 19 Aug 2026 08:26:53 -0700 [thread overview]
Message-ID: <b771b524-ceca-4766-9eaa-07bee153802a@intel.com> (raw)
In-Reply-To: <202608191340.98574fe2-lkp@intel.com>
On 8/18/26 23:20, kernel test robot wrote:
> kernel test robot noticed a 95.7% regression of stress-ng.seccomp.ops_per_sec on:
One one level this is a "vulnerability mitigations cause performance
loss, news at 11" kind of thing. Like, Duh!
The microbenchmark here does seem to be a pretty worse-case scenario
where it sits in a loop loading and running a seccomp filter program. In
other words, it's just about as pathological of a test as you can have.
I think Pawan had some more ideas about ways to optimize this. Is there
any appetite for that? Or is the test just too synthetic to worry about?
next prev parent reply other threads:[~2026-08-19 15:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 6:20 [linus:master] [x86/bugs] a3af84b0fa: stress-ng.seccomp.ops_per_sec 95.7% regression kernel test robot
2026-08-19 15:26 ` Dave Hansen [this message]
2026-08-19 18:59 ` Pawan Gupta
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=b771b524-ceca-4766-9eaa-07bee153802a@intel.com \
--to=dave.hansen@intel.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=x86@kernel.org \
--cc=yi1.lai@intel.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