Searched refs:kjournald (Results 1 - 7 of 7) sorted by relevance

/linux-4.1.27/fs/jbd/
H A Drevoke.c67 * happen only from the kjournald and no other thread touches this table. Also
70 * kjournald. Therefore we need no locks when accessing the hashtable belonging
74 * have a handle to the transaction. Therefore they are safe from kjournald
H A Djournal.c123 * kjournald: The main thread function used to manage a logging device
138 static int kjournald(void *arg) kjournald() function
156 printk(KERN_INFO "kjournald starting. Commit interval %ld seconds\n", kjournald()
187 jbd_debug(1, "Now suspending kjournald\n"); kjournald()
217 jbd_debug(1, "kjournald wakes\n"); kjournald()
242 t = kthread_run(kjournald, journal, "kjournald"); journal_start_thread()
481 the evidence before kjournald goes into a loop and __log_start_commit()
/linux-4.1.27/fs/jbd2/
H A Drevoke.c67 * happen only from the kjournald and no other thread touches this table. Also
70 * kjournald. Therefore we need no locks when accessing the hashtable belonging
74 * have a handle to the transaction. Therefore they are safe from kjournald
H A Djournal.c530 the evidence before kjournald goes into a loop and __jbd2_log_start_commit()
/linux-4.1.27/include/linux/
H A Djbd.h380 * [no locking - only kjournald alters this]
H A Djbd2.h371 * since we cannot afford doing last iput() on behalf of kjournald
/linux-4.1.27/mm/
H A Dvmscan.c2687 * progress. kjournald for example may enter direct reclaim while throttle_direct_reclaim()

Completed in 210 milliseconds