b31dc66a54
A process flag to indicate whether we are doing sync io is incredibly ugly. It also causes performance problems when one does a lot of async io and then proceeds to sync it. Part of the io will go out as async, and the other part as sync. This causes a disconnect between the previously submitted io and the synced io. For io schedulers such as CFQ, this will cause us lost merges and suboptimal behaviour in scheduling. Remove PF_SYNCWRITE completely from the fsync/msync paths, and let the O_DIRECT path just directly indicate that the writes are sync by using WRITE_SYNC instead. Signed-off-by: Jens Axboe <axboe@suse.de> |
||
|---|---|---|
| .. | ||
| at91_udc.c | ||
| at91_udc.h | ||
| config.c | ||
| dummy_hcd.c | ||
| epautoconf.c | ||
| ether.c | ||
| file_storage.c | ||
| gadget_chips.h | ||
| goku_udc.c | ||
| goku_udc.h | ||
| inode.c | ||
| Kconfig | ||
| lh7a40x_udc.c | ||
| lh7a40x_udc.h | ||
| Makefile | ||
| ndis.h | ||
| net2280.c | ||
| net2280.h | ||
| omap_udc.c | ||
| omap_udc.h | ||
| pxa2xx_udc.c | ||
| pxa2xx_udc.h | ||
| rndis.c | ||
| rndis.h | ||
| serial.c | ||
| usbstring.c | ||
| zero.c | ||