linux-kernel - Re: [PATCH] mm: shmem: fix the shmem large folio allocation for the i915 driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <20250728151604.e834daa64e8c816aeffba975@linux-foundation.org>
Date: Mon, 28 Jul 2025 15:16:04 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Patryk Kowalczyk <patryk@...alczyk.ws>
Cc: Baolin Wang <baolin.wang@...ux.alibaba.com>, hughd@...gle.com,
 ville.syrjala@...ux.intel.com, david@...hat.com, willy@...radead.org,
 maarten.lankhorst@...ux.intel.com, mripard@...nel.org, tzimmermann@...e.de,
 airlied@...il.com, simona@...ll.ch, jani.nikula@...ux.intel.com,
 joonas.lahtinen@...ux.intel.com, rodrigo.vivi@...el.com,
 tursulin@...ulin.net, christian.koenig@....com, ray.huang@....com,
 matthew.auld@...el.com, matthew.brost@...el.com,
 dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
 linux-mm@...ck.org
Subject: Re: [PATCH] mm: shmem: fix the shmem large folio allocation for the
 i915 driver

On Mon, 28 Jul 2025 23:59:22 +0200 Patryk Kowalczyk <patryk@...alczyk.ws> wrote:

> In my tests, the performance drop ranges from a few percent up to 13% in
> Unigine Superposition
> under heavy memory usage on the CPU Core Ultra 155H with the Xe 128 EU GPU.
> Other users have reported performance impact up to 30% on certain workloads.
> Please find more  in the regressions reports:
> https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/14645
> https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13845
> 
> I believe the change should be backported to all active kernel branches
> after version 6.12.

OK, thanks.  I added this (important!) info to the changelog and I
added a cc:stable, requesting a backport into everything which has
acd7ccb284b8.

I'll place this in mm.git's mm-hotfixes-unstable branch with a plan to
upstream it sometime during the 6.17-rcX cycle.