mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yin Fengwei <fengwei.yin@intel.com>
To: kernel test robot <oliver.sang@intel.com>,
	Brian Foster <bfoster@redhat.com>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
	Dave Chinner <dchinner@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>, <lkp@lists.01.org>,
	<lkp@intel.com>, <ying.huang@intel.com>, <feng.tang@intel.com>,
	<zhengjun.xing@linux.intel.com>
Subject: Re: [xfs] 6191cf3ad5: stress-ng.rename.ops_per_sec -73.5% regression
Date: Wed, 2 Mar 2022 16:32:02 +0800	[thread overview]
Message-ID: <191b6d46-cb8d-4e5d-8c4c-9dae91e32a45@intel.com> (raw)
In-Reply-To: <20220131154927.GF16385@xsang-OptiPlex-9020>

Hi,

On 2022/1/31 23:49, kernel test robot wrote:
>        0.00           +59.8       59.78        perf-profile.calltrace.cycles-pp.osq_lock.__mutex_lock.flush_workqueue.xfs_fs_statfs.statfs_by_dentry
>       23.44 ±  2%     +61.0       84.49        perf-profile.calltrace.cycles-pp.vfs_statfs.user_statfs.__do_sys_statfs.do_syscall_64.entry_SYSCALL_64_after_hwframe
>       23.40 ±  2%     +61.1       84.47        perf-profile.calltrace.cycles-pp.statfs_by_dentry.vfs_statfs.user_statfs.__do_sys_statfs.do_syscall_64

We did further check of the perf data. From above three lines,
the patch brought higher lock content (+59.8) in this extreme cases.

Regarding the patch could fix race issue, we will not tracking this
report. Let us know if you have any comments. Thanks.


Regards
Yin, Fengwei


      reply	other threads:[~2022-03-02  8:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-31 15:49 kernel test robot
2022-03-02  8:32 ` Yin Fengwei [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=191b6d46-cb8d-4e5d-8c4c-9dae91e32a45@intel.com \
    --to=fengwei.yin@intel.com \
    --cc=bfoster@redhat.com \
    --cc=dchinner@redhat.com \
    --cc=djwong@kernel.org \
    --cc=feng.tang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=lkp@lists.01.org \
    --cc=oliver.sang@intel.com \
    --cc=ying.huang@intel.com \
    --cc=zhengjun.xing@linux.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

all inboxes | Powered by JetHome®