Received: by 2002:a25:86ce:0:0:0:0:0 with SMTP id y14csp604443ybm; Mon, 20 May 2019 23:51:23 -0700 (PDT) X-Google-Smtp-Source: APXvYqynak7isB+McebLnlHFivbuJMKYuJtGCsoeTCUH0G4ID0k+KEt81ZTzC2TPH+tKpk6ZFHCp X-Received: by 2002:a17:902:bd8a:: with SMTP id q10mr32930272pls.155.1558421483697; Mon, 20 May 2019 23:51:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558421483; cv=none; d=google.com; s=arc-20160816; b=zIjaoiOrOtn3j5lpgMEU2lfnQ74SJ65LulVI802CL0iNxLmMkLTD/Gx8Sp2cDknxS3 U/rz9Re6MFZzDRrmJ6QhT3RAm/wi2ukrpWLIY8C6/BZSrkMY92rDvC2Hi96ejg3dG9Sy mGROigaslb+c25edIGONK9lj/XdNaQ/9GB2w5L/XViaIk3IBvjRGGGjGZuNOnW2t9kg3 DC4zH0KMVkj+SzvYKmJBCgopfkgnDXtRouy59NA9vH4sEnkEI86AetNzbpVGhFzWkJ20 z9Qgjqz8LHiZxXbKltHGkWaF42r9TVvUztIsD54sPL9UgQ+gV1r1Pmm2yQEAF9m756m4 L4tQ== 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; bh=2ZkDKgj8qrHt/EXBvP4noZlO8/k3KVLxkmXI+R6GJV0=; b=Ozm/PKyjPaX6PAU12fcpAnYY8MpqIDKY+EphMveX9E4F3P6rTA9Mab+tmlik2a82H6 6dDBuVrpuXRROkQUVT5lclZQQXLasDX7tMv2GoOclKQvkW1NWHfGUwurnAscjmfyeXTN kz/Rtsa2VqwryQPXdvM9AMXJAcTM1GlO5UqncE6gS0Uk83gFxziE/e87W7A9qjslJ2id Wbcm0sMTECfgV4BVDfqfYOZPm27Mr5RKS7V/E2hABf0bTNhOlGzg+z+WASiqjRBtw7GW ruMLLy3xXCjkyv6g8ov72fxM4v2eDaTU9pKdJdR00NtqpmbiHO2ThLUqIjRudWbt3zuZ MPLQ== 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 f6si17196670pga.225.2019.05.20.23.51.08; Mon, 20 May 2019 23:51:23 -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 S1726748AbfEUGuC (ORCPT + 99 others); Tue, 21 May 2019 02:50:02 -0400 Received: from mx2.suse.de ([195.135.220.15]:56762 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726193AbfEUGuC (ORCPT ); Tue, 21 May 2019 02:50:02 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 5C37FAF70; Tue, 21 May 2019 06:50:01 +0000 (UTC) Date: Tue, 21 May 2019 08:50:00 +0200 From: Michal Hocko To: Oleksandr Natalenko Cc: Minchan Kim , Andrew Morton , LKML , linux-mm , Johannes Weiner , Tim Murray , Joel Fernandes , Suren Baghdasaryan , Daniel Colascione , Shakeel Butt , Sonny Rao , Brian Geffon Subject: Re: [RFC 4/7] mm: factor out madvise's core functionality Message-ID: <20190521065000.GH32329@dhcp22.suse.cz> References: <20190520035254.57579-1-minchan@kernel.org> <20190520035254.57579-5-minchan@kernel.org> <20190520142633.x5d27gk454qruc4o@butterfly.localdomain> <20190521012649.GE10039@google.com> <20190521063628.x2npirvs75jxjilx@butterfly.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190521063628.x2npirvs75jxjilx@butterfly.localdomain> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue 21-05-19 08:36:28, Oleksandr Natalenko wrote: [...] > Regarding restricting the hints, I'm definitely interested in having > remote MADV_MERGEABLE/MADV_UNMERGEABLE. But, OTOH, doing it via remote > madvise() introduces another issue with traversing remote VMAs reliably. > IIUC, one can do this via userspace by parsing [s]maps file only, which > is not very consistent, and once some range is parsed, and then it is > immediately gone, a wrong hint will be sent. > > Isn't this a problem we should worry about? See http://lkml.kernel.org/r/20190520091829.GY6836@dhcp22.suse.cz -- Michal Hocko SUSE Labs