From: Jens Axboe <axboe@kernel.dk>
To: Bart Van Assche <Bart.VanAssche@wdc.com>,
"tj@kernel.org" <tj@kernel.org>
Cc: "jthumshirn@suse.de" <jthumshirn@suse.de>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"hch@lst.de" <hch@lst.de>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"ming.lei@redhat.com" <ming.lei@redhat.com>,
"osandov@fb.com" <osandov@fb.com>,
"00moses.alexander00@gmail.com" <00moses.alexander00@gmail.com>,
"joseph.qi@linux.alibaba.com" <joseph.qi@linux.alibaba.com>
Subject: Re: [PATCH v5 1/3] blkcg: Introduce blkg_root_lookup()
Date: Thu, 9 Aug 2018 14:23:57 -0600 [thread overview]
Message-ID: <f51e9e5e-0f8c-c9bb-5318-c442ed242449@kernel.dk> (raw)
In-Reply-To: <794ba3894d7099fa7a855d3eb4d51c30faecd248.camel@wdc.com>
On 8/9/18 2:17 PM, Bart Van Assche wrote:
> On Thu, 2018-08-09 at 12:56 -0700, Tejun Heo wrote:
>> Hello,
>>
>> On Thu, Aug 09, 2018 at 07:53:36AM -0700, Bart Van Assche wrote:
>>> +/**
>>> + * blkg_lookup - look up blkg for the specified request queue
>>> + * @q: request_queue of interest
>>> + *
>>> + * Lookup blkg for @q at the root level. See also blkg_lookup().
>>> + */
>>> +static inline struct blkcg_gq *blkg_root_lookup(struct request_queue *q)
>>> +{
>>> + struct blkcg_gq *blkg;
>>> +
>>> + rcu_read_lock();
>>> + blkg = blkg_lookup(&blkcg_root, q);
>>> + rcu_read_unlock();
>>> +
>>> + return blkg;
>>> +}
>>
>> So, root blkg is always available as long as the request_queue is
>> alive. Sth like the following would be simpler?
>>
>> static inline struct blkcg_gq *blk_queue_root_blkg(struct request_queue *q)
>> {
>> return q->root_blkg;
>> }
>
> That would not only be simpler, it would also avoid that blk_queue_root_blkg()
> returns NULL if bypass mode is enabled and the request queue is still associated
> with the block cgroup controller. How do you want to proceed with this change?
Do a followup patch?
--
Jens Axboe
next prev parent reply other threads:[~2018-08-09 22:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180809145338.6160-1-bart.vanassche@wdc.com>
2018-08-09 14:53 ` [PATCH v5 1/3] blkcg: Introduce blkg_root_lookup() Bart Van Assche
2018-08-09 19:56 ` Tejun Heo
2018-08-09 20:17 ` Bart Van Assche
2018-08-09 20:23 ` Jens Axboe [this message]
2018-08-09 14:53 ` [PATCH v5 2/3] block: Introduce blk_exit_queue() Bart Van Assche
2018-08-09 14:53 ` [PATCH v5 3/3] block: Ensure that a request queue is dissociated from the cgroup controller Bart Van Assche
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=f51e9e5e-0f8c-c9bb-5318-c442ed242449@kernel.dk \
--to=axboe@kernel.dk \
--cc=00moses.alexander00@gmail.com \
--cc=Bart.VanAssche@wdc.com \
--cc=hch@lst.de \
--cc=joseph.qi@linux.alibaba.com \
--cc=jthumshirn@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=osandov@fb.com \
--cc=stable@vger.kernel.org \
--cc=tj@kernel.org \
/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