|To:||Dave Chinner <david@xxxxxxxxxxxxx>|
|Subject:||Re: [PATCH] [RFC] xfs: byte range buffer dirty region tracking|
|From:||Mark Tinguely <tinguely@xxxxxxx>|
|Date:||Wed, 26 Feb 2014 08:53:59 -0600|
|User-agent:||Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20120122 Thunderbird/9.0|
On 02/23/14 16:25, Dave Chinner wrote:
From: Dave Chinner<dchinner@xxxxxxxxxx> Switching this to just track the first and last modified bytes in the block and only converting that to a dirty bitmap in the buffer log item at format time, however, gets rid of most of this dirty bitmap overhead without increasing memcpy time at all. the result is that peformance on a 64k directory block size increases to roughly 16,000 files/s with memcpy() overhead only slightly increasing.
Looks interesting. 4 regions seems reasonable to me. --Mark.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: [PATCH 6/6] ext4/242: Add ext4 specific test for fallocate zero range, Lukáš Czerner|
|Next by Date:||Re: [PATCH 6/6] ext4/242: Add ext4 specific test for fallocate zero range, Lukáš Czerner|
|Previous by Thread:||Re: [PATCH] [RFC] xfs: byte range buffer dirty region tracking, Dave Chinner|
|Next by Thread:||[ANNOUNCE] xfsprogs: master branch updated to da2b3c0, Dave Chinner|
|Indexes:||[Date] [Thread] [Top] [All Lists]|