[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20250129210923.1861-1-sj@kernel.org>
Date: Wed, 29 Jan 2025 13:09:23 -0800
From: SeongJae Park <sj@...nel.org>
To: Shakeel Butt <shakeel.butt@...ux.dev>
Cc: SeongJae Park <sj@...nel.org>,
"Liam R. Howlett" <Liam.Howlett@...cle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
David Hildenbrand <david@...hat.com>,
Lorenzo Stoakes <lorenzo.stoakes@...cle.com>,
Vlastimil Babka <vbabka@...e.cz>,
linux-kernel@...r.kernel.org,
linux-mm@...ck.org
Subject: Re: [RFC PATCH v2 0/4] mm/madvise: remove redundant mmap_lock operations from process_madvise()
Hi Shakeel,
On Wed, 29 Jan 2025 11:22:29 -0800 Shakeel Butt <shakeel.butt@...ux.dev> wrote:
> On Thu, Jan 16, 2025 at 05:30:54PM -0800, SeongJae Park wrote:
> > process_madvise() calls do_madvise() for each address range. Then, each
> > do_madvise() invocation holds and releases same mmap_lock. Optimize the
> > redundant lock operations by splitting do_madvise() internal logics
> > including the mmap_lock operations, and calling the small logics
> > directly from process_madvise() in a sequence that removes the redundant
> > locking.
> >
>
> You skipped the evaluation section which was present in the v1. If you
> decide to post a new version, please include that otherwise we can ask
> Andrew to pickup the evaluation section from the v1 [1].
>
> [1] https://lore.kernel.org/all/20250111004618.1566-1-sj@kernel.org/
Sure. I will run the evaluation again on the new version and include the
result on the next version.
Also, thank you very much for reviews :)
Thanks,
SJ
Powered by blists - more mailing lists