From: Niklas Cassel <cassel@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: kernel test robot <oliver.sang@intel.com>,
oe-lkp@lists.linux.dev, lkp@intel.com,
Jens Axboe <axboe@kernel.dk>, Damien Le Moal <dlemoal@kernel.org>,
Hannes Reinecke <hare@suse.de>,
linux-m68k@lists.linux-m68k.org, linux-um@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
drbd-dev@lists.linbit.com, nbd@other.debian.org,
linuxppc-dev@lists.ozlabs.org, ceph-devel@vger.kernel.org,
virtualization@lists.linux.dev, xen-devel@lists.xenproject.org,
linux-bcache@vger.kernel.org, dm-devel@lists.linux.dev,
linux-raid@vger.kernel.org, linux-mmc@vger.kernel.org,
linux-mtd@lists.infradead.org, nvdimm@lists.linux.dev,
linux-nvme@lists.infradead.org, linux-s390@vger.kernel.org,
linux-scsi@vger.kernel.org, ying.huang@intel.com,
feng.tang@intel.com, fengwei.yin@intel.com
Subject: Re: [axboe-block:for-next] [block] bd4a633b6f: fsmark.files_per_sec -64.5% regression
Date: Mon, 24 Jun 2024 15:45:57 +0200 [thread overview]
Message-ID: <Znl4lXRmK2ukDB7r@ryzen.lan> (raw)
In-Reply-To: <20240624083537.GA19941@lst.de>
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?
>
Seems to be ATA SSD:
https://download.01.org/0day-ci/archive/20240624/202406241546.6bbd44a7-oliver.sang@intel.com/job.yaml
ssd_partitions: "/dev/disk/by-id/ata-INTEL_SSDSC2BG012T4_BTHC428201ZX1P2OGN-part1"
Most likely btrfs does something different depending on the nonrot flag
being set or not. (And like you are suggesting, most likely the value of
the nonrot flag is somehow different after commit bd4a633b6f)
Kind regards,
Niklas
WARNING: multiple messages have this Message-ID (diff)
From: Niklas Cassel <cassel@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: kernel test robot <oliver.sang@intel.com>,
oe-lkp@lists.linux.dev, lkp@intel.com,
Jens Axboe <axboe@kernel.dk>, Damien Le Moal <dlemoal@kernel.org>,
Hannes Reinecke <hare@suse.de>,
linux-m68k@lists.linux-m68k.org, linux-um@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
drbd-dev@lists.linbit.com, nbd@other.debian.org,
linuxppc-dev@lists.ozlabs.org, ceph-devel@vger.kernel.org,
virtualization@lists.linux.dev, xen-devel@lists.xenproject.org,
linux-bcache@vger.kernel.org, dm-devel@lists.linux.dev,
linux-raid@vger.kernel.org, linux-mmc@vger.kernel.org,
linux-mtd@lists.infradead.org, nvdimm@lists.linux.dev,
linux-nvme@lists.infradead.org, linux-s390@vger.kernel.org,
linux-scsi@vger.kernel.org, ying.huang@intel.com,
feng.tang@intel.com, fengwei.yin@intel.com
Subject: Re: [axboe-block:for-next] [block] bd4a633b6f: fsmark.files_per_sec -64.5% regression
Date: Mon, 24 Jun 2024 15:45:57 +0200 [thread overview]
Message-ID: <Znl4lXRmK2ukDB7r@ryzen.lan> (raw)
In-Reply-To: <20240624083537.GA19941@lst.de>
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?
>
Seems to be ATA SSD:
https://download.01.org/0day-ci/archive/20240624/202406241546.6bbd44a7-oliver.sang@intel.com/job.yaml
ssd_partitions: "/dev/disk/by-id/ata-INTEL_SSDSC2BG012T4_BTHC428201ZX1P2OGN-part1"
Most likely btrfs does something different depending on the nonrot flag
being set or not. (And like you are suggesting, most likely the value of
the nonrot flag is somehow different after commit bd4a633b6f)
Kind regards,
Niklas
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: Niklas Cassel <cassel@kernel.org>
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,
kernel test robot <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: Mon, 24 Jun 2024 15:45:57 +0200 [thread overview]
Message-ID: <Znl4lXRmK2ukDB7r@ryzen.lan> (raw)
In-Reply-To: <20240624083537.GA19941@lst.de>
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?
>
Seems to be ATA SSD:
https://download.01.org/0day-ci/archive/20240624/202406241546.6bbd44a7-oliver.sang@intel.com/job.yaml
ssd_partitions: "/dev/disk/by-id/ata-INTEL_SSDSC2BG012T4_BTHC428201ZX1P2OGN-part1"
Most likely btrfs does something different depending on the nonrot flag
being set or not. (And like you are suggesting, most likely the value of
the nonrot flag is somehow different after commit bd4a633b6f)
Kind regards,
Niklas
WARNING: multiple messages have this Message-ID (diff)
From: Niklas Cassel <cassel@kernel.org>
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,
kernel test robot <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: Mon, 24 Jun 2024 15:45:57 +0200 [thread overview]
Message-ID: <Znl4lXRmK2ukDB7r@ryzen.lan> (raw)
In-Reply-To: <20240624083537.GA19941@lst.de>
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?
>
Seems to be ATA SSD:
https://download.01.org/0day-ci/archive/20240624/202406241546.6bbd44a7-oliver.sang@intel.com/job.yaml
ssd_partitions: "/dev/disk/by-id/ata-INTEL_SSDSC2BG012T4_BTHC428201ZX1P2OGN-part1"
Most likely btrfs does something different depending on the nonrot flag
being set or not. (And like you are suggesting, most likely the value of
the nonrot flag is somehow different after commit bd4a633b6f)
Kind regards,
Niklas
next prev parent reply other threads:[~2024-06-24 13:46 UTC|newest]
Thread overview: 23+ 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:25 ` kernel test robot
2024-06-24 8:25 ` kernel test robot
2024-06-24 8:35 ` Christoph Hellwig
2024-06-24 8:35 ` Christoph Hellwig
2024-06-24 8:35 ` Christoph Hellwig
2024-06-24 13:45 ` Niklas Cassel [this message]
2024-06-24 13:45 ` Niklas Cassel
2024-06-24 13:45 ` Niklas Cassel
2024-06-24 13:45 ` Niklas Cassel
2024-06-24 14:21 ` Anthony D'Atri
2024-06-24 14:21 ` Anthony D'Atri
2024-06-24 14:21 ` Anthony D'Atri
2024-06-24 15:20 ` Christoph Hellwig
2024-06-24 15:20 ` Christoph Hellwig
2024-06-24 15:20 ` Christoph Hellwig
2024-06-26 6:11 ` Oliver Sang
2024-06-26 6:11 ` Oliver Sang
2024-06-26 6:11 ` Oliver Sang
2024-06-26 6:11 ` Oliver Sang
2024-06-26 6:18 ` Christoph Hellwig
2024-06-26 6:18 ` Christoph Hellwig
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=Znl4lXRmK2ukDB7r@ryzen.lan \
--to=cassel@kernel.org \
--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=oliver.sang@intel.com \
--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 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.