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

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

 



> Seems to me that this problem has been solved elswhere in the
> kernel, like for tracking of timers to expire on a given jiffie
> (tvec, tvec_base, timer_lists). Perhaps we should be looking to move
> to a set of time based lists for efficiently tracking what inodes
> should be written back at a given background writeback interval
> rather than trying to keep everything on the one list.

It's also pretty similar to the mru cache we use for filesystems in XFS,
except that we'd start writeback instead of deleting items.  The whole
bucket scheme there should also help with I/O batching.

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