Re: [axboe-block:for-next] [block] 1122c0c1cc: aim7.jobs-per-min 22.6% improvement
Christoph Hellwig <[email protected]> Wed, 26 Jun 2024 21:54:05 -0700
| Newsgroups | dev.linux.lists.drbd-dev,dev.linux.lists.dm-devel,dev.linux.lists.nvdimm,dev.linux.lists.oe-lkp,dev.linux.lists.virtualization,org.infradead.lists.linux-mtd,org.infradead.lists.linux-nvme,org.infradead.lists.linux-um,org.kernel.vger.linux-bcache,org.kernel.vger.linux-block,org.kernel.vger.linux-mmc,org.kernel.vger.linux-raid,org.kernel.vger.linux-scsi,org.ozlabs.lists.linuxppc-dev,org.xenproject.lists.xen-devel |
|---|---|
| Message-ID | <[email protected]> |
On Thu, Jun 27, 2024 at 10:35:38AM +0800, Oliver Sang wrote: > > I failed to apply patch in your previous reply to 1122c0c1cc or current tip > of axboe-block/for-next: > c1440ed442a58 (axboe-block/for-next) Merge branch 'for-6.11/block' into for-next That already includes it. > > but it's ok to apply upon next: > * 0fc4bfab2cd45 (tag: next-20240625) Add linux-next specific files for 20240625 > > I've already started the test based on this applyment. > is the expectation that patch should not introduce performance change comparing > to 0fc4bfab2cd45? > > or if this applyment is not ok, please just give me guidance. Thanks! The expectation is that the latest block branch (and thus linux-next) doesn't see this performance change.