From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752632AbcLRXeW (ORCPT ); Sun, 18 Dec 2016 18:34:22 -0500 Received: from aserp1040.oracle.com ([141.146.126.69]:16629 "EHLO aserp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751347AbcLRXeV (ORCPT ); Sun, 18 Dec 2016 18:34:21 -0500 Subject: Re: [RFC PATCH 02/14] sparc64: add new fields to mmu context for shared context support To: Sam Ravnborg References: <1481913337-9331-1-git-send-email-mike.kravetz@oracle.com> <1481913337-9331-3-git-send-email-mike.kravetz@oracle.com> <20161217073406.GA23567@ravnborg.org> Cc: sparclinux@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, "David S . Miller" , Bob Picco , Nitin Gupta , Vijay Kumar , Julian Calaby , Adam Buchbinder , "Kirill A . Shutemov" , Michal Hocko , Andrew Morton From: Mike Kravetz Message-ID: Date: Sun, 18 Dec 2016 15:33:59 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <20161217073406.GA23567@ravnborg.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Source-IP: aserv0021.oracle.com [141.146.126.233] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/16/2016 11:34 PM, Sam Ravnborg wrote: > Hi Mike. > > On Fri, Dec 16, 2016 at 10:35:25AM -0800, Mike Kravetz wrote: >> Add new fields to the mm_context structure to support shared context. >> Instead of a simple context ID, add a pointer to a structure with a >> reference count. This is needed as multiple tasks will share the >> context ID. > > What are the benefits with the shared_mmu_ctx struct? > It does not save any space in mm_context_t, and the CPU only > supports one extra context. > So it looks like over-engineering with all the extra administration > required to handle it with refcount, poitners etc. > > what do I miss? Multiple tasks will share this same context ID. The first task to need a new shared context will allocate the structure, increment the ref count and point to it. As other tasks join the sharing, they will increment the ref count and point to the same structure. Similarly, when tasks no longer use the shared context ID, they will decrement the reference count. The reference count is important so that we will know when the last reference to the shared context ID is dropped. When the last reference is dropped, then the ID can be recycled/given back to the global pool of context IDs. This seemed to be the most straight forward way to implement this. -- Mike Kravetz