From: Jan Kara Subject: [PATCH 0/4 RESEND] writeback: Dirty list handling changes Date: Thu, 15 May 2014 17:41:53 +0200 Message-ID: <1400168517-3565-1-git-send-email-jack@suse.cz> Cc: Wu Fengguang , Andrew Morton , Jan Kara To: linux-fsdevel@vger.kernel.org Return-path: Received: from cantor2.suse.de ([195.135.220.15]:51269 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751686AbaEOPmM (ORCPT ); Thu, 15 May 2014 11:42:12 -0400 Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Hello, so I was recently thinking about how writeback code shuffles inodes between lists and also how redirty_tail() clobbers dirtied_when timestamp (which broke my sync(2) optimization). This patch series came out of that. Patch 1 is a clear win and just needs an independent review that I didn't forget about something. Patch 3 changes writeback list handling - IMHO it makes the logic somewhat more straightforward as we don't have to bother shuffling inodes between lists and we also don't need to clobber dirtied_when timestamp. But opinions may differ... Patches passed xfstests run and I did some basic writeback tests using tiobench and some artifical sync livelock tests to verify nothing regressed. So I'd be happy if people could have a look. Honza