Searched hist:b6e51316 (Results 1 – 5 of 5) sorted by relevance
/openbmc/linux/fs/ubifs/ |
H A D | budget.c | b6e51316 Wed Sep 16 08:13:54 CDT 2009 Jens Axboe <jens.axboe@oracle.com> writeback: separate starting of sync vs opportunistic writeback
bdi_start_writeback() is currently split into two paths, one for WB_SYNC_NONE and one for WB_SYNC_ALL. Add bdi_sync_writeback() for WB_SYNC_ALL writeback and let bdi_start_writeback() handle only WB_SYNC_NONE.
Push down the writeback_control allocation and only accept the parameters that make sense for each function. This cleans up the API considerably.
Signed-off-by: Jens Axboe <jens.axboe@oracle.com> b6e51316 Wed Sep 16 08:13:54 CDT 2009 Jens Axboe <jens.axboe@oracle.com> writeback: separate starting of sync vs opportunistic writeback bdi_start_writeback() is currently split into two paths, one for WB_SYNC_NONE and one for WB_SYNC_ALL. Add bdi_sync_writeback() for WB_SYNC_ALL writeback and let bdi_start_writeback() handle only WB_SYNC_NONE. Push down the writeback_control allocation and only accept the parameters that make sense for each function. This cleans up the API considerably. Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
|
/openbmc/linux/include/linux/ |
H A D | writeback.h | b6e51316 Wed Sep 16 08:13:54 CDT 2009 Jens Axboe <jens.axboe@oracle.com> writeback: separate starting of sync vs opportunistic writeback
bdi_start_writeback() is currently split into two paths, one for WB_SYNC_NONE and one for WB_SYNC_ALL. Add bdi_sync_writeback() for WB_SYNC_ALL writeback and let bdi_start_writeback() handle only WB_SYNC_NONE.
Push down the writeback_control allocation and only accept the parameters that make sense for each function. This cleans up the API considerably.
Signed-off-by: Jens Axboe <jens.axboe@oracle.com> b6e51316 Wed Sep 16 08:13:54 CDT 2009 Jens Axboe <jens.axboe@oracle.com> writeback: separate starting of sync vs opportunistic writeback bdi_start_writeback() is currently split into two paths, one for WB_SYNC_NONE and one for WB_SYNC_ALL. Add bdi_sync_writeback() for WB_SYNC_ALL writeback and let bdi_start_writeback() handle only WB_SYNC_NONE. Push down the writeback_control allocation and only accept the parameters that make sense for each function. This cleans up the API considerably. Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
|
H A D | backing-dev.h | b6e51316 Wed Sep 16 08:13:54 CDT 2009 Jens Axboe <jens.axboe@oracle.com> writeback: separate starting of sync vs opportunistic writeback
bdi_start_writeback() is currently split into two paths, one for WB_SYNC_NONE and one for WB_SYNC_ALL. Add bdi_sync_writeback() for WB_SYNC_ALL writeback and let bdi_start_writeback() handle only WB_SYNC_NONE.
Push down the writeback_control allocation and only accept the parameters that make sense for each function. This cleans up the API considerably.
Signed-off-by: Jens Axboe <jens.axboe@oracle.com> b6e51316 Wed Sep 16 08:13:54 CDT 2009 Jens Axboe <jens.axboe@oracle.com> writeback: separate starting of sync vs opportunistic writeback bdi_start_writeback() is currently split into two paths, one for WB_SYNC_NONE and one for WB_SYNC_ALL. Add bdi_sync_writeback() for WB_SYNC_ALL writeback and let bdi_start_writeback() handle only WB_SYNC_NONE. Push down the writeback_control allocation and only accept the parameters that make sense for each function. This cleans up the API considerably. Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
|
/openbmc/linux/fs/ |
H A D | fs-writeback.c | b6e51316 Wed Sep 16 08:13:54 CDT 2009 Jens Axboe <jens.axboe@oracle.com> writeback: separate starting of sync vs opportunistic writeback
bdi_start_writeback() is currently split into two paths, one for WB_SYNC_NONE and one for WB_SYNC_ALL. Add bdi_sync_writeback() for WB_SYNC_ALL writeback and let bdi_start_writeback() handle only WB_SYNC_NONE.
Push down the writeback_control allocation and only accept the parameters that make sense for each function. This cleans up the API considerably.
Signed-off-by: Jens Axboe <jens.axboe@oracle.com> b6e51316 Wed Sep 16 08:13:54 CDT 2009 Jens Axboe <jens.axboe@oracle.com> writeback: separate starting of sync vs opportunistic writeback bdi_start_writeback() is currently split into two paths, one for WB_SYNC_NONE and one for WB_SYNC_ALL. Add bdi_sync_writeback() for WB_SYNC_ALL writeback and let bdi_start_writeback() handle only WB_SYNC_NONE. Push down the writeback_control allocation and only accept the parameters that make sense for each function. This cleans up the API considerably. Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
|
/openbmc/linux/mm/ |
H A D | page-writeback.c | b6e51316 Wed Sep 16 08:13:54 CDT 2009 Jens Axboe <jens.axboe@oracle.com> writeback: separate starting of sync vs opportunistic writeback
bdi_start_writeback() is currently split into two paths, one for WB_SYNC_NONE and one for WB_SYNC_ALL. Add bdi_sync_writeback() for WB_SYNC_ALL writeback and let bdi_start_writeback() handle only WB_SYNC_NONE.
Push down the writeback_control allocation and only accept the parameters that make sense for each function. This cleans up the API considerably.
Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
|