mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Waiman Long <longman@redhat.com>
To: "Zhang, Qiang" <Qiang.Zhang@windriver.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"mingo@kernel.org" <mingo@kernel.org>,
	"elver@google.com" <elver@google.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 回复: [PATCH v3] debugobjects: install CPU hotplug callback
Date: Wed, 9 Sep 2020 22:50:27 -0400	[thread overview]
Message-ID: <fc7702c8-6d85-66ee-3220-8c1a3e9acf0b@redhat.com> (raw)
In-Reply-To: <BYAPR11MB26324FE54B890DD73417F6B8FF270@BYAPR11MB2632.namprd11.prod.outlook.com>

On 9/9/20 9:48 PM, Zhang, Qiang wrote:
>
> ________________________________________
> 发件人: Waiman Long <longman@redhat.com>
> 发送时间: 2020年9月9日 2:23
> 收件人: Zhang, Qiang; tglx@linutronix.de; mingo@kernel.org; elver@google.com
> 抄送: linux-kernel@vger.kernel.org
> 主题: Re: [PATCH v3] debugobjects: install CPU hotplug callback
>
> On 9/8/20 2:27 AM, qiang.zhang@windriver.com wrote:
>> From: Zqiang <qiang.zhang@windriver.com>
>>
>> Due to CPU hotplug, it may never be online after it's offline,
>> some objects in percpu pool is never free. in order to avoid
>> this happening, install CPU hotplug callback, call this callback
>> func to free objects in percpu pool when CPU going offline.
>>
>> Signed-off-by: Zqiang <qiang.zhang@windriver.com>
>> ---
>>    v1->v2:
>>    Modify submission information.
>>
>>    v2->v3:
>>    In CPU hotplug callback func, add clear percpu pool "obj_free" operation.
>>    capitalize 'CPU', and use shorter preprocessor sequence.
>>
>>    include/linux/cpuhotplug.h |  1 +
>>    lib/debugobjects.c         | 24 ++++++++++++++++++++++++
>>    2 files changed, 25 insertions(+)
>>
>> diff --git a/include/linux/cpuhotplug.h b/include/linux/cpuhotplug.h
>> index 3215023d4852..0c39d57e5342 100644
>> --- a/include/linux/cpuhotplug.h
>> +++ b/include/linux/cpuhotplug.h
>> @@ -36,6 +36,7 @@ enum cpuhp_state {
>>        CPUHP_X86_MCE_DEAD,
>>        CPUHP_VIRT_NET_DEAD,
>>        CPUHP_SLUB_DEAD,
>> +     CPUHP_DEBUG_OBJ_DEAD,
>>        CPUHP_MM_WRITEBACK_DEAD,
>>        CPUHP_MM_VMSTAT_DEAD,
>>        CPUHP_SOFTIRQ_DEAD,
>> diff --git a/lib/debugobjects.c b/lib/debugobjects.c
>> index fe4557955d97..bb69a02c3e7b 100644
>> --- a/lib/debugobjects.c
>> +++ b/lib/debugobjects.c
>> @@ -19,6 +19,7 @@
>>    #include <linux/slab.h>
>>    #include <linux/hash.h>
>>    #include <linux/kmemleak.h>
>> +#include <linux/cpu.h>
>>
>>    #define ODEBUG_HASH_BITS    14
>>    #define ODEBUG_HASH_SIZE    (1 << ODEBUG_HASH_BITS)
>> @@ -433,6 +434,24 @@ static void free_object(struct debug_obj *obj)
>>        }
>>    }
>>
>> +#ifdef CONFIG_HOTPLUG_CPU
>> +static int object_cpu_offline(unsigned int cpu)
>> +{
>> +     struct debug_percpu_free *percpu_pool;
>> +     struct hlist_node *tmp;
>> +     struct debug_obj *obj;
>> +
>> +     percpu_pool = per_cpu_ptr(&percpu_obj_pool, cpu);
>> +     hlist_for_each_entry_safe(obj, tmp, &percpu_pool->free_objs, node) {
>> +             hlist_del(&obj->node);
>> +             kmem_cache_free(obj_cache, obj);
>> +     }
>> +     percpu_pool->obj_free = 0;
>>> For pointer, it is better to use NULL for clarity.
>>> Cheers,
>>> Longman
> Do you mean "->obj_free" variable ?   this represents the number of free objects in  percpu_pool .
>
You are right. I got confused. Sorry for the noise.

Cheers,
Longman


  reply	other threads:[~2020-09-10  2:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-08  6:27 qiang.zhang
2020-09-08 18:23 ` Waiman Long
2020-09-10  1:48   ` 回复: " Zhang, Qiang
2020-09-10  2:50     ` Waiman Long [this message]
2020-09-16  6:00       ` 回复: " Zhang, Qiang
2020-10-01 14:40 ` [tip: core/debugobjects] debugobjects: Free per CPU pool after CPU unplug tip-bot2 for Zqiang

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=fc7702c8-6d85-66ee-3220-8c1a3e9acf0b@redhat.com \
    --to=longman@redhat.com \
    --cc=Qiang.Zhang@windriver.com \
    --cc=elver@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®