All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolay Borisov <kernel-6AxghH7DbtA@public.gmane.org>
To: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	SiteGround Operations
	<operations-/eCPMmvKun9pLGFMi4vTTA@public.gmane.org>
Subject: Re: blkcg throttle settings page cache writes
Date: Tue, 27 Sep 2016 14:28:25 +0300	[thread overview]
Message-ID: <57EA57D9.6000104@kyup.com> (raw)
In-Reply-To: <20160916155736.GC26371-piEFEHQLUPpN0TnZuCh8vA@public.gmane.org>



On 09/16/2016 06:57 PM, Tejun Heo wrote:
> Hello,
> 
> On Wed, Sep 14, 2016 at 11:25:49AM +0300, Nikolay Borisov wrote:
>> Hello,
>> So Tejun, my question is what is the problem for the blkcg information
>> to be transferred alongside the bio (which I believed to be happening
>> with the blkcg_association calls) so that even buffered writes are
>> throttled via the cgroup policies? Or are the numbers I'm seeing in
>> iostat actually the writes to the page-cache and not the underlying
>> block device?
> 
> You gotta use cgroup v2 for that.  Controlling buffered writes
> requires coordination between memory and io controllers which isn't
> possible with cgroup v1.

Thanks for the information Tejun, that makes sense. However, in my
testing I observed that when a throttle limit is set on IOPS it's not
being enforced for buffered writes, but when it's set on bps it is
actually working as expected. Is this expected or are there conflating
factors which I'm not taking into account and as such what I'm seeing -
iostat reports perfect utilisation of a particular device according to
the bps throttle limit.


> 
> Thanks.
> 

  parent reply	other threads:[~2016-09-27 11:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14  8:25 blkcg throttle settings page cache writes Nikolay Borisov
     [not found] ` <57D9098D.3020403-6AxghH7DbtA@public.gmane.org>
2016-09-16 15:57   ` Tejun Heo
     [not found]     ` <20160916155736.GC26371-piEFEHQLUPpN0TnZuCh8vA@public.gmane.org>
2016-09-27 11:28       ` Nikolay Borisov [this message]
     [not found]         ` <57EA57D9.6000104-6AxghH7DbtA@public.gmane.org>
2016-09-27 23:22           ` 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=57EA57D9.6000104@kyup.com \
    --to=kernel-6axghh7dbta@public.gmane.org \
    --cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=operations-/eCPMmvKun9pLGFMi4vTTA@public.gmane.org \
    --cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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.