Re: [dm-devel] [PATCH] vmalloc: introduce vmap_pfn for persistent memory

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Wed, 8 Nov 2017, Christoph Hellwig wrote:

> On Wed, Nov 08, 2017 at 10:21:38AM -0500, Mikulas Patocka wrote:
> > > And what do you do for an architecture with virtuall indexed caches?
> > 
> > Persistent memory is not supported on such architectures - it is only 
> > supported on x86-64 and arm64.
> 
> For now.  But once support is added your driver will just corrupt data
> unless you have the right API in place.

If dax_flush were able to flush vmapped area, I don't see a problem with 
it.

You obviously can't access the same device simultaneously through vmapped 
area and direct mapping. But when the persistent memory driver is using 
the device, no one is expected to touch it anyway.

Mikulas

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>



[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]
  Powered by Linux