From: Mel Gorman <mgorman@techsingularity.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Hugh Dickins <hughd@google.com>, Yu Zhao <yuzhao@google.com>,
Vlastimil Babka <vbabka@suse.cz>,
Marcelo Tosatti <mtosatti@redhat.com>,
Michal Hocko <mhocko@kernel.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>,
Mel Gorman <mgorman@techsingularity.net>
Subject: [PATCH v3 0/2] Leave IRQs enabled for per-cpu page allocations
Date: Fri, 18 Nov 2022 10:17:12 +0000 [thread overview]
Message-ID: <20221118101714.19590-1-mgorman@techsingularity.net> (raw)
Changelog since V2
o Fix list corruption issue (hughd)
o Tighen up locking protocol (hughd)
o Micro-optimisations (hughd)
Changelog since V1
o Use trylock in free_unref_page_list due to IO completion from
softirq context (yuzhao)
This was a standalone patch but now split in two. The main changes since
v2 are fixing the issues exposed by Hugh's shmfs stress test.
Patch 1 is a long-standing issue that is technically a bug but happened
to work because of how it was used.
Patch 2 leaves IRQs enabled for most PCP allocations with more details
in the changelog itself.
--
2.35.3
next reply other threads:[~2022-11-18 10:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 10:17 Mel Gorman [this message]
2022-11-18 10:17 ` [PATCH 1/2] mm/page_alloc: Always remove pages from temporary list Mel Gorman
2022-11-18 13:24 ` Vlastimil Babka
2022-11-18 10:17 ` [PATCH 2/2] mm/page_alloc: Leave IRQs enabled for per-cpu page allocations Mel Gorman
2022-11-18 14:30 ` Vlastimil Babka
2022-11-21 12:01 ` Mel Gorman
2022-11-21 16:03 ` Mel Gorman
2022-11-22 9:11 ` Vlastimil Babka
2022-11-22 9:09 ` Vlastimil Babka
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=20221118101714.19590-1-mgorman@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--cc=mhocko@kernel.org \
--cc=mtosatti@redhat.com \
--cc=vbabka@suse.cz \
--cc=yuzhao@google.com \
/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