From: Schspa Shi <schspa@gmail.com>
To: lkp@lists.01.org
Subject: Re: [workqueue] 1a0a67f5ef: phoronix-test-suite.fio.SequentialRead.IO_uring.Yes.No.1MB.DefaultTestDirectory.mb_s -17.7% regression
Date: Wed, 13 Jul 2022 14:09:28 +0800 [thread overview]
Message-ID: <m2bkttms3w.fsf@gmail.com> (raw)
In-Reply-To: <Ys4zVkJCH04cnSGX@xsang-OptiPlex-9020>
[-- Attachment #1: Type: text/plain, Size: 399 bytes --]
kernel test robot <oliver.sang@intel.com> writes:
> Greeting,
>
> FYI, we noticed a -17.7% regression of phoronix-test-suite.fio.SequentialRead.IO_uring.Yes.No.1MB.DefaultTestDirectory.mb_s due to commit:
>
This performance drop can be fixed by convert to wq_pool_attach_mutex
to a rwsem, or add another lock for this. I will upload a new PATCH
version for this.
--
BRs
Schspa Shi
WARNING: multiple messages have this Message-ID (diff)
From: Schspa Shi <schspa@gmail.com>
To: kernel test robot <oliver.sang@intel.com>
Cc: 0day robot <lkp@intel.com>, LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org, ying.huang@intel.com, feng.tang@intel.com,
zhengjun.xing@linux.intel.com, fengwei.yin@intel.com,
guobing.chen@intel.com, ming.a.chen@intel.com,
frank.du@intel.com, Shuhua.Fan@intel.com, wangyang.guo@intel.com,
Wenhuan.Huang@intel.com, jessica.ji@intel.com,
shan.kang@intel.com, guangli.li@intel.com, tiejun.li@intel.com,
yu.ma@intel.com, dapeng1.mi@intel.com, jiebin.sun@intel.com,
gengxin.xie@intel.com, fan.zhao@intel.com, tj@kernel.org,
jiangshanlai@gmail.com
Subject: Re: [workqueue] 1a0a67f5ef: phoronix-test-suite.fio.SequentialRead.IO_uring.Yes.No.1MB.DefaultTestDirectory.mb_s -17.7% regression
Date: Wed, 13 Jul 2022 14:09:28 +0800 [thread overview]
Message-ID: <m2bkttms3w.fsf@gmail.com> (raw)
In-Reply-To: <Ys4zVkJCH04cnSGX@xsang-OptiPlex-9020>
kernel test robot <oliver.sang@intel.com> writes:
> Greeting,
>
> FYI, we noticed a -17.7% regression of phoronix-test-suite.fio.SequentialRead.IO_uring.Yes.No.1MB.DefaultTestDirectory.mb_s due to commit:
>
This performance drop can be fixed by convert to wq_pool_attach_mutex
to a rwsem, or add another lock for this. I will upload a new PATCH
version for this.
--
BRs
Schspa Shi
next prev parent reply other threads:[~2022-07-13 6:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 9:05 [PATCH] workqueue: Use active mask for new worker when pool is DISASSOCIATED Schspa Shi
2022-07-13 2:52 ` [workqueue] 1a0a67f5ef: phoronix-test-suite.fio.SequentialRead.IO_uring.Yes.No.1MB.DefaultTestDirectory.mb_s -17.7% regression kernel test robot
2022-07-13 2:52 ` kernel test robot
2022-07-13 6:09 ` Schspa Shi [this message]
2022-07-13 6:09 ` Schspa Shi
2022-07-13 9:52 ` [PATCH] workqueue: Use active mask for new worker when pool is DISASSOCIATED Lai Jiangshan
2022-07-13 11:22 ` Schspa Shi
2022-07-14 14:39 ` Peter Zijlstra
2022-07-14 15:17 ` Schspa Shi
2022-07-30 3:49 ` Schspa Shi
2022-08-01 3:56 ` Lai Jiangshan
2022-08-01 4:42 ` Schspa Shi
2022-08-01 8:48 ` Lai Jiangshan
2022-08-01 9:32 ` Schspa Shi
2022-08-07 13:52 ` Schspa Shi
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=m2bkttms3w.fsf@gmail.com \
--to=schspa@gmail.com \
--cc=lkp@lists.01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.