On 08/05/2010 08:53 PM, Jan Kara wrote: > Background writeback and kupdate-style writeback are easily livelockable (from > a definition of their target). This is inconvenient because it can make sync(1) > stall forever waiting on its queued work to be finished. Generally, if someone > has a particular requirement for writeback he needs, it makes sense to give it > preference over a generic background dirty page cleaning. As soon as that work > is done, flusher thread will return back to background cleaning if it is > needed. So lets just interrupt background and kupdate writeback if there is > some other work to do to fix the livelocking problem. Looks good to me. Acked-by: Jens Axboe <jaxboe@xxxxxxxxxxxx> -- Jens Axboe Confidentiality Notice: This e-mail message, its contents and any attachments to it are confidential to the intended recipient, and may contain information that is privileged and/or exempt from disclosure under applicable law. If you are not the intended recipient, please immediately notify the sender and destroy the original e-mail message and any attachments (and any copies that may have been made) from your system or otherwise. Any unauthorized use, copying, disclosure or distribution of this information is strictly prohibited. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
