From: Jeff Layton <jlayton@kernel.org>
To: Christian Brauner <brauner@kernel.org>
Cc: kernel test robot <oliver.sang@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
oe-lkp@lists.linux.dev, lkp@intel.com,
Linux Memory Management List <linux-mm@kvack.org>,
Josef Bacik <josef@toxicpanda.com>,
"Darrick J. Wong" <djwong@kernel.org>,
linux-xfs@vger.kernel.org, ying.huang@intel.com,
feng.tang@intel.com, fengwei.yin@intel.com
Subject: Re: [linux-next:master] [xfs] 3062a738d7: filebench.sum_operations/s -85.0% regression
Date: Tue, 01 Oct 2024 11:29:10 -0400 [thread overview]
Message-ID: <af844e8dff16f5003e0fc32616420c6c96d1e06b.camel@kernel.org> (raw)
In-Reply-To: <20241001-lausbub-skilift-10d22cfbf03c@brauner>
On Tue, 2024-10-01 at 17:09 +0200, Christian Brauner wrote:
> On Mon, Sep 30, 2024 at 02:21:30PM GMT, Jeff Layton wrote:
> > This is a known problem.
> >
> > I have a fix that moves the floor handing into the timekeeper, but
> > Thomas said he had a better way to do this, so I haven't resent them
> > yet.
> >
> > The patches in Christian's tree are out of date, so it may be best to
> > just drop them for now until I have the newer set ready.
>
> Yeah, I only kept including them while the merge window wasn't closed so
> not to cause unnecessary churn pre merge window (Since we only got the
> performance regression report at -rc7...).
Understood.
After I wrote this, Thomas replied and said that he couldn't suggest
any way to improve on what I'm already doing in this series. I re-
posted the set a few hours ago, so it might be good to replace that
series in your tree with those.
Hopefully the timekeeping devs will send some Acked-by's or R-b's soon
(hint, hint)!
--
Jeff Layton <jlayton@kernel.org>
prev parent reply other threads:[~2024-10-01 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-29 14:36 kernel test robot
2024-09-30 18:21 ` Jeff Layton
2024-10-01 15:09 ` Christian Brauner
2024-10-01 15:29 ` Jeff Layton [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=af844e8dff16f5003e0fc32616420c6c96d1e06b.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=feng.tang@intel.com \
--cc=fengwei.yin@intel.com \
--cc=josef@toxicpanda.com \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=tglx@linutronix.de \
--cc=ying.huang@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