From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-it0-f69.google.com (mail-it0-f69.google.com [209.85.214.69]) by kanga.kvack.org (Postfix) with ESMTP id 620506B0038 for ; Mon, 3 Apr 2017 12:25:01 -0400 (EDT) Received: by mail-it0-f69.google.com with SMTP id 8so37771408itg.6 for ; Mon, 03 Apr 2017 09:25:01 -0700 (PDT) Received: from aserp1040.oracle.com (aserp1040.oracle.com. [141.146.126.69]) by mx.google.com with ESMTPS id d91si15317397ioj.52.2017.04.03.09.25.00 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 03 Apr 2017 09:25:00 -0700 (PDT) Subject: Re: [LSF/MM TOPIC][LSF/MM,ATTEND] shared TLB, hugetlb reservations References: <20170403115137.GB24668@dhcp22.suse.cz> From: Mike Kravetz Message-ID: Date: Mon, 3 Apr 2017 09:24:52 -0700 MIME-Version: 1.0 In-Reply-To: <20170403115137.GB24668@dhcp22.suse.cz> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Michal Hocko Cc: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org, linux-kernel 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 -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org