Function report

Linux Kernel

v5.5.9

Brick Technologies Co., Ltd

Source Code:fs\fs-writeback.c Create Date:2022-07-28 20:10:48
Last Modify:2020-03-12 14:18:49 Copyright©Brick
home page Tree
Annotation kernel can get tool activityDownload SCCTChinese

Name:de_io_list_move_locked - move an inode onto a bdi_writeback IO list*@inode: inode to be moved*@wb: target bdi_writeback*@head: one of @wb->b_{dirty|io|more_io|dirty_time}* Move @inode->i_io_list to @list of @wb and set %WB_has_dirty_io

Proto:static bool inode_io_list_move_locked(struct inode *inode, struct bdi_writeback *wb, struct list_head *head)

Type:bool

Parameter:

TypeParameterName
struct inode *inode
struct bdi_writeback *wb
struct list_head *head
123  assert_spin_locked( & protects the b_* lists )
125  list_move - delete from one list and add as another's head*@list: the entry to move*@head: the head that will precede our entry
128  If head != ime stamps are dirty Then Return wb_io_lists_populated(wb)
131  wb_io_lists_depopulated(wb)
132  Return false
Caller
NameDescribe
redirty_tailRedirty an inode: set its when-it-was dirtied timestamp and move it to the* furthest end of its superblock's dirty-inode list.* Before stamping the inode's ->dirtied_when, we check to see whether it is
requeue_ioqueue inode for re-scanning after bdi->b_io list is exhausted.
requeue_inodeFind proper writeback list for the inode depending on its current state and* possibly also change of its state while we were doing writeback. Here we* handle things such as livelock prevention or fairness of writeback among* inodes
__mark_inode_dirty__mark_inode_dirty - internal function*@inode: inode to mark*@flags: what kind of dirty (i