Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758687AbcJYMg4 (ORCPT ); Tue, 25 Oct 2016 08:36:56 -0400 Received: from mail-pf0-f195.google.com ([209.85.192.195]:34076 "EHLO mail-pf0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756717AbcJYMgz (ORCPT ); Tue, 25 Oct 2016 08:36:55 -0400 Subject: Re: [RFC 5/8] mm: Add new flag VM_CDM for coherent device memory To: Dave Hansen , Anshuman Khandual , linux-kernel@vger.kernel.org, linux-mm@kvack.org References: <1477283517-2504-1-git-send-email-khandual@linux.vnet.ibm.com> <1477283517-2504-6-git-send-email-khandual@linux.vnet.ibm.com> <580E4704.1040104@intel.com> Cc: mhocko@suse.com, js1304@gmail.com, vbabka@suse.cz, mgorman@suse.de, minchan@kernel.org, akpm@linux-foundation.org, aneesh.kumar@linux.vnet.ibm.com From: Balbir Singh Message-ID: <2a9819b8-0d2d-fb2a-e9d1-094f7f3cf54c@gmail.com> Date: Tue, 25 Oct 2016 23:36:34 +1100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <580E4704.1040104@intel.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1156 Lines: 30 On 25/10/16 04:38, Dave Hansen wrote: > On 10/23/2016 09:31 PM, Anshuman Khandual wrote: >> VMAs containing coherent device memory should be marked with VM_CDM. These >> VMAs need to be identified in various core kernel paths and this new flag >> will help in this regard. > > ... and it's sticky? So if a VMA *ever* has one of these funky pages in > it, it's stuck being VM_CDM forever? Never to be merged with other > VMAs? Never to see the light of autonuma ever again? > > What if a 100TB VMA has one page of fancy pants device memory, and the > rest normal vanilla memory? Do we really want to consider the whole > thing fancy? > Those are good review comments to improve the patchset. > This whole patch set is looking really hackish. If you want things to > be isolated from the VM, them it should probably *actually* be isolated > from the VM. As Jerome mentioned, ZONE_DEVICE is probably a better > thing to use here than to try what you're attempting. > The RFC explains the motivation, this is not fancy pants, it is regular memory from the systems perspective, with some changes as described Thanks for the review! Balbir Singh