From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ingo Molnar <mingo@kernel.org>
Subject: Re: another pmem variant V2
Date: Tue, 31 Mar 2015 18:44:56 +0200
Message-ID: <20150331164456.GB8462@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>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Boaz Harrosh <boaz@plexistor.com>, linux-nvdimm@ml01.01.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	x86@kernel.org, ross.zwisler@linux.intel.com, axboe@kernel.dk
To: Christoph Hellwig <hch@lst.de>
Return-path: <linux-kernel-owner@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <20150331161648.GA1318@lst.de>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org


* Christoph Hellwig <hch@lst.de> wrote:

> On Tue, Mar 31, 2015 at 06:14:15PM +0300, Boaz Harrosh wrote:
> > We can not accept it as is right now.
> 
> Who is we?
> 
> > We have conducted farther tests. And it messes up NUMA.
> 
> Only you if you use the memmap option in weird ways.
> 
> Sounds like I should simply remove the memmap= option so people don't
> abuse it.  The main point is to parse the e820 tables, which works fine.

I'd be fine with that too - mind sending an updated series?

the memmap= option can be added on top of that.

Thanks,

	Ingo