From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>,
linux-mm@kvack.org
Subject: Re: [PATCH v1 0/5] MM_CID and HPCC mm_struct static init fixes
Date: Wed, 24 Dec 2025 11:37:50 -0500 [thread overview]
Message-ID: <dd9fa8f0-b39f-4651-825d-a3d52c33d589@efficios.com> (raw)
In-Reply-To: <20251222175957.bfc9cf8b25e587f3f5e304bc@linux-foundation.org>
On 2025-12-22 20:59, Andrew Morton wrote:
[...]
> Well, simply appending this series to your "mm: Fix OOM killer
> inaccuracy on large many-core systems, v10" will create an annoying
> bisection hole.
>
> Also, there are some cc:stable fixes in here which depend upon the
> presence of "mm: Fix OOM killer inaccuracy on large many-core systems"
> series, which is all backwards.
>
>
> So for now I'll toss this series in there for testing but I'll ask for
> a redo, please.
>
> - All cc:stable patches prepared in a standalone fashion against
> latest mainline.
>
> - Any non-cc:stable patches which fix things in current mm-new come
> next. Perhaps view these as preparation for "mm: Fix OOM killer
> inaccuracy on large many-core systems".
>
> - Then "mm: Fix OOM killer inaccuracy on large many-core systems,
> v11" which incorporates anything which didn't make it into the above
> two categories.
>
> That could be as many as three patch series. Thanks.
Will do! It may take a few days due to holiday vacations here.
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
prev parent reply other threads:[~2025-12-24 16:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-21 23:29 Mathieu Desnoyers
2025-12-21 23:29 ` [PATCH v1 1/5] mm: Add missing static initializer for init_mm::mm_cid.lock Mathieu Desnoyers
2025-12-21 23:29 ` [PATCH v1 2/5] mm: Rename cpu_bitmap field to flexible_array Mathieu Desnoyers
2025-12-21 23:29 ` [PATCH v1 3/5] mm: Take into account mm_cid size for mm_struct static definitions Mathieu Desnoyers
2025-12-21 23:29 ` [PATCH v1 4/5] mm: Take into account hierarchical percpu tree items for static mm_struct definitions Mathieu Desnoyers
2025-12-21 23:29 ` [PATCH v1 5/5] tsacct: Skip all kernel threads Mathieu Desnoyers
2025-12-23 1:59 ` [PATCH v1 0/5] MM_CID and HPCC mm_struct static init fixes Andrew Morton
2025-12-24 16:37 ` Mathieu Desnoyers [this message]
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=dd9fa8f0-b39f-4651-825d-a3d52c33d589@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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