From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>,
Gao Xiang <hsiangkao@linux.alibaba.com>,
linux-xfs <linux-xfs@vger.kernel.org>,
Zorro Lang <zlang@redhat.com>
Subject: Re: [report] Unixbench shell1 performance regression
Date: Tue, 18 Mar 2025 01:10:53 -0700 [thread overview]
Message-ID: <Z9kqjdXM8i-7bS9o@infradead.org> (raw)
In-Reply-To: <Z9jUXkfmDYc0Vlni@debian>
On Tue, Mar 18, 2025 at 10:03:10AM +0800, Gao Xiang wrote:
> Anyway, I've got the community view of Unixbench. I will arrange my
> own TODO list.
FYI, while I agree with all of Dave's observation on Unixbench I don't
entirely agree with the conclusion. Yes, we should not bend over
backwards to optimize for this workload. But if we can find an easy
enough way to improve it I'm all in favour. While everyone should
know not to do subsector writes there's actually still plenty of
workloads that do. And while those are not the heavily optimized ones
that really matter it would still be nice to get good numbers for them.
So if you can find a way to optimize it without much negative impact
I'd love to see that.
next prev parent reply other threads:[~2025-03-18 8:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 17:19 [report] Unixbench shell1 performance regression Gao Xiang
2025-03-16 21:25 ` Dave Chinner
2025-03-17 0:25 ` Gao Xiang
2025-03-17 20:43 ` Dave Chinner
2025-03-18 0:29 ` Gao Xiang
2025-03-18 0:58 ` Dave Chinner
2025-03-18 2:03 ` Gao Xiang
2025-03-18 8:10 ` Christoph Hellwig [this message]
2025-03-18 9:27 ` Gao Xiang
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=Z9kqjdXM8i-7bS9o@infradead.org \
--to=hch@infradead.org \
--cc=david@fromorbit.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@redhat.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 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.