On 24/10/2019 01:13, Dave Chinner wrote: > On Wed, Oct 23, 2019 at 04:09:50PM +0300, Boaz Harrosh wrote: >> On 22/10/2019 14:21, Boaz Harrosh wrote: >>> On 20/10/2019 18:59, ira.weiny@xxxxxxxxx wrote: >> Please explain the use case behind your model? > > No application changes needed to control whether they use DAX or > not. It allows the admin to control the application behaviour > completely, so they can turn off DAX if necessary. Applications are > unaware of constraints that may prevent DAX from being used, and so > admins need a mechanism to prevent DAX aware application from > actually using DAX if the capability is present. > > e.g. given how slow some PMEM devices are when it comes to writing > data, especially under extremely high concurrency, DAX is not > necessarily a performance win for every application. Admins need a > guaranteed method of turning off DAX in these situations - apps may > not provide such a knob, or even be aware of a thing called DAX... > Thank you Dave for explaining. Forgive my slowness. I now understand your intention. But if so please address my first concern. That in the submitted implementation you must set the flag-bit after the create of the file but before the write. So exactly the above slow writes must always be DAX if I ever want the file to be DAX accessed in the future. In fact I do not see how you do this without changing the application because most applications create thier own files, so you do not have a chance to set the DAX-flag before the write happens. So the only effective fixture is the inheritance from the parent directory. But then again how do you separate from the slow writes that we would like none-DAX to the DAX reads that are fast and save so much resources and latency. What if, say in XFS when setting the DAX-bit we take all the three write-locks same as a truncate. Then we check that there are no active page-cache mappings ie. a single opener. Then allow to set the bit. Else return EBUISY. (file is in use) > e.g. the data set being accessed by the application is mapped and > modified by RDMA applications, so those files must not be accessed > using DAX by any application because DAX+RDMA are currently > incompatible. Hence you can have RDMA on pmem devices co-exist > within the same filesystem as other applications using DAX to access > the pmem... > I actually like the lastest patchset that takes a lease on the file. But yes an outside admin tool to set different needs. > Cheers, > Dave. > Yes, thanks Boaz
