Function report |
Source Code:include\linux\fs.h |
Create Date:2022-07-28 05:42:53 |
Last Modify:2020-03-12 14:18:49 | Copyright©Brick |
home page | Tree |
Annotation kernel can get tool activity | Download SCCT | Chinese |
Name:Returns true if any of the pages in the mapping are marked with the tag.
Proto:static inline bool mapping_tagged(struct address_space *mapping, xa_mark_t tag)
Type:bool
Parameter:
Type | Parameter | Name |
---|---|---|
struct address_space * | mapping | |
xa_mark_t | tag |
Name | Describe |
---|---|
__filemap_fdatawrite_range | __filemap_fdatawrite_range - start writeback on mapping dirty pages in range*@mapping: address space structure to write*@start: offset in bytes where the range starts*@end: offset in bytes where the range ends (inclusive)*@sync_mode: enable synchronous |
test_clear_page_writeback | |
__test_set_page_writeback | |
requeue_inode | Find 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 |
__writeback_single_inode | Write out an inode and its dirty pages. Do not update the writeback list* linkage. That is left to the caller. The caller is also responsible for* setting I_SYNC flag and calling inode_sync_complete() to clear it. |
writeback_single_inode | Write out an inode's dirty pages. Either the caller has an active reference* on the inode or the inode has I_WILL_FREE set.* This function is designed to be called for writing back one inode which* we go e |
wait_sb_inodes | The @s_sync_lock is used to serialise concurrent sync operations* to avoid lock contention problems with concurrent wait_sb_inodes() calls.* Concurrent callers will block on the s_sync_lock rather than doing contending* walks |
Source code conversion tool public plug-in interface | X |
---|---|
Support c/c++/esqlc/java Oracle/Informix/Mysql Plug-in can realize: logical Report Code generation and batch code conversion |