On Thu, May 05, 2016 at 11:57:30AM +1000, Dave Chinner wrote:
> We did this intentionally. DAX IO needs to have the same parallel
> write semantics of direct IO, because otherwise a single writer
> prevents any IO concurrency and that's a bigger problem for DAX that
> traditional storage due to the
On Sun, May 01, 2016 at 10:28:54AM -0700, Christoph Hellwig wrote:
> On Fri, Apr 29, 2016 at 12:38:20PM -0400, Waiman Long wrote:
> > From my testing, it looked like that parallel overwrites to the same file in
> > an ext4 filesystem on DAX can happen in parallel even if their range
> > overlaps. I
On 05/01/2016 01:28 PM, Christoph Hellwig wrote:
On Fri, Apr 29, 2016 at 12:38:20PM -0400, Waiman Long wrote:
From my testing, it looked like that parallel overwrites to the same file in
an ext4 filesystem on DAX can happen in parallel even if their range
overlaps. It was mainly because the cod
On Fri, Apr 29, 2016 at 12:38:20PM -0400, Waiman Long wrote:
> From my testing, it looked like that parallel overwrites to the same file in
> an ext4 filesystem on DAX can happen in parallel even if their range
> overlaps. It was mainly because the code will drop the i_mutex before the
> write. Tha
On 04/29/2016 12:27 PM, Waiman Long wrote:
v4->v5:
- Change patch 1 to disable i_dio_count update in do_dax_io().
v3->v4:
- For patch 1, add the DIO_SKIP_DIO_COUNT flag to dax_do_io() calls
only to address issue raised by Dave Chinner.
v2->v3:
- Remove the percpu_stats helper function
v4->v5:
- Change patch 1 to disable i_dio_count update in do_dax_io().
v3->v4:
- For patch 1, add the DIO_SKIP_DIO_COUNT flag to dax_do_io() calls
only to address issue raised by Dave Chinner.
v2->v3:
- Remove the percpu_stats helper functions and use percpu_counters
instead.
v1->v2:
-
6 matches
Mail list logo
