Re: [PATCH 3/3] ext4: Pass DIO_SKIP_DIO_COUNT to dax_do_io

2016-06-09 Thread Christoph Hellwig
On Fri, Jun 03, 2016 at 06:28:17PM -0400, Waiman Long wrote: > Since all the DAX I/Os are synchronous, there is no need to update > the DIO count in dax_do_io() when the count has already been updated > or the i_rwsem lock (read or write) has or will be taken. > > This patch passes in the

Re: [PATCH 3/3] ext4: Pass DIO_SKIP_DIO_COUNT to dax_do_io

2016-06-09 Thread Christoph Hellwig
On Fri, Jun 03, 2016 at 06:28:17PM -0400, Waiman Long wrote: > Since all the DAX I/Os are synchronous, there is no need to update > the DIO count in dax_do_io() when the count has already been updated > or the i_rwsem lock (read or write) has or will be taken. > > This patch passes in the

[PATCH 3/3] ext4: Pass DIO_SKIP_DIO_COUNT to dax_do_io

2016-06-03 Thread Waiman Long
Since all the DAX I/Os are synchronous, there is no need to update the DIO count in dax_do_io() when the count has already been updated or the i_rwsem lock (read or write) has or will be taken. This patch passes in the DIO_SKIP_DIO_COUNT flag to dax_do_io() to disable two unneeded atomic

[PATCH 3/3] ext4: Pass DIO_SKIP_DIO_COUNT to dax_do_io

2016-06-03 Thread Waiman Long
Since all the DAX I/Os are synchronous, there is no need to update the DIO count in dax_do_io() when the count has already been updated or the i_rwsem lock (read or write) has or will be taken. This patch passes in the DIO_SKIP_DIO_COUNT flag to dax_do_io() to disable two unneeded atomic