{"push_id":1645190832,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"ba71e65a91e205481ce98e257cabe65a06fea26d","before":"29cda1ed15c210da5d8625ea757bc1a937e77954","commits":[{"sha":"ba71e65a91e205481ce98e257cabe65a06fea26d","author":{"name":"Jan Kara","email":"7bb7087018cc5fef3c041f6f038f586664845dbf@suse.com"},"message":"fs/sync.c: make sync_file_range(2) use WB_SYNC_NONE writeback\n\nsync_file_range(2) is documented to issue writeback only for pages that\nare not currently being written.  After all the system call has been\ncreated for userspace to be able to issue background writeout and so\nwaiting for in-flight IO is undesirable there.  However commit\nee53a891f474 (\"mm: do_sync_mapping_range integrity fix\") switched\ndo_sync_mapping_range() and thus sync_file_range() to issue writeback in\nWB_SYNC_ALL mode since do_sync_mapping_range() was used by other code\nrelying on WB_SYNC_ALL semantics.\n\nThese days do_sync_mapping_range() went away and we can switch\nsync_file_range(2) back to issuing WB_SYNC_NONE writeback.  That should\nhelp PostgreSQL avoid large latency spikes when flushing data in the\nbackground.\n\nAndres measured a 20% increase in transactions per second on an SSD disk.\n\nSigned-off-by: Jan Kara <jack@suse.com>\nReported-by: Andres Freund <andres@anarazel.de>\nTested-By: Andres Freund <andres@anarazel.de>\nCc: Al Viro <viro@ZenIV.linux.org.uk>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/alexSduzz/dark_kernel/commits/ba71e65a91e205481ce98e257cabe65a06fea26d"}]}
{"actor":{"display_login":"alexSduzz"}}