From: Oliver Sang <oliver.sang@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: nvdimm@lists.linux.dev, feng.tang@intel.com,
linux-nvme@lists.infradead.org, fengwei.yin@intel.com,
linux-mtd@lists.infradead.org, linux-bcache@vger.kernel.org,
drbd-dev@lists.linbit.com, linux-s390@vger.kernel.org,
lkp@intel.com, linux-scsi@vger.kernel.org, ying.huang@intel.com,
xen-devel@lists.xenproject.org, dm-devel@lists.linux.dev,
linux-um@lists.infradead.org, virtualization@lists.linux.dev,
nbd@other.debian.org, linux-raid@vger.kernel.org,
linux-m68k@lists.linux-m68k.org,
Damien Le Moal <dlemoal@kernel.org>,
Hannes Reinecke <hare@suse.de>,
ceph-devel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, linux-mmc@vger.kernel.org,
linux-kernel@vger.kernel.org, oliver.sang@intel.com,
oe-lkp@lists.linux.dev, linuxppc-dev@lists.ozlabs.org
Subject: Re: [axboe-block:for-next] [block] bd4a633b6f: fsmark.files_per_sec -64.5% regression
Date: Wed, 26 Jun 2024 14:11:11 +0800 [thread overview]
Message-ID: <Znuw/4zMD4w5Oq2a@xsang-OptiPlex-9020> (raw)
In-Reply-To: <20240624083537.GA19941@lst.de>
hi, Christoph Hellwig,
On Mon, Jun 24, 2024 at 10:35:37AM +0200, Christoph Hellwig wrote:
> This is odd to say at least. Any chance you can check the value
> of /sys/block/$DEVICE/queue/rotational for the relevant device before
> and after this commit? And is this an ATA or NVMe SSD?
>
yeah, as Niklas mentioned, it's an ATA SSD.
I checked the /sys/block/$DEVICE/queue/rotational before and after this commit,
both show '0'. not sure if this is expected.
anyway, I noticed you send a patch [1]
so I applied this patch upon bd4a633b6f, and found the performance restored.
=========================================================================================
compiler/cpufreq_governor/disk/filesize/fs2/fs/iterations/kconfig/nr_directories/nr_files_per_directory/nr_threads/rootfs/sync_method/tbox_group/test_size/testcase:
gcc-13/performance/1SSD/9B/nfsv4/btrfs/1x/x86_64-rhel-8.3/16d/256fpd/32t/debian-12-x86_64-20240206.cgz/fsyncBeforeClose/lkp-ivb-2ep2/400M/fsmark
commit:
1122c0c1cc ("block: move cache control settings out of queue->flags")
bd4a633b6f ("block: move the nonrot flag to queue_limits")
e9a0f6a398 = bd4a633b6f + patch [1]
1122c0c1cc71f740 bd4a633b6f7c3c6b6ebc1a07317 e9a0f6a398f162d115d208ad95b
---------------- --------------------------- ---------------------------
%stddev %change %stddev %change %stddev
\ | \ | \
4177 ± 2% -64.7% 1475 -1.1% 4130 fsmark.files_per_sec
[1] https://lore.kernel.org/all/20240624173835.76753-1-hch@lst.de/
next prev parent reply other threads:[~2024-06-26 6:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 8:25 [axboe-block:for-next] [block] bd4a633b6f: fsmark.files_per_sec -64.5% regression kernel test robot
2024-06-24 8:35 ` Christoph Hellwig
2024-06-24 13:45 ` Niklas Cassel
2024-06-24 14:21 ` Anthony D'Atri
2024-06-24 15:20 ` Christoph Hellwig
2024-06-26 6:11 ` Oliver Sang [this message]
2024-06-26 6:18 ` Christoph Hellwig
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=Znuw/4zMD4w5Oq2a@xsang-OptiPlex-9020 \
--to=oliver.sang@intel.com \
--cc=axboe@kernel.dk \
--cc=ceph-devel@vger.kernel.org \
--cc=dlemoal@kernel.org \
--cc=dm-devel@lists.linux.dev \
--cc=drbd-dev@lists.linbit.com \
--cc=feng.tang@intel.com \
--cc=fengwei.yin@intel.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lkp@intel.com \
--cc=nbd@other.debian.org \
--cc=nvdimm@lists.linux.dev \
--cc=oe-lkp@lists.linux.dev \
--cc=virtualization@lists.linux.dev \
--cc=xen-devel@lists.xenproject.org \
--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;
as well as URLs for NNTP newsgroup(s).