Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Salvatore Dipietro <dipiets@amazon.it>
To: <stable@vger.kernel.org>
Cc: <dipietro.salvatore@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Vlastimil Babka <vbabka@kernel.org>,
	Johannes Weiner <hannes@cmpxchg.org>, <linux-mm@kvack.org>
Subject: [STABLE 7.3.y] 0e05a469c294 ("mm/page_alloc: avoid direct reclaim and compaction for costly __GFP_NORETRY allocations")
Date: Thu, 12 Nov 2026 09:42:05 +0000	[thread overview]
Message-ID: <20261112094205.994560-1-dipiets@amazon.it> (raw)


Hi,

Please apply to 7.3.y:

  0e05a469c294 ("mm/page_alloc: avoid direct reclaim and compaction for costly __GFP_NORETRY allocations")

It fixes a regression from 5d8edfb900d5 ("iomap: Copy larger chunks
from userspace"), in since v6.6: PostgreSQL pgbench on XFS runs at
0.38x throughput. Andrew and Vlastimil agreed to restore its
Cc: stable [1], but it was merged without the tag.

It depends on 6ee3d87b9408 and fe21f930d1e6, already queued for 7.3.

I'll send backports for 6.18.y, 6.12.y and 6.6.y separately.

[1] https://lore.kernel.org/all/1fc0caa5-43b1-487f-94cf-0d1aff4c03fd@kernel.org/

Thanks,
Salvatore



AMAZON DEVELOPMENT CENTER ITALY SRL, viale Monte Grappa 3/5, 20124 Milano, Italia, Registro delle Imprese di Milano Monza Brianza Lodi REA n. 2504859, Capitale Sociale: 10.000 EUR i.v., Cod. Fisc. e P.IVA 10100050961, Societa con Socio Unico




             reply	other threads:[~2026-11-12  9:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-12  9:42 Salvatore Dipietro [this message]
2026-11-13  2:33 ` [STABLE 7.3.y] 0e05a469c294 ("mm/page_alloc: avoid direct reclaim and compaction for costly __GFP_NORETRY allocations") Sasha Levin

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=20261112094205.994560-1-dipiets@amazon.it \
    --to=dipiets@amazon.it \
    --cc=akpm@linux-foundation.org \
    --cc=dipietro.salvatore@gmail.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-mm@kvack.org \
    --cc=stable@vger.kernel.org \
    --cc=vbabka@kernel.org \
    /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