Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2842793imu; Thu, 17 Jan 2019 23:50:25 -0800 (PST) X-Google-Smtp-Source: ALg8bN5zegYVJLAdoYgP2Hu/ZMZRLvhe1r24JuoYjhkwpHErPFoVtXjM2vKwdlPz8hdeqTy5whjC X-Received: by 2002:a63:4456:: with SMTP id t22mr16896916pgk.0.1547797825164; Thu, 17 Jan 2019 23:50:25 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1547797825; cv=none; d=google.com; s=arc-20160816; b=lLYKlkCtbojLi4Tn4mfXnKuMlkM9BmVZV95CBuCr/tSLvzsWrdbWspuLokBruVbyIX r/gSV9iXLf9thp28c8YBuAvDthOryjsZSOKBFwE2v6tgNMG15Bju5C/3IEP9CvLYksEH dEOv1AfkrJhAzK6TkHslKzLtAVvxsB8hdvIR8CkFQUJu7sxO+h3auGSzwXjQhIhH6t8X 6LaC04cK86ba9iYf/uJ3U/uAbXk3z4C9od17v8K4MCKt2r1vDfJgFhn62+EtpLXmLMiR Lh6d5MwQa2xMZyqFxPAzKkUdLWfLnlu4QTNCy92bLjA5WYtnhKdkBcvnxY+4qsMb6Q37 ELhA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=1sD45OeRcpdhCi7aguh3zehR3mbmyB7GfmelEOajBBU=; b=jT6K/nqYKYQqx9ehx0dN9HS0eQzaDfQgoulq9q3MIBfc/SbYIxA8fqAeSybQIO04QH Yb20mySzAMpjWOPc5X5dxb+RGzVENOWEu9KnROZuNUTMHA5PGAk0OYlkBMEKBVPaHtPi ucjOB8rUdqIaH3RgGg/0rTznasqqV0CcBu1HKEoQU2rr6ebU46wuyZasn3Nphy6YSsEv qcQBcTzTy+CCp7OkjVkg55qBmt7tO4cUNnRpCaCfWZKUZN5l1FntGaAlpxZloq4NMvVa kKnWI+HM2vhvGLTwxXri3TyRCpbtm8xp1DbzyBKJB/mdmiixYX4N7uwqw7nYzZGJf4lr 2nKg== 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 g124si3728155pgc.568.2019.01.17.23.50.06; Thu, 17 Jan 2019 23:50:25 -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 S1727452AbfARHrO (ORCPT + 99 others); Fri, 18 Jan 2019 02:47:14 -0500 Received: from mga14.intel.com ([192.55.52.115]:48229 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727349AbfARHrL (ORCPT ); Fri, 18 Jan 2019 02:47:11 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 Jan 2019 23:47:11 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,489,1539673200"; d="scan'208";a="109214309" Received: from ymzhang.sh.intel.com (HELO [10.239.154.104]) ([10.239.154.104]) by orsmga006.jf.intel.com with ESMTP; 17 Jan 2019 23:47:06 -0800 Subject: Re: [PATCH 4/4] dax: "Hotplug" persistent memory for use like normal RAM To: Dave Hansen , Dave Hansen , dave@sr71.net Cc: dan.j.williams@intel.com, dave.jiang@intel.com, zwisler@kernel.org, vishal.l.verma@intel.com, thomas.lendacky@amd.com, akpm@linux-foundation.org, mhocko@suse.com, linux-nvdimm@lists.01.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, ying.huang@intel.com, fengguang.wu@intel.com, bp@suse.de, bhelgaas@google.com, baiyaowei@cmss.chinamobile.com, tiwai@suse.de References: <20190116181859.D1504459@viggo.jf.intel.com> <20190116181905.12E102B4@viggo.jf.intel.com> <5ef5d5e9-9d35-fb84-b69e-7456dcf4c241@linux.intel.com> <1e9377c6-11a0-3bbd-763d-d9347bd556cf@intel.com> From: Yanmin Zhang Message-ID: <74c01a55-1a47-d649-a32a-ea597c24ab4a@linux.intel.com> Date: Fri, 18 Jan 2019 15:47:32 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <1e9377c6-11a0-3bbd-763d-d9347bd556cf@intel.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2019/1/17 下午11:17, Dave Hansen wrote: > On 1/17/19 12:19 AM, Yanmin Zhang wrote: >>> >> I didn't try pmem and I am wondering it's slower than DRAM. >> Should a flag, such like _GFP_PMEM, be added to distinguish it from >> DRAM? > > Absolutely not. :) Agree. > > We already have performance-differentiated memory, and lots of ways to > enumerate and select it in the kernel (all of our NUMA infrastructure). Kernel does manage memory like what you say. My question is: with your patch, PMEM becomes normal RAM, then there is a chance for kernel to allocate PMEM as DMA buffer. Some super speed devices like 10Giga NIC, USB (SSIC connecting modem), might not work well if DMA buffer is in PMEM as it's slower than DRAM. Should your patchset consider it? > > PMEM is also just the first of many "kinds" of memory that folks want to > build in systems and use a "RAM". We literally don't have space to put > a flag in for each type. > >