[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240317203645.GB5975@lst.de>
Date: Sun, 17 Mar 2024 21:36:45 +0100
From: Christoph Hellwig <hch@....de>
To: kernel test robot <oliver.sang@...el.com>
Cc: Christoph Hellwig <hch@....de>, oe-lkp@...ts.linux.dev, lkp@...el.com,
linux-kernel@...r.kernel.org, Keith Busch <kbusch@...nel.org>,
Max Gurtovoy <mgurtovoy@...dia.com>, linux-nvme@...ts.infradead.org,
ying.huang@...el.com, feng.tang@...el.com, fengwei.yin@...el.com
Subject: Re: [linus:master] [nvme] 63dfa10043: fsmark.files_per_sec 6.4%
improvement
On Fri, Mar 15, 2024 at 04:21:13PM +0800, kernel test robot wrote:
>
>
> Hello,
>
> kernel test robot noticed a 6.4% improvement of fsmark.files_per_sec on:
>
>
> commit: 63dfa1004322d596417f23da43cdc43cf6298c71 ("nvme: move NVME_QUIRK_DEALLOCATE_ZEROES out of nvme_config_discard")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>
> testcase: fsmark
> test machine: 96 threads 2 sockets Intel(R) Xeon(R) Platinum 8260L CPU @ 2.40GHz (Cascade Lake) with 128G memory
> parameters:
That is kinda odd and unexpected. Is this system using one of the old
Intel SSDs that this quirk is actually used for?
Powered by blists - more mailing lists