Re: [PATCH 2/5] dax: increase granularity of dax_clear_blocks() operations

2015-10-22 Thread Jan Kara
On Thu 22-10-15 02:41:54, Dan Williams wrote: > dax_clear_blocks is currently performing a cond_resched() after every > PAGE_SIZE memset. We need not check so frequently, for example md-raid > only calls cond_resched() at stripe granularity. Also, in preparation > for introducing a

[PATCH 2/5] dax: increase granularity of dax_clear_blocks() operations

2015-10-22 Thread Dan Williams
dax_clear_blocks is currently performing a cond_resched() after every PAGE_SIZE memset. We need not check so frequently, for example md-raid only calls cond_resched() at stripe granularity. Also, in preparation for introducing a dax_map_atomic() operation that temporarily pins a dax mapping move

[PATCH 2/5] dax: increase granularity of dax_clear_blocks() operations

2015-10-22 Thread Dan Williams
dax_clear_blocks is currently performing a cond_resched() after every PAGE_SIZE memset. We need not check so frequently, for example md-raid only calls cond_resched() at stripe granularity. Also, in preparation for introducing a dax_map_atomic() operation that temporarily pins a dax mapping move

Re: [PATCH 2/5] dax: increase granularity of dax_clear_blocks() operations

2015-10-22 Thread Jan Kara
On Thu 22-10-15 02:41:54, Dan Williams wrote: > dax_clear_blocks is currently performing a cond_resched() after every > PAGE_SIZE memset. We need not check so frequently, for example md-raid > only calls cond_resched() at stripe granularity. Also, in preparation > for introducing a