From: Vivek Goyal <vgoyal@redhat.com>
To: Tejun Heo <tj@kernel.org>
Cc: axboe@kernel.dk, ctalbott@google.com, rni@google.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 12/12] blkcg: kill the mind-bending blkg->dev
Date: Thu, 19 Jan 2012 11:46:41 -0500 [thread overview]
Message-ID: <20120119164641.GA15561@redhat.com> (raw)
In-Reply-To: <20120119163056.GH5198@google.com>
On Thu, Jan 19, 2012 at 08:30:56AM -0800, Tejun Heo wrote:
> Hello,
>
> On Thu, Jan 19, 2012 at 10:49:19AM -0500, Vivek Goyal wrote:
> > > Let stat and conf read functions get device name from
> > > blkg->q->backing_dev_info.dev and pass it down to printing functions
> > > and remove blkg->dev.
> >
> > I think one of the reasons for not using blkg->q->backing_dev_info.dev was
> > that there were still drivers where multiple gendisks were sharing the
> > request queue.
>
> Hmmm... is that relevant? The configurations / stats are per
> cgroup-request_queue pair. How does multiple genhd's sharing a queue
> make any difference? Also, the fill_dev_details functions were using
> the same q->backing_dev_info to fill it in, so it's not like it was
> using anything different.
You are right. Looks like it should not make any difference. Also looks
like bdi->dev points to first disk on the queue and ignores later ones.
int bdi_register(struct backing_dev_info *bdi, struct device *parent,
const char *fmt, ...)
{
if (bdi->dev) /* The driver needs to use separate queues per
device */
return 0;
}
So if a queue is being shared by multiple disks, then any throttling rule
on the device will practically trated a rule on the queue and will be
effective on all the devices cumulatively. So sounds fine.
Thanks
Vivek
next prev parent reply other threads:[~2012-01-19 16:46 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 1:11 [PATCHSET] blkcg: kill policy node and blkg->dev Tejun Heo
2012-01-19 1:11 ` [PATCH 01/12] blkcg: obtaining blkg should be enclosed inside rcu_read_lock() Tejun Heo
2012-01-19 10:07 ` Vivek Goyal
2012-01-19 15:39 ` Tejun Heo
2012-01-19 15:54 ` Vivek Goyal
2012-01-19 15:58 ` Tejun Heo
2012-01-19 1:11 ` [PATCH 02/12] cfq: don't register propio policy if !CONFIG_CFQ_GROUP_IOSCHED Tejun Heo
2012-01-19 10:11 ` Vivek Goyal
2012-01-19 1:11 ` [PATCH 03/12] elevator: clear auxiliary data earlier during elevator switch Tejun Heo
2012-01-19 1:11 ` [PATCH 04/12] elevator: make elevator_init_fn() return 0/-errno Tejun Heo
2012-01-19 11:11 ` Vivek Goyal
2012-01-19 15:44 ` Tejun Heo
2012-01-19 1:11 ` [PATCH 05/12] blkcg: update blkg get functions take blkio_cgroup as parameter Tejun Heo
2012-01-19 11:21 ` Vivek Goyal
2012-01-19 15:45 ` Tejun Heo
2012-01-19 1:11 ` [PATCH 06/12] blkcg: use q and plid instead of opaque void * for blkio_group association Tejun Heo
2012-01-19 14:04 ` Vivek Goyal
2012-01-19 15:55 ` Tejun Heo
2012-01-19 16:16 ` Vivek Goyal
2012-01-19 16:25 ` Tejun Heo
2012-01-19 16:42 ` Tejun Heo
2012-01-19 1:11 ` [PATCH 07/12] blkcg: add blkio_policy[] array and allow one policy per policy ID Tejun Heo
2012-01-19 1:11 ` [PATCH 08/12] blkcg: use the usual get blkg path for root blkio_group Tejun Heo
2012-01-19 14:41 ` Vivek Goyal
2012-01-19 16:17 ` Tejun Heo
2012-01-19 1:11 ` [PATCH 09/12] blkcg: factor out blkio_group creation Tejun Heo
2012-01-19 1:11 ` [PATCH 10/12] blkcg: don't allow or retain configuration of missing devices Tejun Heo
2012-01-19 1:11 ` [PATCH 11/12] blkcg: kill blkio_policy_node Tejun Heo
2012-01-19 20:32 ` Vivek Goyal
2012-01-19 22:03 ` Tejun Heo
2012-01-19 22:30 ` Vivek Goyal
2012-01-19 1:11 ` [PATCH 12/12] blkcg: kill the mind-bending blkg->dev Tejun Heo
2012-01-19 15:49 ` Vivek Goyal
2012-01-19 16:30 ` Tejun Heo
2012-01-19 16:46 ` Vivek Goyal [this message]
2012-01-19 1:18 ` [PATCHSET] blkcg: kill policy node and blkg->dev Tejun Heo
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=20120119164641.GA15561@redhat.com \
--to=vgoyal@redhat.com \
--cc=axboe@kernel.dk \
--cc=ctalbott@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rni@google.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.