Hello, Jan. On Thu, Jun 20, 2019 at 05:21:45PM +0200, Jan Kara wrote: > I'm completely ignorant of how btrfs compressed writeback works so don't > quite understand implications of this. So does this mean that writeback to > btrfs compressed files won't be able to transition inodes from one memcg to > another? Or are you trying to say the 'wbc' used from async worker thread > is actually a dummy one and we would double-account the writeback? So, before, only the async compression workers would run through the wbc accounting code regardless of who originated the dirty pages, which is obviously wrong. After the patch, the code accounts when the dirty pages are being handed off to the compression workers and no_wbc_acct is used to suppress spurious accounting from the workers. > Anyway, AFAICS no_wbc_acct means: "IO done as a result of this wbc will not > have influence on inode memcg ownership", doesn't it? Yeap. Thanks. -- tejun
