mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
	linux-kernel@vger.kernel.org, Li Zefan <lizefan@huawei.com>,
	cgroups@vger.kernel.org
Subject: Re: [PATCH RFC] blkcg: prepare blkcg knobs for default hierarchy
Date: Wed, 23 Apr 2014 13:01:41 -0400	[thread overview]
Message-ID: <20140423170141.GJ4781@htj.dyndns.org> (raw)
In-Reply-To: <20140415141826.GB17018@redhat.com>

On Tue, Apr 15, 2014 at 10:18:26AM -0400, Vivek Goyal wrote:
> Ok, that's fine. Let us just document the knobs well so that people can
> find which knob is giving what information and make cfq names better at
> the expense of inconsistency of names with throttling layer.

I've been thinking about it more.  Why do we even have separate stats
for common things like bytes transferred?  It doesn't serve any
purpose to do double accounting and reporting on everything, does it?
Shouldn't we just have single set of common stats for things like
requests / bytes serviced?

Thanks.

-- 
tejun

  reply	other threads:[~2014-04-23 17:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-13  1:32 Tejun Heo
2014-04-14 18:08 ` Vivek Goyal
2014-04-14 19:32   ` Tejun Heo
2014-04-15 13:53     ` Vivek Goyal
2014-04-15 14:06       ` Tejun Heo
2014-04-15 14:18         ` Vivek Goyal
2014-04-23 17:01           ` Tejun Heo [this message]
2014-04-23 17:17             ` Vivek Goyal
2014-04-23 18:52               ` Tejun Heo
2014-04-23 18:58                 ` Vivek Goyal
2014-04-23 19:00                   ` Tejun Heo
2014-04-23 19:21                     ` Vivek Goyal
2014-04-23 19:27                       ` Tejun Heo
2014-05-23 17:39                       ` Tejun Heo
2014-05-27 12:49                         ` Vivek Goyal

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=20140423170141.GJ4781@htj.dyndns.org \
    --to=tj@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=cgroups@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=vgoyal@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®