From: Tejun Heo <tj@kernel.org>
To: qiang.zhang@windriver.com
Cc: jiangshanlai@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] workqueue: replace call_rcu with kfree_rcu
Date: Mon, 26 Oct 2020 09:41:14 -0400 [thread overview]
Message-ID: <20201026134010.GA73258@mtj.duckdns.org> (raw)
In-Reply-To: <20201014083145.16959-1-qiang.zhang@windriver.com>
On Wed, Oct 14, 2020 at 04:31:45PM +0800, qiang.zhang@windriver.com wrote:
> diff --git a/kernel/workqueue.c b/kernel/workqueue.c
> index ac088ce6059b..8d4fe649631a 100644
> --- a/kernel/workqueue.c
> +++ b/kernel/workqueue.c
> @@ -3653,11 +3653,6 @@ static struct worker_pool *get_unbound_pool(const struct workqueue_attrs *attrs)
> return NULL;
> }
>
> -static void rcu_free_pwq(struct rcu_head *rcu)
> -{
> - kmem_cache_free(pwq_cache,
> - container_of(rcu, struct pool_workqueue, rcu));
> -}
>
> /*
> * Scheduled on system_wq by put_pwq() when an unbound pwq hits zero refcnt
> @@ -3683,7 +3678,7 @@ static void pwq_unbound_release_workfn(struct work_struct *work)
> put_unbound_pool(pool);
> mutex_unlock(&wq_pool_mutex);
>
> - call_rcu(&pwq->rcu, rcu_free_pwq);
> + kfree_rcu(pwq, rcu);
kfree_rcu() eventually calls kfree() which is different from
kmem_cache_free(). It can only be used for kmalloc'd areas, not
kmem_cache_alloc'd ones.
Thanks.
--
tejun
next prev parent reply other threads:[~2020-10-26 13:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 8:31 qiang.zhang
2020-10-26 13:41 ` Tejun Heo [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-10-14 8:20 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=20201026134010.GA73258@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=qiang.zhang@windriver.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
all inboxes | Powered by JetHome®