From: Yonghong Song <yhs@meta.com>
To: Rong Tao <rtoax@foxmail.com>, vbabka@suse.cz
Cc: 42.hyeyoo@gmail.com, akpm@linux-foundation.org, cl@linux.com,
iamjoonsoo.kim@lge.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, penberg@kernel.org, rientjes@google.com,
roman.gushchin@linux.dev, rongtao@cestc.cn, sdf@google.com,
yhs@fb.com
Subject: Re: [PATCH] mm: Functions used internally should not be put into
Date: Sat, 21 Jan 2023 12:34:06 -0800 [thread overview]
Message-ID: <9b556b3d-538e-733b-7525-57a78012d3bf@meta.com> (raw)
In-Reply-To: <tencent_6BA336883F064B42805919971C2AC6AFF508@qq.com>
On 1/17/23 11:23 PM, Rong Tao wrote:
> Hi, Vlastimil.
>
> Thank you for your reply. Indeed, BTF can eliminate the existing problem
> of data structure parsing. But as far as the current BCC[0] code is
> concerned, more surgery may be required.
>
> Now the bcc problem[1] should probably be solved by the bcc itself using
> BTF, and should not bother the kernel. I hope the maintenance engineers
> at BCC can agree with this. Thanks again.
>
> [0] https://github.com/iovisor/bcc
> [1] https://github.com/iovisor/bcc/issues/4438
Rong, I have added a comment in above [1]. Let us try to resolve
this issue inside the bcc. Thanks!
>
> Best wishes.
>
> Rong Tao
prev parent reply other threads:[~2023-01-21 20:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 8:50 [PATCH] mm: Functions used internally should not be put into slub_def.h Rong Tao
2023-01-16 11:59 ` Hyeonggon Yoo
2023-01-17 2:01 ` [PATCH] mm: Functions used internally should not be put into Rong Tao
2023-01-17 12:57 ` Vlastimil Babka
2023-01-18 7:23 ` Rong Tao
2023-01-21 20:34 ` Yonghong Song [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=9b556b3d-538e-733b-7525-57a78012d3bf@meta.com \
--to=yhs@meta.com \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=rongtao@cestc.cn \
--cc=rtoax@foxmail.com \
--cc=sdf@google.com \
--cc=vbabka@suse.cz \
--cc=yhs@fb.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