From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-f72.google.com (mail-oi0-f72.google.com [209.85.218.72]) by kanga.kvack.org (Postfix) with ESMTP id 9DD95440417 for ; Wed, 8 Nov 2017 10:41:26 -0500 (EST) Received: by mail-oi0-f72.google.com with SMTP id o126so2298287oif.21 for ; Wed, 08 Nov 2017 07:41:26 -0800 (PST) Received: from mail-sor-f41.google.com (mail-sor-f41.google.com. [209.85.220.41]) by mx.google.com with SMTPS id i58sor222283ote.70.2017.11.08.07.41.24 for (Google Transport Security); Wed, 08 Nov 2017 07:41:24 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <20171108153522.GB24548@infradead.org> References: <20171108095909.GA7390@infradead.org> <20171108150447.GA10374@infradead.org> <20171108153522.GB24548@infradead.org> From: Dan Williams Date: Wed, 8 Nov 2017 07:41:23 -0800 Message-ID: Subject: Re: [dm-devel] [PATCH] vmalloc: introduce vmap_pfn for persistent memory Content-Type: text/plain; charset="UTF-8" Sender: owner-linux-mm@kvack.org List-ID: To: Christoph Hellwig Cc: Mikulas Patocka , "linux-nvdimm@lists.01.org" , Christoph Hellwig , Linux MM , dm-devel@redhat.com, Ross Zwisler , Laura Abbott , "Kirill A . Shutemov" On Wed, Nov 8, 2017 at 7:35 AM, 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. I'm also in the process of ripping out page-less dax support. With pages we can potentially leverage the VIVT-cache support in some architectures, likely with more supporting infrastructure for dax_flush(). -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org