From: Yu Zhao <yuzhao@google.com>
To: Jaewon Kim <jaewon31.kim@gmail.com>
Cc: jaewon31.kim@samsung.com,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"tjmercier@google.com" <tjmercier@google.com>,
"kaleshsingh@google.com" <kaleshsingh@google.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"vbabka@suse.cz" <vbabka@suse.cz>,
"hannes@cmpxchg.org" <hannes@cmpxchg.org>,
"sj@kernel.org" <sj@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-trace-kernel@vger.kernel.org"
<linux-trace-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH v4] vmscan: add trace events for lru_gen
Date: Sun, 1 Oct 2023 21:26:53 -0600 [thread overview]
Message-ID: <CAOUHufaqROR00_u6enJxhvGuPLTLMW_t4MSMqvDuyGpTECU3Mg@mail.gmail.com> (raw)
In-Reply-To: <CAJrd-Uu16oZncaFzycGoyryxyjEGFWJdecQoShveGV6_GGJLiQ@mail.gmail.com>
On Sun, Oct 1, 2023 at 5:41 PM Jaewon Kim <jaewon31.kim@gmail.com> wrote:
>
> Hello Yu Zhao
>
> Could you give me your comment? I am waiting for your opinion on the
> reuse method. I'm planning to resend it as a complete patch with it.
> Thank you.
Acked-by: Yu Zhao <yuzhao@google.com>
prev parent reply other threads:[~2023-10-02 3:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230926042019epcas1p11c28533f7b7db99db9f9d8a03ddd332c@epcas1p1.samsung.com>
2023-09-26 4:22 ` Jaewon Kim
2023-09-26 4:42 ` Yu Zhao
[not found] ` <CGME20230926042019epcas1p11c28533f7b7db99db9f9d8a03ddd332c@epcms1p3>
2023-09-26 5:10 ` 김재원
[not found] ` <CGME20230926042019epcas1p11c28533f7b7db99db9f9d8a03ddd332c@epcms1p1>
2023-09-26 7:33 ` 김재원
[not found] ` <CGME20230926042019epcas1p11c28533f7b7db99db9f9d8a03ddd332c@epcms1p5>
2023-09-26 14:15 ` 김재원
2023-10-01 23:41 ` Jaewon Kim
2023-10-02 3:26 ` Yu Zhao [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=CAOUHufaqROR00_u6enJxhvGuPLTLMW_t4MSMqvDuyGpTECU3Mg@mail.gmail.com \
--to=yuzhao@google.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=jaewon31.kim@gmail.com \
--cc=jaewon31.kim@samsung.com \
--cc=kaleshsingh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sj@kernel.org \
--cc=tjmercier@google.com \
--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