Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753178AbbDAHuR (ORCPT ); Wed, 1 Apr 2015 03:50:17 -0400 Received: from mail-wi0-f178.google.com ([209.85.212.178]:36169 "EHLO mail-wi0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751256AbbDAHuP (ORCPT ); Wed, 1 Apr 2015 03:50:15 -0400 Date: Wed, 1 Apr 2015 09:50:10 +0200 From: Ingo Molnar To: Dan Williams Cc: Christoph Hellwig , Jens Axboe , linux-nvdimm , X86 ML , "linux-kernel@vger.kernel.org" , linux-fsdevel Subject: Re: [Linux-nvdimm] another pmem variant V2 Message-ID: <20150401075010.GA10694@gmail.com> References: <1427358764-6126-1-git-send-email-hch@lst.de> <55143A8B.2060304@plexistor.com> <20150331092526.GA25958@lst.de> <551AB9C7.6020505@plexistor.com> <20150331161648.GA1318@lst.de> <20150331164456.GB8462@gmail.com> <20150331172458.GA3037@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1464 Lines: 42 * Dan Williams wrote: > On Tue, Mar 31, 2015 at 10:24 AM, Christoph Hellwig wrote: > > On Tue, Mar 31, 2015 at 06:44:56PM +0200, Ingo Molnar wrote: > >> I'd be fine with that too - mind sending an updated series? > > > > I will send an updated one tonight or early tomorrow. > > > > Btw, do you want to keep the E820_PRAM name instead of E820_PMEM? > > Seems like most people either don't care or prefer E820_PMEM. I'm > > fine either way. > > FWIW, I like the idea of having a separate E820_PRAM name for > type-12 memory vs future "can't yet disclose" UEFI memory type. The > E820_PRAM type potentially has the property of being relegated to > "legacy" NVDIMMs. We can later add E820_PMEM as a memory type that, > for example, is not automatically backed by struct page. That said, > I'm fine either way. I agree that it's a minor detail, but I think the separation is useful in two ways: - We have a generic 'pmem' driver, but the low level, platform specific RAM enumeration name does not use that name. - 'E820_PRAM' is a more natural extension of 'E820_RAM'. Later on we can then do a: s/E820_PRAM/E820_LEGACY_PRAM rename or so. Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/