From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f197.google.com (mail-pf0-f197.google.com [209.85.192.197]) by kanga.kvack.org (Postfix) with ESMTP id 1733A6B02CF for ; Wed, 8 Nov 2017 12:47:51 -0500 (EST) Received: by mail-pf0-f197.google.com with SMTP id d28so2765932pfe.1 for ; Wed, 08 Nov 2017 09:47:51 -0800 (PST) Received: from bombadil.infradead.org (bombadil.infradead.org. [65.50.211.133]) by mx.google.com with ESMTPS id k126si4649765pfc.348.2017.11.08.09.47.49 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 08 Nov 2017 09:47:50 -0800 (PST) Date: Wed, 8 Nov 2017 09:47:47 -0800 From: Christoph Hellwig Subject: Re: [dm-devel] [PATCH] vmalloc: introduce vmap_pfn for persistent memory Message-ID: <20171108174747.GA12199@infradead.org> References: <20171108095909.GA7390@infradead.org> <20171108150447.GA10374@infradead.org> <20171108153522.GB24548@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org List-ID: To: Mikulas Patocka Cc: Christoph Hellwig , linux-nvdimm@lists.01.org, Christoph Hellwig , linux-mm@kvack.org, dm-devel@redhat.com, Ross Zwisler , Laura Abbott , Dan Williams , "Kirill A . Shutemov" Can you start by explaining what you actually need the vmap for? Going through a vmap for every I/O is certainly not going to be nice on NVDIMM-N or similar modules :) -- 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