|
@@ -1857,8 +1857,10 @@ following two functions.
|
|
|
|
|
|
wbc_init_bio(@wbc, @bio)
|
|
|
Should be called for each bio carrying writeback data and
|
|
|
- associates the bio with the inode's owner cgroup. Can be
|
|
|
- called anytime between bio allocation and submission.
|
|
|
+ associates the bio with the inode's owner cgroup and the
|
|
|
+ corresponding request queue. This must be called after
|
|
|
+ a queue (device) has been associated with the bio and
|
|
|
+ before submission.
|
|
|
|
|
|
wbc_account_io(@wbc, @page, @bytes)
|
|
|
Should be called for each data segment being written out.
|
|
@@ -1877,7 +1879,7 @@ the configuration, the bio may be executed at a lower priority and if
|
|
|
the writeback session is holding shared resources, e.g. a journal
|
|
|
entry, may lead to priority inversion. There is no one easy solution
|
|
|
for the problem. Filesystems can try to work around specific problem
|
|
|
-cases by skipping wbc_init_bio() or using bio_associate_blkcg()
|
|
|
+cases by skipping wbc_init_bio() or using bio_associate_create_blkg()
|
|
|
directly.
|
|
|
|
|
|
|