linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Zhongkun He <hezhongkun.hzk@bytedance.com>
To: Michal Hocko <mhocko@suse.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	wuyun.abel@bytedance.com
Subject: Re: [External] Re: [PATCH 0/3] mm: replace atomic_t with percpu_ref in mempolicy.
Date: Sun, 15 Jan 2023 00:52:26 +0800	[thread overview]
Message-ID: <d1f71b24-2e50-341f-93f8-e3ed9b2dd412@bytedance.com> (raw)
In-Reply-To: <Y8GPCT2w0WKARLVF@dhcp22.suse.cz>

> On Mon 05-12-22 00:14:29, Zhongkun He wrote:
> [...]
>> +/* Obtain a reference on the specified mpol */
>>   static inline void mpol_get(struct mempolicy *pol)
>>   {
>>   	if (pol)
> 
> Shouldn't this be mpol_needs_cond_ref?
> 
>> -		atomic_inc(&pol->refcnt);
>> +		percpu_ref_get(&pol->refcnt);
>> +}
>> +
>> +static inline bool mpol_tryget(struct mempolicy *pol)
>> +{
>> +	return pol && percpu_ref_tryget(&pol->refcnt);
>>   }
>>   
>> +/*
>> + * This function initiates destruction of mempolicy.
> 
> This is not a useful comment. It would be much more helpful to say when
> this should be called.
> 
>> + */
>> +static inline void mpol_kill(struct mempolicy *pol)
>> +{
>> +        if (pol)
>> +                percpu_ref_kill(&pol->refcnt);
>> +}
>> +
>> +
>>   extern bool __mpol_equal(struct mempolicy *a, struct mempolicy *b);
>>   static inline bool mpol_equal(struct mempolicy *a, struct mempolicy *b)
>>   {
>> @@ -197,11 +210,15 @@ static inline void mpol_put(struct mempolicy *p)
>>   {
>>   }
>>   
>> -static inline void mpol_cond_put(struct mempolicy *pol)
>> +static inline void mpol_get(struct mempolicy *pol)
>>   {
>>   }
>>   
>> -static inline void mpol_get(struct mempolicy *pol)
>> +static inline bool mpol_tryget(struct mempolicy *pol)
>> +{
>> +}
> 
> This should return false, right?
> 
> [...]
>> +/* Obtain a reference on the specified task mempolicy */
> 
> Again, this is pretty much clear from the name. It would be more useful
> to explain how the pointer can be used - e.g. needs to call mpol_put
> or mpol_kill depending on the calling context.
> 
>> +static mempolicy *get_task_mpol(struct task_struct *p)
>> +{
>> +	struct mempolicy *pol;
>> +
>> +	rcu_read_lock();
>> +	pol = rcu_dereference(p->mempolicy);
>> +
>> +	if (!pol || mpol_tryget(pol))
> 
> Shouldn't be !mpol_tryget?
> 
>> +		pol = NULL;
>> +	rcu_read_unlock();
>> +
>> +	return pol;
>> +}
>> +
> 
> I do not see any rcu_assign_pointer for the newly created policy so this
> seems incomplete. Ditto no mpol_kill calls. I am unlikely to get into
> follow up patches now. Please split up the work so that it is reviewable
> more easily and then I can have a further look.
> 
> Thanks!

Thanks for your review, some changes may be in other patch,i will
reorganize the patches according to the suggestions to make
things clear.

Thanks.



      reply	other threads:[~2023-01-14 16:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-04 16:14 Zhongkun He
2022-12-04 16:14 ` [PATCH 1/3] mm: replace mpol_put() with mpol_kill() initiated the destruction of mpol Zhongkun He
2022-12-04 16:14 ` [PATCH 2/3] mm: fix the reference of mempolicy in some functions Zhongkun He
2022-12-04 16:14 ` [PATCH 3/3] mm: add __rcu symbol for task->mempolicy Zhongkun He
2022-12-04 18:25 ` [PATCH 0/3] mm: replace atomic_t with percpu_ref in mempolicy kernel test robot
2023-01-13 16:20 ` Michal Hocko
2023-01-13 16:22   ` Michal Hocko
2023-01-14 16:10     ` [External] " Zhongkun He
2023-01-13 17:04 ` Michal Hocko
2023-01-14 16:52   ` Zhongkun He [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=d1f71b24-2e50-341f-93f8-e3ed9b2dd412@bytedance.com \
    --to=hezhongkun.hzk@bytedance.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=wuyun.abel@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