From: Thomas Gleixner <tglx@linutronix.de>
To: "Zhang\, Qiang" <Qiang.Zhang@windriver.com>,
Waiman Long <longman@redhat.com>,
"elver\@google.com" <elver@google.com>
Cc: "linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"akpm\@linux-foundation.org" <akpm@linux-foundation.org>
Subject: Re: 回复: 回复: [PATCH] debugobjects: install cpu hotplug callback
Date: Wed, 26 Aug 2020 11:41:36 +0200 [thread overview]
Message-ID: <874kopwxpr.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <BYAPR11MB2632ABDD5A8334F74B4F539AFF540@BYAPR11MB2632.namprd11.prod.outlook.com>
On Wed, Aug 26 2020 at 08:34, Qiang Zhang wrote:
> ________________________________________
> 发件人: linux-kernel-owner@vger.kernel.org <linux-kernel-owner@vger.kernel.org> 代表 Thomas Gleixner <tglx@linutronix.de>
> 发送时间: 2020年8月26日 7:53
> 收件人: Waiman Long; Zhang, Qiang; elver@google.com
> 抄送: linux-kernel@vger.kernel.org; akpm@linux-foundation.org
> 主题: Re: 回复: [PATCH] debugobjects: install cpu hotplug callback
Can you please fix your mail client not to copy the headers into the
mail body? The headers are already in the mail itself.
> On Tue, Aug 25 2020 at 18:26, Waiman Long wrote:
Something like this is completely sufficient.
>>That's a really good question nevertheless. The only case where this
>>ever matters is physical hotplug. All other CPU hotplug stuff is
>>temporarily or in case of a late (post boottime) SMT disable it's going
>>to be a handful of free objects on that pool. As debugobjects is as the
>>name says a debug facility the benefit is questionable unless there is a
>>good reason to do so.
>
> I don't know there may not be too many objects in the percpu pool,
> but that doesn't mean they no need to be free, a CPU may never be
> online after it is offline. some objects in percpu pool is never
> free.
And this matters because? Because your fully debug enabled kernel will
have an uptime of years after disabling the CPU?
That said, I'm not opposed against this patch, but
'we should free objects'
is not a convincing technical argument for doing this. If we want to
have that then please add proper technical arguments to the changelog.
Thanks,
tglx
prev parent reply other threads:[~2020-08-26 9:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-20 3:24 [PATCH] debugobjects: install cpu hotplug callback qiang.zhang
2020-08-25 4:53 ` 回复: " Zhang, Qiang
2020-08-25 22:26 ` Waiman Long
2020-08-25 23:32 ` Waiman Long
2020-08-25 23:53 ` Thomas Gleixner
2020-08-26 0:48 ` Waiman Long
2020-08-26 8:34 ` 回复: " Zhang, Qiang
2020-08-26 9:41 ` Thomas Gleixner [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=874kopwxpr.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=Qiang.Zhang@windriver.com \
--cc=akpm@linux-foundation.org \
--cc=elver@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.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