From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754478AbdGJQg6 (ORCPT ); Mon, 10 Jul 2017 12:36:58 -0400 Received: from mx2.suse.de ([195.135.220.15]:37678 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754059AbdGJQg4 (ORCPT ); Mon, 10 Jul 2017 12:36:56 -0400 Date: Mon, 10 Jul 2017 18:36:52 +0200 From: Michal Hocko To: Jerome Glisse Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, John Hubbard , David Nellans , Dan Williams , Balbir Singh , Johannes Weiner , Vladimir Davydov , cgroups@vger.kernel.org Subject: Re: [PATCH 4/5] mm/memcontrol: allow to uncharge page without using page->lru field Message-ID: <20170710163651.GD7071@dhcp22.suse.cz> References: <20170703211415.11283-1-jglisse@redhat.com> <20170703211415.11283-5-jglisse@redhat.com> <20170704125113.GC14727@dhcp22.suse.cz> <20170705143528.GB3305@redhat.com> <20170710082805.GD19185@dhcp22.suse.cz> <20170710153222.GA4964@redhat.com> <20170710160444.GB7071@dhcp22.suse.cz> <20170710162542.GB4964@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170710162542.GB4964@redhat.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon 10-07-17 12:25:42, Jerome Glisse wrote: [...] > Bottom line is that we can always free and uncharge device memory > page just like any regular page. OK, this answers my earlier question. Then it should be feasible to charge this memory. There are still some things to handle. E.g. how do we consider this memory during oom victim selection (this is not accounted as an anonymous memory in get_mm_counter, right?), maybe others. But the primary point is that nobody pins the memory outside of the mapping. -- Michal Hocko SUSE Labs