Re: [PATCH 01/10] writeback: move backing_dev_info->state into bdi_writeback
From: Tejun Heo
Date: Thu Nov 20 2014 - 10:38:48 EST
On Thu, Nov 20, 2014 at 04:27:02PM +0100, Jan Kara wrote:
> Hum, does it make sense to convert BDI_sync_congested and
> BDI_async_congested? It contains information whether the *device* is
> congested and cannot take more work. I understand that in a cgroup world
Yeah, I mean, with cgroup writeback, the device itself doesn't matter.
The only thing writeback sees is that cgroup's slice of the device
whose congestion status can be independent from other slices of the
> you want to throttle IO from a cgroup to a device so when you take
> bdi_writeback to be a per-cgroup structure you want some indication there
> that a particular cgroup cannot push more to the device. But is it that
> e.g. mdraid cares about a cgroup and not about the device?
I didn't update mdraid to support cgroup writeback yet but it depends
on how it's implemented. If it just transmits back the pressure from
individual underlying cgroup split devices, it's the same. If we
wanna put blkcg splitting in front of mdraid and keep the backend side
clear of cgroup splitting, it'd just send down everything as belonging
to the root cgroup.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/