From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754075AbdDCQ5L (ORCPT ); Mon, 3 Apr 2017 12:57:11 -0400 Received: from mx2.suse.de ([195.135.220.15]:60847 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751441AbdDCQ5J (ORCPT ); Mon, 3 Apr 2017 12:57:09 -0400 Date: Mon, 3 Apr 2017 18:57:06 +0200 From: Michal Hocko To: Mike Kravetz Cc: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org, linux-kernel Subject: Re: [LSF/MM TOPIC][LSF/MM,ATTEND] shared TLB, hugetlb reservations Message-ID: <20170403165706.GR24661@dhcp22.suse.cz> References: <20170403115137.GB24668@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 03-04-17 09:24:52, Mike Kravetz wrote: > 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. Thanks a lot. This is highly appreciated! -- Michal Hocko SUSE Labs