On Fri, May 18, 2018 at 10:36 AM, Jason Gunthorpe <jgg@xxxxxxxx> wrote: > On Fri, May 18, 2018 at 04:47:48PM +0000, Christopher Lameter wrote: >> On Fri, 18 May 2018, Jason Gunthorpe wrote: >> >> > > The solution that was proposed at the meeting was that mmu notifiers can >> > > remedy that situation by allowing callbacks to the RDMA device to ensure >> > > that the RDMA device and the filesystem do not do concurrent writeback. >> > >> > This keeps coming up, and I understand why it seems appealing from the >> > MM side, but the reality is that very little RDMA hardware supports >> > this, and it carries with it a fairly big performance penalty so many >> > users don't like using it. >> >> Ok so we have a latent data corruption issue that is not being addressed. >> >> > > But could we do more to prevent issues here? I think what may be useful is >> > > to not allow the memory registrations of file back writable mappings >> > > unless the device driver provides mmu callbacks or something like that. >> > >> > Why does every proposed solution to this involve crippling RDMA? Are >> > there really no ideas no ideas to allow the FS side to accommodate >> > this use case?? >> >> The newcomer here is RDMA. The FS side is the mainstream use case and has >> been there since Unix learned to do paging. > > Well, it has been this way for 12 years, so it isn't that new. > > Honestly it sounds like get_user_pages is just a broken Linux > API?? > > Nothing can use it to write to pages because the FS could explode - > RDMA makes it particularly easy to trigger this due to the longer time > windows, but presumably any get_user_pages could generate a race and > hit this? Is that right? > > I am left with the impression that solving it in the FS is too > performance costly so FS doesn't want that overheard? Was that also > the conclusion? > > Could we take another crack at this during Linux Plumbers? Will the MM > parties be there too? I'm sorry I wasn't able to attend LSFMM this > year! Yes, you and hch were missed, and I had to skip the last day due to a family emergency. Plumbers sounds good to resync on this topic, but we already have a plan, use "break_layouts()" to coordinate a filesystem's need to move dax blocks around relative to an active RDMA memory registration. If you never punch a hole in the middle of your RDMA registration then you never incur any performance penalty. Otherwise the layout break notification is just there to tell the application "hey man, talk to your friend that punched a hole in the middle of your mapping, but the filesystem wants this block back now. Sorry, I'm kicking you out. Ok, bye.". In other words, get_user_pages_longterm() is just a short term band-aid for RDMA until we can get that infrastructure built. We don't need to go down any mmu-notifier rabbit holes.
