From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751629AbdAaFtR (ORCPT ); Tue, 31 Jan 2017 00:49:17 -0500 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:58180 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751346AbdAaFtM (ORCPT ); Tue, 31 Jan 2017 00:49:12 -0500 Subject: Re: [RFC V2 00/12] Define coherent device memory node To: Anshuman Khandual , linux-kernel@vger.kernel.org, linux-mm@kvack.org References: <20170130033602.12275-1-khandual@linux.vnet.ibm.com> Cc: mhocko@suse.com, vbabka@suse.cz, mgorman@suse.de, minchan@kernel.org, aneesh.kumar@linux.vnet.ibm.com, bsingharora@gmail.com, srikar@linux.vnet.ibm.com, haren@linux.vnet.ibm.com, jglisse@redhat.com, dave.hansen@intel.com, dan.j.williams@intel.com From: Anshuman Khandual Date: Tue, 31 Jan 2017 11:18:49 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <20170130033602.12275-1-khandual@linux.vnet.ibm.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 17013105-0016-0000-0000-000003D5BFBD X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 17013105-0017-0000-0000-000028B9CB4B Message-Id: <1e57493b-1981-7c36-612d-3ddaf6ca88b7@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-01-31_02:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1612050000 definitions=main-1701310054 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello Dave/Jerome/Mel, Here is the overall layout of the functions I am trying to put together through this patch series. (1) Define CDM from core VM and kernel perspective (2) Isolation/Special consideration for HugeTLB allocations (3) Isolation/Special consideration for buddy allocations (a) Zonelist modification based isolation (proposed) (b) Cpuset modification based isolation (proposed) (c) Buddy modification based isolation (working) (4) Define VMA containing CDM memory with a new flag VM_CDM (5) Special consideration for VM_CDM marked VMAs (a) Special consideration for auto NUMA (b) Special consideration for KSM Is there are any other area which needs to be taken care of before CDM node can be represented completely inside the kernel ? Regards Anshuman