mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Daniel Vacek <neelx@redhat.com>
Cc: Waiman Long <longman@redhat.com>,
	Zefan Li <lizefan.x@bytedance.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	cgroups@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cgroup/cpuset: no need to explicitly init a global static variable
Date: Wed, 4 Jan 2023 12:21:54 -1000	[thread overview]
Message-ID: <Y7X8Asv25sntht6t@slm.duckdns.org> (raw)
In-Reply-To: <20221220151415.856093-1-neelx@redhat.com>

On Tue, Dec 20, 2022 at 04:14:15PM +0100, Daniel Vacek wrote:
> cpuset_rwsem is a static variable. It's initialized at build time and so
> there's no need for explicit runtime init leaking one percpu int.
> 
> Signed-off-by: Daniel Vacek <neelx@redhat.com>

Applied to cgroup/for-6.2-fixes with the following description:

    cgroup/cpuset: no need to explicitly init a global static variable
    
    cpuset_rwsem is a static variable defined with DEFINE_STATIC_PERCPU_RWSEM().
    It's initialized at build time and so there's no need for explicit runtime
    init leaking one percpu int.
    
    Signed-off-by: Daniel Vacek <neelx@redhat.com>
    Reviewed-by: Aaron Tomlin <atomlin@atomlin.com>
    Acked-by: Mukesh Ojha <quic_mojha@quicinc.com>
    Signed-off-by: Tejun Heo <tj@kernel.org>

Thanks.

-- 
tejun

      parent reply	other threads:[~2023-01-04 22:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-20 15:14 Daniel Vacek
2022-12-20 16:59 ` Waiman Long
2022-12-21  8:49   ` Daniel Vacek
2022-12-20 17:32 ` Aaron Tomlin
2022-12-21  6:19 ` Mukesh Ojha
2023-01-04 22:21 ` Tejun Heo [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=Y7X8Asv25sntht6t@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan.x@bytedance.com \
    --cc=longman@redhat.com \
    --cc=neelx@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
all inboxes | Powered by JetHome®