From: Carlos Llamas <cmllamas@google.com>
To: Lei Liu <liulei.rjpt@vivo.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Arve Hjønnevåg" <arve@android.com>,
"Todd Kjos" <tkjos@android.com>,
"Martijn Coenen" <maco@android.com>,
"Joel Fernandes" <joel@joelfernandes.org>,
"Christian Brauner" <brauner@kernel.org>,
"Suren Baghdasaryan" <surenb@google.com>,
linux-kernel@vger.kernel.org, opensource.kernel@vivo.com
Subject: Re: [PATCH v3] binder_alloc: Replace kcalloc with kvcalloc to mitigate OOM issues
Date: Wed, 19 Jun 2024 23:41:28 +0000 [thread overview]
Message-ID: <ZnNsqBNeXnyzhtZ5@google.com> (raw)
In-Reply-To: <239d2936-8fae-4538-8621-b07c09918df9@vivo.com>
On Wed, Jun 19, 2024 at 04:44:07PM +0800, Lei Liu wrote:
> We used the "adb shell stop" command to retest the data.
>
> Now, the test data for kmalloc and vmalloc are basically consistent.
Ok, this matches my observations too.
> Can I prepare the V4 version of the patch now? Do I need to modify anything
> else in the V4 version, in addition to addressing the following two points?
>
> 1.Shorten the "backtrace" in the commit message.
>
> 2.Modify the code indentation to comply with the community's code style
> requirements.
Yeap, that would be all. Thanks.
Carlos Llamas
prev parent reply other threads:[~2024-06-19 23:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 4:09 [PATCH v3] binder_alloc: Replace kcalloc with kvcalloc to mitigate OOM issues Lei Liu
2024-06-14 18:38 ` Carlos Llamas
2024-06-17 4:01 ` Lei Liu
2024-06-17 18:43 ` Carlos Llamas
2024-06-18 2:50 ` Lei Liu
2024-06-18 4:37 ` Carlos Llamas
2024-06-19 8:35 ` Lei Liu
2024-06-19 8:44 ` Lei Liu
2024-06-19 23:41 ` Carlos Llamas [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=ZnNsqBNeXnyzhtZ5@google.com \
--to=cmllamas@google.com \
--cc=arve@android.com \
--cc=brauner@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liulei.rjpt@vivo.com \
--cc=maco@android.com \
--cc=opensource.kernel@vivo.com \
--cc=surenb@google.com \
--cc=tkjos@android.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.