From: Weijie Yuan <wy@wyuan.org>
To: "zhen.ni" <zhen.ni@easystack.cn>
Cc: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
Lorenzo Stoakes <ljs@kernel.org>,
"Liam R . Howlett" <liam@infradead.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>, Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Brendan Jackman <brendan.jackman@linux.dev>,
Johannes Weiner <hannes@cmpxchg.org>, Zi Yan <ziy@nvidia.com>,
linux-mm@kvack.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH v2 0/8] mm/page_owner: Add PID/TGID/COMM and cgroup filtering
Date: Tue, 8 Sep 2026 15:04:02 +0800 [thread overview]
Message-ID: <ap-zYt-1qCBGKZed@wyuan.org> (raw)
In-Reply-To: <048d7470-a813-4252-a4f0-0ec29694f639@easystack.cn>
On Tue, Sep 08, 2026 at 02:40:10PM +0800, zhen.ni wrote:
>
>
> 在 2026/9/8 14:24, Weijie Yuan 写道:
> > From an outsider..
> >
> > On Tue, Sep 08, 2026 at 10:41:23AM +0800, zhen.ni wrote:
> > > >
> > > > Sorry but your whole reply reads like a LLM slop. It took a lot of
> > > > mental effor to actually try and engage with it.
> > > >
> > >
> > > This reply was written by me, and its viewpoints are not simply copied
> > > directly from an LLM. The LLM only assists with the wording.
> >
> > So that's probably the reason. Your previous replies was indeed very
> > much like the output of an LLM. Even if the idea is your own, after
> > being "polished" by LLM, it's hard to read. I know English is not our
> > first language, and it's not that easy to speak like a native speaker.
> > But may I ask you did you read it before sending them out? I really
> > found this bunch of overly formal content a little painful to read.
> >
> > So I suspect the LLM may have taken too much liberty in polishing your
> > text, to the point that your replies no longer read like something a
> > person would naturally write.
> >
> > The "Summary and Plan" in your reply in v1, both in its formatting and
> > wording, looks quite similar to LLM-generated text to me. So I can
> > understand why Lorenzo asked whether you had used an LLM. Come on, we
> > all know what LLM writing looks like.
> >
> > That said, I do not know exactly how you used the LLM on your original
> > text, so please forgive me if I have this wrong.
> >
> > Thanks.
> >
> I really can't distinguish the LLM flavor that clearly in English.
Yes, sometimes I can not as well. But I guess the native ones can.
So.. ;-)
> I'm sorry for causing some trouble.
That's fine. No need to say sorry.
I know and understand that we non-native speakers would rather not make
mistakes over these little language detail issues. But over-polishing
can end up having the opposite effect. Keeping some of your natural
writing style may actually be what the community prefers, especially
these AI days.
> My normal reply process is to first describe my ideas, then have the
> LLM check for logic and grammar issues, and do a round of polishing. I
> check the final draft once more to see if it has deviated from my
> ideas, and make corresponding revisions.
Sigh, so it is hard to know where to draw the line. Write more and learn
more about "human-like" writing, perhaps. :)
Thanks!
next prev parent reply other threads:[~2026-09-08 7:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 4:18 [PATCH v2 0/8] mm/page_owner: Add PID/TGID/COMM and cgroup filtering Zhen Ni
2026-09-03 4:18 ` [PATCH v2 1/8] mm/page_owner: Add PID filtering support Zhen Ni
2026-09-03 4:18 ` [PATCH v2 2/8] mm/page_owner: Add TGID " Zhen Ni
2026-09-03 4:18 ` [PATCH v2 3/8] mm/page_owner: Add COMM filtering with wildcard support Zhen Ni
2026-09-03 4:18 ` [PATCH v2 4/8] mm/page_owner: Refactor memcg handling for cgroup filter support Zhen Ni
2026-09-03 4:18 ` [PATCH v2 5/8] mm/page_owner: Add memcg " Zhen Ni
2026-09-03 4:18 ` [PATCH v2 6/8] tools/mm: Add PID/TGID/COMM filtering support to page_owner_filter Zhen Ni
2026-09-03 4:18 ` [PATCH v2 7/8] tools/mm: Add memory cgroup " Zhen Ni
2026-09-03 4:18 ` [PATCH v2 8/8] Documentation: page_owner: Document PID/TGID/COMM and cgroup filters Zhen Ni
[not found] ` <20260902221225.228fb4b18e115ba55b29fe29@linux-foundation.org>
2026-09-03 12:00 ` [PATCH v2 0/8] mm/page_owner: Add PID/TGID/COMM and cgroup filtering zhen.ni
2026-09-04 8:25 ` Vlastimil Babka (SUSE)
2026-09-07 4:08 ` zhen.ni
2026-09-07 15:21 ` Vlastimil Babka (SUSE)
2026-09-08 2:41 ` zhen.ni
2026-09-08 6:24 ` Weijie Yuan
2026-09-08 6:40 ` zhen.ni
2026-09-08 7:04 ` Weijie Yuan [this message]
2026-09-08 9:13 ` Lorenzo Stoakes (ARM)
2026-09-08 11:18 ` zhen.ni
2026-09-08 17:37 ` Weijie Yuan
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=ap-zYt-1qCBGKZed@wyuan.org \
--to=wy@wyuan.org \
--cc=akpm@linux-foundation.org \
--cc=brendan.jackman@linux.dev \
--cc=corbet@lwn.net \
--cc=david@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=liam@infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=zhen.ni@easystack.cn \
--cc=ziy@nvidia.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