[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231107090829.259753-1-aliceryhl@google.com>
Date: Tue, 7 Nov 2023 09:08:29 +0000
From: Alice Ryhl <aliceryhl@...gle.com>
To: Carlos Llamas <cmllamas@...gle.com>
Cc: "Arve Hjønnevåg" <arve@...roid.com>,
Christian Brauner <brauner@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Joel Fernandes <joel@...lfernandes.org>,
kernel-team@...roid.com, linux-kernel@...r.kernel.org,
Martijn Coenen <maco@...roid.com>,
Suren Baghdasaryan <surenb@...gle.com>,
Todd Kjos <tkjos@...roid.com>
Subject: Re: [PATCH 14/21] binder: do not add pages to LRU in release path
Carlos Llamas <cmllamas@...gle.com> writes:
> In binder_alloc_deferred_release() pages are added to the LRU list via
> binder_free_buf_locked(). However, this is pointless because these pages
> are kfree'd immediately afterwards. Add an option to skip the LRU list.
They aren't freed with kfree, buf with __free_page.
> Signed-off-by: Carlos Llamas <cmllamas@...gle.com>
The change itself looks correct, so I'll give my tag for this:
Reviewed-by: Alice Ryhl <aliceryhl@...gle.com>
But I'm wondering whether process cleanup really is so performance
intensive to justify the added complexity of this?
Alice
Powered by blists - more mailing lists