Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp28069imm; Mon, 2 Jul 2018 07:08:28 -0700 (PDT) X-Google-Smtp-Source: AAOMgpdO4aoJLnvDSBzHIUKkMwT8XrFQHSlbeiv4e5yspoQpXB/YRPoiRr+eClOk53p7cEKCspvt X-Received: by 2002:a63:ff21:: with SMTP id k33-v6mr1060186pgi.38.1530540508624; Mon, 02 Jul 2018 07:08:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1530540508; cv=none; d=google.com; s=arc-20160816; b=d1w0y3BkDNg5PSZ3v7wwdwvWJ2GEsEcZ7+dOmCl85Ad7y71j2rVjgbml1p8paIXezh 0YLEaxxCuvDxDykHkZUge3UsQ78xDeJL7CZUkpT0QaF39gQYlDZgmIxyarw5dg343uKe Du8S5KXUFQHbkzWglX/dTaVp+v65cuqdKf404f7OsZBbdmc6vJsA5qzs6g/Z5ZabEqa8 3vFriKTqkK2OR98ZYDSpJVTirYsjQWnS3ARZB8Rc/hlLN9Ff5/meGDfOzTN53Ft5PkQb c398F3gXlfA5VCbu57QCHU7TGp1De/MTiE8QyN3KcExf52akb6xa7D6LJU6aFEAI2I+g KPng== 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:arc-authentication-results; bh=LJU9tzHlWISGtz1+2/aNdfCP8vtYe8TE0caSINIbKd8=; b=vI37ziBczhQ6QfNN41NIMTkRRwOeuKH/OTsBhJmdo4yn3rA9UEPo6TsEd1UBv/L12i 7oqC9nKjR8LZUkqpgM2Ct/bcSwpI5zWQGKgpc028mQnErxYuZO907pFCa3ZteSVdYc8f sqSxxGtpZQkCtlHIbJR+XFLFD3g3u8bwQhbA13Vf7a2eNRuNUK1UzCE/4jvbPRdGc31C Mavj+DMf30QAdaHOtIjvACP3PW8wLnS57aLAfFp2/IbMNNDCKmL2b88426uIMW7G7a8/ gUsbSEkD6d1ynEE4skGKLfgwXcI6X5HfSekYjy5s97KnozF7AWjX3ITRQFuIAKsuvciV 5iZg== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j66-v6si16511784pfc.243.2018.07.02.07.08.13; Mon, 02 Jul 2018 07:08:28 -0700 (PDT) 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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752492AbeGBOFO (ORCPT + 99 others); Mon, 2 Jul 2018 10:05:14 -0400 Received: from mx2.suse.de ([195.135.220.15]:51512 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752355AbeGBOFF (ORCPT ); Mon, 2 Jul 2018 10:05:05 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay1.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 5034CAD26; Mon, 2 Jul 2018 14:05:04 +0000 (UTC) Date: Mon, 2 Jul 2018 16:05:02 +0200 From: Michal Hocko To: Andrew Morton Cc: Yang Shi , willy@infradead.org, ldufour@linux.vnet.ibm.com, peterz@infradead.org, mingo@redhat.com, acme@kernel.org, alexander.shishkin@linux.intel.com, jolsa@redhat.com, namhyung@kernel.org, tglx@linutronix.de, hpa@zytor.com, linux-mm@kvack.org, x86@kernel.org, linux-kernel@vger.kernel.org Subject: Re: [RFC v3 PATCH 4/5] mm: mmap: zap pages with read mmap_sem for large mapping Message-ID: <20180702140502.GZ19043@dhcp22.suse.cz> References: <1530311985-31251-1-git-send-email-yang.shi@linux.alibaba.com> <1530311985-31251-5-git-send-email-yang.shi@linux.alibaba.com> <20180629183501.9e30c26135f11853245c56c7@linux-foundation.org> <084aeccb-2c54-2299-8bf0-29a10cc0186e@linux.alibaba.com> <20180629201547.5322cfc4b52d19a0443daec2@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180629201547.5322cfc4b52d19a0443daec2@linux-foundation.org> User-Agent: Mutt/1.10.0 (2018-05-17) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri 29-06-18 20:15:47, Andrew Morton wrote: [...] > Would one of your earlier designs have addressed all usecases? I > expect the dumb unmap-a-little-bit-at-a-time approach would have? It has been already pointed out that this will not work. You simply cannot drop the mmap_sem during unmap because another thread could change the address space under your feet. So you need some form of VM_DEAD and handle concurrent and conflicting address space operations. -- Michal Hocko SUSE Labs