On Fri, Apr 30, 2021 at 10:57:20AM +0200, Thomas Gleixner wrote:
On Fri, Apr 30 2021 at 16:13, Feng Tang wrote:
> On Tue, Apr 20, 2021 at 11:08:37AM +0800, kernel test robot wrote:
>> 69995ebbb9 ("signal: Hand SIGQUEUE_PREALLOC flag to
>> 4bad58ebc8 ("signal: Allow tasks to cache one sigqueue struct")
>> 69995ebbb9d37173 4bad58ebc8bc4f20d89cff95417
>> ---------------- ---------------------------
>> %stddev %change %stddev
>> \ | \
>> 1.273e+09 -3.3% 1.231e+09 will-it-scale.192.threads
>> 6630224 -3.3% 6409738 will-it-scale.per_thread_ops
>> 1.273e+09 -3.3% 1.231e+09 will-it-scale.workload
> We've double checked this, and it seems to be another case of
> the code alignment change caused regression change, just like
> the other case we debugged " [genirq] cbe16f35be:
> will-it-scale.per_thread_ops -5.2% regression"
> With the same debug patch of forcing function address 64 bytes
> aligned, then commit 4bad58ebc8 will bring no change on this case.
> commit 09c60546f04f "./Makefile: add debug option to enable function
> aligned on 32 bytes" only forced 32 bytes align, with thinking 64B
> align will occupy more code space, and affect iTLB more. Maybe we
> should just extend it to 64B align, as it is for debug only anyway.
thanks for the heads up!
But why is this restricted to debug mode?
The fact that adding a few bytes of text causes regressions in unrelated
code is not restricted to debug or am I missing something here?
With the default kernel config of 0day, 64B_force_aligned kernel is 11%
bigger than the 32B_force_aligned kernel (both the vmlinux and its text
size), and benchmark also shows there are performance drops with the
64B_forced_aligned kernel (should be related with more i-cache and i-TLB
Also we are still looking for other ways with same effect, while not
increasing kernel text so much. So we are still put it under debug