From: Josef Bacik <josef@toxicpanda.com>
To: Andrea Righi <andrea.righi@canonical.com>
Cc: Josef Bacik <josef@toxicpanda.com>, Tejun Heo <tj@kernel.org>,
Li Zefan <lizefan@huawei.com>,
Paolo Valente <paolo.valente@linaro.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Jens Axboe <axboe@kernel.dk>, Vivek Goyal <vgoyal@redhat.com>,
Dennis Zhou <dennis@kernel.org>,
cgroups@vger.kernel.org, linux-block@vger.kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] blkcg: implement sync() isolation
Date: Thu, 7 Mar 2019 17:07:01 -0500 [thread overview]
Message-ID: <20190307220659.5qmye2pxmto7nlei@macbook-pro-91.dhcp.thefacebook.com> (raw)
In-Reply-To: <20190307180834.22008-4-andrea.righi@canonical.com>
On Thu, Mar 07, 2019 at 07:08:34PM +0100, Andrea Righi wrote:
> Keep track of the inodes that have been dirtied by each blkcg cgroup and
> make sure that a blkcg issuing a sync() can trigger the writeback + wait
> of only those pages that belong to the cgroup itself.
>
> This behavior is applied only when io.sync_isolation is enabled in the
> cgroup, otherwise the old behavior is applied: sync() triggers the
> writeback of any dirty page.
>
> Signed-off-by: Andrea Righi <andrea.righi@canonical.com>
> ---
> block/blk-cgroup.c | 47 ++++++++++++++++++++++++++++++++++
> fs/fs-writeback.c | 52 +++++++++++++++++++++++++++++++++++---
> fs/inode.c | 1 +
> include/linux/blk-cgroup.h | 22 ++++++++++++++++
> include/linux/fs.h | 4 +++
> mm/page-writeback.c | 1 +
> 6 files changed, 124 insertions(+), 3 deletions(-)
>
> diff --git a/block/blk-cgroup.c b/block/blk-cgroup.c
> index 4305e78d1bb2..7d3b26ba4575 100644
> --- a/block/blk-cgroup.c
> +++ b/block/blk-cgroup.c
> @@ -1480,6 +1480,53 @@ void blkcg_stop_wb_wait_on_bdi(struct backing_dev_info *bdi)
> spin_unlock(&blkcg_wb_sleeper_lock);
> rcu_read_unlock();
> }
> +
> +/**
> + * blkcg_set_mapping_dirty - set owner of a dirty mapping
> + * @mapping: target address space
> + *
> + * Set the current blkcg as the owner of the address space @mapping (the first
> + * blkcg that dirties @mapping becomes the owner).
> + */
> +void blkcg_set_mapping_dirty(struct address_space *mapping)
> +{
> + struct blkcg *curr_blkcg, *blkcg;
> +
> + if (mapping_tagged(mapping, PAGECACHE_TAG_WRITEBACK) ||
> + mapping_tagged(mapping, PAGECACHE_TAG_DIRTY))
> + return;
> +
> + rcu_read_lock();
> + curr_blkcg = blkcg_from_current();
> + blkcg = blkcg_from_mapping(mapping);
> + if (curr_blkcg != blkcg) {
> + if (blkcg)
> + css_put(&blkcg->css);
> + css_get(&curr_blkcg->css);
> + rcu_assign_pointer(mapping->i_blkcg, curr_blkcg);
> + }
> + rcu_read_unlock();
> +}
> +
> +/**
> + * blkcg_set_mapping_clean - clear the owner of a dirty mapping
> + * @mapping: target address space
> + *
> + * Unset the owner of @mapping when it becomes clean.
> + */
> +
> +void blkcg_set_mapping_clean(struct address_space *mapping)
> +{
> + struct blkcg *blkcg;
> +
> + rcu_read_lock();
> + blkcg = rcu_dereference(mapping->i_blkcg);
> + if (blkcg) {
> + css_put(&blkcg->css);
> + RCU_INIT_POINTER(mapping->i_blkcg, NULL);
> + }
> + rcu_read_unlock();
> +}
> #endif
>
Why do we need this? We already have the inode_attach_wb(), which has the
blkcg_css embedded in it for whoever dirtied the inode first. Can we not just
use that? Thanks,
Josef
next prev parent reply other threads:[~2019-03-07 22:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-07 18:08 [PATCH v2 0/3] blkcg: " Andrea Righi
2019-03-07 18:08 ` [PATCH v2 1/3] blkcg: prevent priority inversion problem during sync() Andrea Righi
2019-03-07 22:10 ` Josef Bacik
2019-03-08 7:38 ` Andrea Righi
2019-03-07 18:08 ` [PATCH v2 2/3] blkcg: introduce io.sync_isolation Andrea Righi
2019-03-07 22:11 ` Josef Bacik
2019-03-07 18:08 ` [PATCH v2 3/3] blkcg: implement sync() isolation Andrea Righi
2019-03-07 22:07 ` Josef Bacik [this message]
2019-03-08 7:39 ` Andrea Righi
2019-03-08 17:22 ` [PATCH v2 0/3] blkcg: " Josef Bacik
2019-03-08 17:32 ` Andrea Righi
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=20190307220659.5qmye2pxmto7nlei@macbook-pro-91.dhcp.thefacebook.com \
--to=josef@toxicpanda.com \
--cc=andrea.righi@canonical.com \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=dennis@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizefan@huawei.com \
--cc=paolo.valente@linaro.org \
--cc=tj@kernel.org \
--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