From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753315AbbCaQQy (ORCPT ); Tue, 31 Mar 2015 12:16:54 -0400 Received: from verein.lst.de ([213.95.11.211]:55976 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753276AbbCaQQu (ORCPT ); Tue, 31 Mar 2015 12:16:50 -0400 Date: Tue, 31 Mar 2015 18:16:48 +0200 From: Christoph Hellwig To: Boaz Harrosh Cc: Christoph Hellwig , 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 Subject: Re: another pmem variant V2 Message-ID: <20150331161648.GA1318@lst.de> References: <1427358764-6126-1-git-send-email-hch@lst.de> <55143A8B.2060304@plexistor.com> <20150331092526.GA25958@lst.de> <551AB9C7.6020505@plexistor.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <551AB9C7.6020505@plexistor.com> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. And those people having fake pmem, or pcie cards that they are too lazy to submit proper drivers for can stick to their out of tree hacks?