From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751856AbcA0DYE (ORCPT ); Tue, 26 Jan 2016 22:24:04 -0500 Received: from mail-yk0-f177.google.com ([209.85.160.177]:36208 "EHLO mail-yk0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750952AbcA0DYA (ORCPT ); Tue, 26 Jan 2016 22:24:00 -0500 MIME-Version: 1.0 In-Reply-To: <20160127021515.GA7562@js1304-P5Q-DELUXE> References: <20160126000639.358.89668.stgit@dwillia2-desk3.amr.corp.intel.com> <20160126141152.e1043d14502dcca17813afb3@linux-foundation.org> <20160126145153.44e4f38b04200209d133c0a3@linux-foundation.org> <20160127011817.GA7398@js1304-P5Q-DELUXE> <20160127021515.GA7562@js1304-P5Q-DELUXE> Date: Tue, 26 Jan 2016 19:23:59 -0800 Message-ID: Subject: Re: [RFC PATCH] mm: support CONFIG_ZONE_DEVICE + CONFIG_ZONE_DMA From: Dan Williams To: Joonsoo Kim Cc: Andrew Morton , Rik van Riel , linux-nvdimm , Dave Hansen , "linux-kernel@vger.kernel.org" , Christoph Hellwig , Linux MM , Ingo Molnar , Mel Gorman , "H. Peter Anvin" , Jerome Glisse , Sudip Mukherjee Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 26, 2016 at 6:15 PM, Joonsoo Kim wrote: > On Tue, Jan 26, 2016 at 05:37:38PM -0800, Dan Williams wrote: >> On Tue, Jan 26, 2016 at 5:18 PM, Joonsoo Kim wrote: [..] >> > Please refer my previous attempt to add a new zone, ZONE_CMA. >> > >> > https://lkml.org/lkml/2015/2/12/84 >> > >> > It salvages a bit from SECTION_WIDTH by increasing section size. >> > Similarly, I guess we can reduce NODE_WIDTH if needed although >> > it could cause to reduce maximum node size. >> >> Dave pointed out to me that LAST__PID_SHIFT might be a better >> candidate to reduce to 7 bits. That field is for storing pids which >> are already bigger than 8 bits. If it is relying on the fact that >> pids don't rollover very often then likely the impact of 7-bits >> instead of 8 will be minimal. > > Hmm... I'm not sure it's possible or not, but, it looks not a general > solution. It will solve your problem because you are using 64 bit arch > but other 32 bit archs can't get the benefit. This is where the ZONE_CMA and ZONE_DEVICE efforts diverge. ZONE_DEVICE is meant to enable DMA access to hundreds of gigagbytes of persistent memory. A 64-bit-only limitation for ZONE_DEVICE is reasonable.