Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp190224imj; Thu, 14 Feb 2019 18:19:04 -0800 (PST) X-Google-Smtp-Source: AHgI3IalmAuXUw5XZ2r+jJ0dSIlYHNkJ5GBXFjUeDnL73QaDdk4kRpjihwPalCTAOxxCcLlMANeA X-Received: by 2002:a62:9604:: with SMTP id c4mr7375050pfe.200.1550197144713; Thu, 14 Feb 2019 18:19:04 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550197144; cv=none; d=google.com; s=arc-20160816; b=Aq2x4pvy0UgDf/I59IPD+NyynhCqCs3D9UOKXUOqv7Ry3gyb6SMnJBG53rkvFItsT3 dCUQGTdHW03unuw1Zr5EA1zKuh3g/lDmVbucxoVfyZAr4u3G9MZTQig7d3Yas6AyfG+x vb0/tj4Xb8cLA72I4CishvXkzpEn643/8c8tiouVtsBf7Unn66EN8lJIf/9wol0TUV+a UorJwxrg4+/SA9dcGsiJ1b9Q70YvTGaEi5r5n9+WMQqfQ9mJGE+LU5LSAi/bQSxmUO65 vF8+hxSC9GgGSR9ijPhf5w70c8R5rO+STEhcboNusPn6x7i9Me2cUSxWr6LYTUtw3Raj z8cA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=t1hVwJWaLn2x3podPvX+xTLteVECyauDZZjQoDe0D+0=; b=nXjuUJl78fB3nrgIsWhRtdtjXzxghb5+mNn1oBEJ6yhNmAKdXOw+iuFLJlJvbuHstE 4p+Ezg7nRBtq7bRqLkkKKFVhXwGxaclMq8h3zp4khAkIQ1slHvAYruC1DZgYu0kAgAYl UFP0hjE5Vxr+CgnkrHPlGAvJrV800vu23VrNAt96P+1/LzWRLd+9DuDFN4aGhEZXZh/F msp1EPYj1oT7GFZTYdQmA0HL/0OHFMay8PaOQy/wqOw7RkyXgBw/kb75Tsv+p//jaU6X fhNMjdoClgnB7SKxfgCGp4QUk9DZiY2IOKq/luJIFf27Sd0ipE3xeO8bKDdF3oqKHC0v S/FQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ziepe.ca header.s=google header.b=EmWX0F+U; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id bd12si4024163plb.193.2019.02.14.18.18.48; Thu, 14 Feb 2019 18:19:04 -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=@ziepe.ca header.s=google header.b=EmWX0F+U; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2438281AbfBNWQd (ORCPT + 99 others); Thu, 14 Feb 2019 17:16:33 -0500 Received: from mail-pg1-f193.google.com ([209.85.215.193]:45900 "EHLO mail-pg1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388126AbfBNWQc (ORCPT ); Thu, 14 Feb 2019 17:16:32 -0500 Received: by mail-pg1-f193.google.com with SMTP id y4so3749705pgc.12 for ; Thu, 14 Feb 2019 14:16:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ziepe.ca; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=t1hVwJWaLn2x3podPvX+xTLteVECyauDZZjQoDe0D+0=; b=EmWX0F+U8QlHwgyOQyU7/GpC3WglrqT05XbL6OtUXhmICyYGqD//fSe0HIl+i8ygVj KLImM7wLgwqYgwHC38M8+IdJpGvQF7STuPF4slPbpqRbJi4onN9XO0pxqn7viPOReHoA yD50Kc68GMkGWx3uRxx22P3bY9gTYJmFuwYuPUXwzZF+V0RVlVT+vctp2K+b0qkFvJIn S42lTYn684RC3NIapzX5v7GhbOGbCpPUAGz94OauM4EFokmqxeIVwCBS8XRmddSLSnkA XfaqPTxJ+62cn994jdfrHXkNizC58LofY5+68+iTjn1jXJqa3vqLrTUAPaCHMxON+wdK 8Qsw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=t1hVwJWaLn2x3podPvX+xTLteVECyauDZZjQoDe0D+0=; b=gPILtj8hsNwSYZCIgdEUcTbVI/POM9y23jbXKfy3Yz/+lklgo+m7EMoxEqXZXOZM0T Nw4iGMO9mwyPM2nndfrDW0uxuoUko/GRpf2kb4RRlOBSl+I4Xyxxy34e4A2ZZJQD3ojO 8rzA4gt76LAvB+sLcwYzj5HE2a/S9udOyLPi9uTs0F2NiGzWmDcPIWjI1mdsW0sidpxE n2WFQGE9m2RYKAd9Oqstsbj6bL5ZBtpd+/4aMpPGBPkc4kpMjnlGHK8chdeArnXVm0A6 snoghCMXKwm7iSxRtl6JNyFTC3USFJqRnpgJIn0Iol4hD2QigAKC9wprXw2RDDNK2oJK xZ7A== X-Gm-Message-State: AHQUAuY2OYnQj746wVvJP4xgn8DaJQeK0D3nKF0egOuj9WBCOBemCG8L CWHvluBCDCx82N4ShVhGrsMgug== X-Received: by 2002:a65:6249:: with SMTP id q9mr2077195pgv.229.1550182591612; Thu, 14 Feb 2019 14:16:31 -0800 (PST) Received: from ziepe.ca (S010614cc2056d97f.ed.shawcable.net. [174.3.196.123]) by smtp.gmail.com with ESMTPSA id l73sm7556152pfb.113.2019.02.14.14.16.30 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 14 Feb 2019 14:16:30 -0800 (PST) Received: from jgg by mlx.ziepe.ca with local (Exim 4.90_1) (envelope-from ) id 1guPIz-0005gz-UH; Thu, 14 Feb 2019 15:16:29 -0700 Date: Thu, 14 Feb 2019 15:16:29 -0700 From: Jason Gunthorpe To: Ira Weiny Cc: Daniel Jordan , akpm@linux-foundation.org, dave@stgolabs.net, jack@suse.cz, cl@linux.com, linux-mm@kvack.org, kvm@vger.kernel.org, kvm-ppc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-fpga@vger.kernel.org, linux-kernel@vger.kernel.org, alex.williamson@redhat.com, paulus@ozlabs.org, benh@kernel.crashing.org, mpe@ellerman.id.au, hao.wu@intel.com, atull@kernel.org, mdf@kernel.org, aik@ozlabs.ru Subject: Re: [PATCH 0/5] use pinned_vm instead of locked_vm to account pinned pages Message-ID: <20190214221629.GD1739@ziepe.ca> References: <20190211224437.25267-1-daniel.m.jordan@oracle.com> <20190211225447.GN24692@ziepe.ca> <20190214015314.GB1151@iweiny-DESK2.sc.intel.com> <20190214060006.GE24692@ziepe.ca> <20190214193352.GA7512@iweiny-DESK2.sc.intel.com> <20190214201231.GC1739@ziepe.ca> <20190214214650.GB7512@iweiny-DESK2.sc.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190214214650.GB7512@iweiny-DESK2.sc.intel.com> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 14, 2019 at 01:46:51PM -0800, Ira Weiny wrote: > > > > Really unclear how to fix this. The pinned/locked split with two > > > > buckets may be the right way. > > > > > > Are you suggesting that we have 2 user limits? > > > > This is what RDMA has done since CL's patch. > > I don't understand? What is the other _user_ limit (other than > RLIMIT_MEMLOCK)? With todays implementation RLIMIT_MEMLOCK covers two user limits, total number of pinned pages and total number of mlocked pages. The two are different buckets and not summed. Jason