Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2128356imu; Thu, 17 Jan 2019 08:50:40 -0800 (PST) X-Google-Smtp-Source: ALg8bN7zQIWWeBQwDxCPcG2GJehMiXKWnzFUmx2Wqjw5UUoAReKF4IKbBmcDlZZchQXnhokk21oy X-Received: by 2002:a17:902:c5:: with SMTP id a63mr15888039pla.267.1547743840859; Thu, 17 Jan 2019 08:50:40 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1547743840; cv=none; d=google.com; s=arc-20160816; b=Bw4hqQBJJT2rPWW4yXijm4GXICanJ7H0wldHndHTL38V7ifuj3oPHdiTM+RdN3hl5Y OsqdTfagzhZ65J7ZXub8x4soaZbTfjV+SwunI8zIe3IfoAM0LeGf4+i0Mkxh3aHt7zr4 Svi/Qrp08buDfY0AJXYa1rFnh/TzjLHf10Hmv6vO2S+WyEN+i2ShG7lwu0SW8bY63tMG MklNsMBQ7jsIF2HGN/MhO0A+XeExiBFpIEdLIFdoBU2YAZtfziLjk2+H4npx0dfDgi2A weaH19VA+SOmsCxJ8JQ2+CvPQ26uRUwjNmqL0H1IyK7izcARSYsnlpmdvWZqynOXXdj8 1oTA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=tGQ4HPHxy6uQ/tvW5NyOZ1c228ABkJGbtKl7/YtffDc=; b=BQDcWyQcBIeZMpQxbQd/gwX+PJXHNtVeY8qtjDRegF3als24yCU7xuvvpFxF71CIsk qzmM93w062ciD0amUuC/42ZHY+4psRUQNufHP+E2f0MKpq5GJw1mGbDE8ekBhWrVKNSN a1MLAob4JRWEZYfMUKknuF3aXKtyOEdwo84wWW7/jZcstZMxI+elY6b/XMTeUAPe3QRp l8ER65CA7Lo5dD754m+RvjiITc/6QIQjYdOJrYmve6D8PcbObmr2cuOOm8fYFA/5XN5B CByNGwDlb4mE4+AOMfA9tpI2MiioK7xfclwRVDqHHRishFxlA2vem9mqQ1UcyrdeJWYu ocoA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j17si2189322pfd.113.2019.01.17.08.50.23; Thu, 17 Jan 2019 08:50:40 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729118AbfAQQs4 (ORCPT + 99 others); Thu, 17 Jan 2019 11:48:56 -0500 Received: from mga17.intel.com ([192.55.52.151]:11152 "EHLO mga17.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728980AbfAQQsv (ORCPT ); Thu, 17 Jan 2019 11:48:51 -0500 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga107.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 Jan 2019 08:48:50 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,489,1539673200"; d="scan'208";a="119296606" Received: from unknown (HELO localhost.localdomain) ([10.232.112.69]) by orsmga003.jf.intel.com with ESMTP; 17 Jan 2019 08:48:49 -0800 Date: Thu, 17 Jan 2019 09:47:37 -0700 From: Keith Busch To: Jeff Moyer Cc: Dave Hansen , thomas.lendacky@amd.com, fengguang.wu@intel.com, dave@sr71.net, linux-nvdimm@lists.01.org, tiwai@suse.de, zwisler@kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, mhocko@suse.com, baiyaowei@cmss.chinamobile.com, ying.huang@intel.com, bhelgaas@google.com, akpm@linux-foundation.org, bp@suse.de Subject: Re: [PATCH 0/4] Allow persistent memory to be used like normal RAM Message-ID: <20190117164736.GC31543@localhost.localdomain> References: <20190116181859.D1504459@viggo.jf.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jan 17, 2019 at 11:29:10AM -0500, Jeff Moyer wrote: > Dave Hansen writes: > > Persistent memory is cool. But, currently, you have to rewrite > > your applications to use it. Wouldn't it be cool if you could > > just have it show up in your system like normal RAM and get to > > it like a slow blob of memory? Well... have I got the patch > > series for you! > > So, isn't that what memory mode is for? > https://itpeernetwork.intel.com/intel-optane-dc-persistent-memory-operating-modes/ > > Why do we need this code in the kernel? I don't think those are the same thing. The "memory mode" in the link refers to platforms that sequester DRAM to side cache memory access, where this series doesn't have that platform dependency nor hides faster DRAM.