From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751156AbdK3TBZ (ORCPT ); Thu, 30 Nov 2017 14:01:25 -0500 Received: from mail-wr0-f196.google.com ([209.85.128.196]:35611 "EHLO mail-wr0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750921AbdK3TBX (ORCPT ); Thu, 30 Nov 2017 14:01:23 -0500 X-Google-Smtp-Source: AGs4zMa7FzYhZOUABpvfibIWi+5+8IiD+BSpBJ+GFfTFg4Do68TYFVgaabYbbvYWHEJmI60KugTvsw== Date: Thu, 30 Nov 2017 12:01:17 -0700 From: Jason Gunthorpe To: Dan Williams Cc: Michal Hocko , Andrew Morton , Linux MM , "linux-kernel@vger.kernel.org" , Christoph Hellwig , "stable@vger.kernel.org" , "linux-nvdimm@lists.01.org" , linux-rdma Subject: Re: [PATCH v3 1/4] mm: introduce get_user_pages_longterm Message-ID: <20171130190117.GF7754@ziepe.ca> References: <151197872943.26211.6551382719053304996.stgit@dwillia2-desk3.amr.corp.intel.com> <151197873499.26211.11687422577653326365.stgit@dwillia2-desk3.amr.corp.intel.com> <20171130095323.ovrq2nenb6ztiapy@dhcp22.suse.cz> <20171130174201.stbpuye4gu5rxwkm@dhcp22.suse.cz> <20171130181741.2y5nyflyhqxg6y5p@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Nov 30, 2017 at 10:32:42AM -0800, Dan Williams wrote: > > Who and how many LRU pages can pin that way and how do you prevent nasty > > users to DoS systems this way? > > I assume this is something the RDMA community has had to contend with? > I'm not an RDMA person, I'm just here to fix dax. The RDMA implementation respects the mlock rlimit Jason