linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hongbo Li <lihongbo22@huawei.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: <muchun.song@linux.dev>, <mhiramat@kernel.org>,
	<mathieu.desnoyers@efficios.com>, <linux-mm@kvack.org>,
	<david@fromorbit.com>, <linux-trace-kernel@vger.kernel.org>,
	<linux-fsdevel@vger.kernel.org>, <songmuchun@bytedance.com>
Subject: Re: [PATCH RESEND v3 1/2] hugetlbfs: support tracepoint
Date: Sat, 7 Sep 2024 15:57:49 +0800	[thread overview]
Message-ID: <6a676ec5-1ac8-4974-9cee-4525bf8c70be@huawei.com> (raw)
In-Reply-To: <20240903155623.62615be8@gandalf.local.home>



On 2024/9/4 3:56, Steven Rostedt wrote:
> On Thu, 29 Aug 2024 14:41:09 +0800
> Hongbo Li <lihongbo22@huawei.com> wrote:
> 
>> Add basic tracepoints for {alloc, evict, free}_inode, setattr and
>> fallocate. These can help users to debug hugetlbfs more conveniently.
>>
>> Signed-off-by: Hongbo Li <lihongbo22@huawei.com>
> 
> Pretty basic trace events.
yeah, very basic. Thanks for reviewing!😄

Thanks,
Hongbo
> 
> Reviewed-by: Steven Rostedt (Google) <rostedt@goodmis.org>
> 
> -- Steve


  reply	other threads:[~2024-09-07  7:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-29  6:41 [PATCH RESEND v3 0/2] Introduce tracepoint for hugetlbfs Hongbo Li
2024-08-29  6:41 ` [PATCH RESEND v3 1/2] hugetlbfs: support tracepoint Hongbo Li
2024-09-03 19:56   ` Steven Rostedt
2024-09-07  7:57     ` Hongbo Li [this message]
2024-08-29  6:41 ` [PATCH RESEND v3 2/2] hugetlbfs: use tracepoints in hugetlbfs functions Hongbo Li
2024-09-14  8:09 ` [PATCH RESEND v3 0/2] Introduce tracepoint for hugetlbfs Hongbo Li
2024-09-17  9:08 ` Christian Brauner

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=6a676ec5-1ac8-4974-9cee-4525bf8c70be@huawei.com \
    --to=lihongbo22@huawei.com \
    --cc=david@fromorbit.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=muchun.song@linux.dev \
    --cc=rostedt@goodmis.org \
    --cc=songmuchun@bytedance.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox