From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754004AbdDCQZE (ORCPT ); Mon, 3 Apr 2017 12:25:04 -0400 Received: from aserp1040.oracle.com ([141.146.126.69]:44161 "EHLO aserp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751803AbdDCQZD (ORCPT ); Mon, 3 Apr 2017 12:25:03 -0400 Subject: Re: [LSF/MM TOPIC][LSF/MM,ATTEND] shared TLB, hugetlb reservations To: Michal Hocko References: <20170403115137.GB24668@dhcp22.suse.cz> Cc: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org, linux-kernel From: Mike Kravetz Message-ID: Date: Mon, 3 Apr 2017 09:24:52 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <20170403115137.GB24668@dhcp22.suse.cz> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Source-IP: userv0022.oracle.com [156.151.31.74] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/03/2017 04:51 AM, Michal Hocko wrote: > On Wed 08-03-17 17:30:55, Mike Kravetz wrote: >> On 01/10/2017 03:02 PM, Mike Kravetz wrote: >>> Another more concrete topic is hugetlb reservations. Michal Hocko >>> proposed the topic "mm patches review bandwidth", and brought up the >>> related subject of areas in need of attention from an architectural >>> POV. I suggested that hugetlb reservations was one such area. I'm >>> guessing it was introduced to solve a rather concrete problem. However, >>> over time additional hugetlb functionality was added and the >>> capabilities of the reservation code was stretched to accommodate. >>> It would be good to step back and take a look at the design of this >>> code to determine if a rewrite/redesign is necessary. Michal suggested >>> documenting the current design/code as a first step. If people think >>> this is worth discussion at the summit, I could put together such a >>> design before the gathering. >> >> I attempted to put together a design/overview of how hugetlb reservations >> currently work. Hopefully, this will be useful. > > I am still too busy to read through this carefuly and provide a useful > feedback but I believe this should go int Documentation/vm/hugetlb$foo > file. Care to send it as a patch please? Sure There is some incomplete information in the document, so I will make some revisions and then send out as patch later this week. -- Mike Kravetz