[PATCH 0/4 RESEND] writeback: Dirty list handling changes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



  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
--
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




[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux