From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: SeongJae Park <sj@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Liam R. Howlett" <howlett@gmail.com>,
David Hildenbrand <david@redhat.com>,
Shakeel Butt <shakeel.butt@linux.dev>,
Vlastimil Babka <vbabka@suse.cz>,
kernel-team@meta.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH 0/4] mm/madvise: cleanup requests validations and classifications
Date: Thu, 13 Mar 2025 05:30:09 +0000 [thread overview]
Message-ID: <add63931-2b94-4bd4-a8a3-b5754671b437@lucifer.local> (raw)
In-Reply-To: <20250312164750.59215-1-sj@kernel.org>
On Wed, Mar 12, 2025 at 09:47:46AM -0700, SeongJae Park wrote:
> Cleanup madvise entry level code for cleaner request validations and
> classifications.
>
> Note that this series was a part of another one[1], and separated to
> this one following a reviewer's nice comment[2].
Thanks :>)
>
> Changes from the original series
> (https://lore.kernel.org/20250310172318.653630-1-sj@kernel.org)
> - Separate from the tlb flushes batching part
> - Collect Reviewed-by: tags from Lorenzo
> - Fix typos and wordsmith commit messages and comments
> - Rebase on latest mm-unstable
>
> [1] https://lore.kernel.org/20250310172318.653630-1-sj@kernel.org
> [2] https://lore.kernel.org/0f90d56e-5960-4478-803e-1054696c0cde@lucifer.local
>
> SeongJae Park (4):
> mm/madvise: use is_memory_failure() from madvise_do_behavior()
> mm/madvise: split out populate behavior check logic
> mm/madvise: deduplicate madvise_do_behavior() skip case handlings
> mm/madvise: remove len parameter of madvise_do_behavior()
>
> mm/madvise.c | 128 +++++++++++++++++++++++++++++----------------------
> 1 file changed, 74 insertions(+), 54 deletions(-)
>
>
> base-commit: 733c75c2264b9de72a463f731507e674a32ff094
> --
> 2.39.5
prev parent reply other threads:[~2025-03-13 5:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 16:47 SeongJae Park
2025-03-12 16:47 ` [PATCH 1/4] mm/madvise: use is_memory_failure() from madvise_do_behavior() SeongJae Park
2025-03-12 20:52 ` Shakeel Butt
2025-03-12 16:47 ` [PATCH 2/4] mm/madvise: split out populate behavior check logic SeongJae Park
2025-03-12 20:53 ` Shakeel Butt
2025-03-12 16:47 ` [PATCH 3/4] mm/madvise: deduplicate madvise_do_behavior() skip case handlings SeongJae Park
2025-03-12 20:53 ` Shakeel Butt
2025-03-12 16:47 ` [PATCH 4/4] mm/madvise: remove len parameter of madvise_do_behavior() SeongJae Park
2025-03-12 20:54 ` Shakeel Butt
2025-03-13 5:30 ` Lorenzo Stoakes [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=add63931-2b94-4bd4-a8a3-b5754671b437@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=howlett@gmail.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shakeel.butt@linux.dev \
--cc=sj@kernel.org \
--cc=vbabka@suse.cz \
/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