From: Oliver Sang <oliver.sang@intel.com>
To: Benjamin Coddington <bcodding@redhat.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Lance Shelton <lance.shelton@hammerspace.com>,
Trond Myklebust <trond.myklebust@hammerspace.com>,
<linux-nfs@vger.kernel.org>,
"Trond Myklebust" <trondmy@kernel.org>,
Anna Schumaker <anna@kernel.org>,
Jeff Layton <jlayton@kernel.org>, <oliver.sang@intel.com>
Subject: Re: [PATCH v3 2/3] nfs: Add timecreate to nfs inode
Date: Tue, 17 Jun 2025 16:48:17 +0800 [thread overview]
Message-ID: <aFEr0edl4bHYtY3u@xsang-OptiPlex-9020> (raw)
In-Reply-To: <1877A633-7DCE-4598-BEE5-83E854F7DE61@redhat.com>
hi, Benjamin Coddington,
On Thu, Jun 12, 2025 at 11:32:05AM -0400, Benjamin Coddington wrote:
> On 12 Jun 2025, at 3:22, kernel test robot wrote:
>
> > Hello,
> >
> > kernel test robot noticed a 41.2% regression of stress-ng.msg.ops_per_sec on:
>
> Wow, this is really unexpected here - best I can think is that we're mucking
> up cachelines in a very problematic way, but then NFS would have to be
> involved in the test somehow and I don't see evidence of that.
>
> LKP folks, is there some NFS on the test system that could be in play? I
> see that you collect nfsstat output, but I don't see that output in the
> details. Is it possible this report could be an anomaly?
sorry about this, seems this is a wrong report. there is no NFS involved in this
test, so there is no nfsstat monitor enabled while doing tests.
one possibility is fs/ is build earlier, which impacts the kernel image layout.
we observed the cases that stress-ng tests are sensitive to this kind of
alignment changes.
sorry for the wrong report.
>
> Ben
>
next prev parent reply other threads:[~2025-06-17 8:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 10:45 [PATCH v3 0/3] NFS Client btime support Benjamin Coddington
2025-05-29 10:45 ` [PATCH v3 1/3] Expand the type of nfs_fattr->valid Benjamin Coddington
2025-05-29 10:45 ` [PATCH v3 2/3] nfs: Add timecreate to nfs inode Benjamin Coddington
2025-06-12 7:22 ` kernel test robot
2025-06-12 15:32 ` Benjamin Coddington
2025-06-17 8:48 ` Oliver Sang [this message]
2025-06-12 15:28 ` Benjamin Coddington
2025-05-29 10:45 ` [PATCH v3 3/3] NFS: Return the file btime in the statx results when appropriate Benjamin Coddington
2025-05-29 11:06 ` [PATCH v3 0/3] NFS Client btime support Jeff Layton
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=aFEr0edl4bHYtY3u@xsang-OptiPlex-9020 \
--to=oliver.sang@intel.com \
--cc=anna@kernel.org \
--cc=bcodding@redhat.com \
--cc=jlayton@kernel.org \
--cc=lance.shelton@hammerspace.com \
--cc=linux-nfs@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=trond.myklebust@hammerspace.com \
--cc=trondmy@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox