Lines Matching defs:data
89 * The generator of dirty data starts writeback at this percentage
107 * The longest time for which data is allowed to remain dirty
1567 * data. It looks at the number of dirty pages in the machine and will force
2036 * of all dirty data a few seconds from now. If the flush is already scheduled
2063 * If ratelimit_pages is too high then we can get into dirty-data overload
2159 * @data: data passed to writepage function
2163 * but it is INCORRECT for data-integrity system calls such as fsync(). fsync()
2164 * and msync() need to guarantee that all the data which was dirty at the time
2166 * WB_SYNC_ALL then we were called for data integrity and we must wait for
2171 * writing them. For data-integrity sync we have to be careful so that we do
2187 void *data)
2234 * then, even for data integrity operations: the page
2236 * real expectation of this data interity operation
2263 error = (*writepage)(page, wbc, data);
2325 void *data)
2327 struct address_space *mapping = data;