Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp223511imu; Tue, 27 Nov 2018 11:23:40 -0800 (PST) X-Google-Smtp-Source: AFSGD/V/FPqpfo9npyvc/dxXFrPKi5yEAAkY/6EA4LbS0xzznGlzu7Kc2xHxHO+pIl2kgjCONlJS X-Received: by 2002:a63:3858:: with SMTP id h24mr29563756pgn.300.1543346619831; Tue, 27 Nov 2018 11:23:39 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1543346619; cv=none; d=google.com; s=arc-20160816; b=Zy+80aLFYhhAxqUGRUMzP5VrXvb19wpIRuA3KV4DYGiWahRNhAH2AJlvEOMQrd/mmD iX+hgGrZIfmKESfzXd/UCMQMd2x4NMvpiXPwxwQn4otfaAcn+UVVY49gI77F2dUWnNnS JHDK1UfQZJxC/mkqVH1ICQ/xQnyVV+cQHUjjh0oBrgGNoyqlx+x/A1LdNWLyNgDlmO+L 8vircjAHJ2KFQiIEJatsk/ZjzFbROCnxkTkbx+aF7sXMa++WQiOef0b4OmBjjKCTxObx k+q5/fj1Q6DpuJjwDUaVkLqZjdZ7QGiPJF/pQiO+rB1XHFOheuSHnNFT2+ZFrZ9QTKmY EA7w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:to:references:message-id :content-transfer-encoding:cc:date:in-reply-to:from:subject :mime-version:dkim-signature; bh=oyccUdWIelEWKpwjvGBKca5PSCy0iL8os39pB4V7K4A=; b=CwAv/yApWrEtyn6d4LFSXrcoHerjIh6Ej6nH93LHwuK0ROvnbtDCTryR3AFjMRmwUs p0U89ccKLp4QjG5QL2n253avcmQrxh9EblhWkeSd3En3D5r+qiRT1Q5DLnzu2S7NONqp 5CQlvlr4tQv7qHKnCHZo83zLBaKUPcRPrsYQGCn0PsS1BfmDSq8VACTpU+97O+FF5lmj 3xOlokOz/ZHWSx75LUxSCzksdA2KFFq8YvMDSgMurcOtt/SLqGBsWVml25uh7kIbExuW a3Wvl/Kqfnek2/M0a3qasGsuJ/eFaf0kJ7aBO0AUUL/Fih9xB7RQ7FvfsM13uyIp6UHc YDAg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@oracle.com header.s=corp-2018-07-02 header.b=e6x7WjVE; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=oracle.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g10-v6si633235plt.321.2018.11.27.11.23.24; Tue, 27 Nov 2018 11:23:39 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@oracle.com header.s=corp-2018-07-02 header.b=e6x7WjVE; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=oracle.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728366AbeK1BsY (ORCPT + 99 others); Tue, 27 Nov 2018 20:48:24 -0500 Received: from userp2130.oracle.com ([156.151.31.86]:47276 "EHLO userp2130.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726299AbeK1BsY (ORCPT ); Tue, 27 Nov 2018 20:48:24 -0500 Received: from pps.filterd (userp2130.oracle.com [127.0.0.1]) by userp2130.oracle.com (8.16.0.22/8.16.0.22) with SMTP id wAREmd4P009606; Tue, 27 Nov 2018 14:50:11 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=content-type : mime-version : subject : from : in-reply-to : date : cc : content-transfer-encoding : message-id : references : to; s=corp-2018-07-02; bh=oyccUdWIelEWKpwjvGBKca5PSCy0iL8os39pB4V7K4A=; b=e6x7WjVEvtRFfA0tSUmiNT0L5SnP9kIXSZrjt4r4mOIqhw54Wt9ORZbquCAssrYcl3pa cfTnNlFIN77rJdZ3RXSe+5CfjgSPrZPWtAwhRXkzCt6JfZjsyBNXwhkEgCMfKaLlR58p tyPO7FNhiW8SIjJeaTVfZx44YaaP+hWpJhd60fxCPxCh7tUg+Iz9VJtqqeqf/MRTDsM/ jH8Dv10fMo+2N5ki1SgTQaz5ZdK/hsbPp1PKf2pqABf0s0HK2ifDNPsRolQsSpOli3ob yMWPKXXkfG2HCnDF0K0BIsdVfCVaP66+8Ju/JkKKg6ovXbCY8Erk8nal2k/ltGNJotQC FQ== Received: from aserv0021.oracle.com (aserv0021.oracle.com [141.146.126.233]) by userp2130.oracle.com with ESMTP id 2nxx2u4e35-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 27 Nov 2018 14:50:10 +0000 Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by aserv0021.oracle.com (8.14.4/8.14.4) with ESMTP id wAREo9iu027744 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 27 Nov 2018 14:50:10 GMT Received: from abhmp0004.oracle.com (abhmp0004.oracle.com [141.146.116.10]) by aserv0121.oracle.com (8.14.4/8.13.8) with ESMTP id wAREo9w6000653; Tue, 27 Nov 2018 14:50:09 GMT Received: from [192.168.0.110] (/73.243.10.6) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 27 Nov 2018 06:50:09 -0800 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) Subject: Re: [RFC PATCH 3/3] mm, proc: report PR_SET_THP_DISABLE in proc From: William Kucharski In-Reply-To: <20181127131707.GW12455@dhcp22.suse.cz> Date: Tue, 27 Nov 2018 07:50:08 -0700 Cc: linux-api@vger.kernel.org, Andrew Morton , Alexey Dobriyan , linux-mm@kvack.org, LKML Content-Transfer-Encoding: 7bit Message-Id: <04647F77-FE93-4A8E-90C1-4245709B88A5@oracle.com> References: <20181120103515.25280-1-mhocko@kernel.org> <20181120103515.25280-4-mhocko@kernel.org> <0ACDD94B-75AD-4DD0-B2E3-32C0EDFBAA5E@oracle.com> <20181127131707.GW12455@dhcp22.suse.cz> To: Michal Hocko X-Mailer: Apple Mail (2.3445.102.3) X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=9089 signatures=668685 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=631 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1811270128 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > On Nov 27, 2018, at 6:17 AM, Michal Hocko wrote: > > This is only about the process wide flag to disable THP. I do not see > how this can be alighnement related. I suspect you wanted to ask in the > smaps patch? No, answered below. > >> I'm having to deal with both these issues in the text page THP >> prototype I've been working on for some time now. > > Could you be more specific about the issue and how the alignment comes > into the game? The only thing I can think of is to not report VMAs > smaller than the THP as eligible. Is this what you are looking for? Basically, if the faulting VA is one that cannot be mapped with a THP due to alignment or size constraints, it may be "eligible" for THP mapping but ultimately can't be. I was just double checking that this was meant to be more of a check done before code elsewhere performs additional checks and does the actual THP mapping, not an all-encompassing go/no go check for THP mapping. Thanks, William Kucharski