Lines Matching refs:writeback

382 written asynchronously to the backing filesystem by the writeback
388 controllers cannot be established making it impossible for writeback
390 writeback IOs are attributed to the root cgroup.
393 and the filesystem supports cgroup writeback, writeback operations
398 and enforces the more restrictive of the two.  Also, writeback control
401 to their current writeback bandwidth.
404 granularity between memory controller and writeback.  While memory
405 controller tracks ownership per page, writeback operates on inode
406 basis.  cgroup writeback bridges the gap by tracking ownership by
411 This is a conscious design choice as writeback operations are
418 released, even if cgroup writeback strictly follows page ownership,
423 Filesystem support for cgroup writeback
426 A filesystem can make writeback IOs cgroup-aware by updating
432   Should be called for each bio carrying writeback data and associates
440   writeback session, it's the easiest and most natural to call it as
443 With writeback bio's annotated, cgroup support can be enabled per
445 selective disabling of cgroup writeback support which is helpful when
451 the writeback session is holding shared resources, e.g. a journal