Re: [PATCH v2 3/3] blkcg: implement sync() isolation

2019-03-07 Thread Andrea Righi
On Thu, Mar 07, 2019 at 05:07:01PM -0500, Josef Bacik wrote: > 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 pa

Re: [PATCH v2 3/3] blkcg: implement sync() isolation

2019-03-07 Thread Josef Bacik
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 o

[PATCH v2 3/3] blkcg: implement sync() isolation

2019-03-07 Thread Andrea Righi
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 b