From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: [PATCH v3 4/4] mm: Adaptive hash table scaling To: Michal Hocko Cc: Andrew Morton , linux-mm@kvack.org, sparclinux@vger.kernel.org, linux-fsdevel@vger.kernel.org, Al Viro References: <1488432825-92126-1-git-send-email-pasha.tatashin@oracle.com> <1488432825-92126-5-git-send-email-pasha.tatashin@oracle.com> <20170303153247.f16a31c95404c02a8f3e2c5f@linux-foundation.org> <20170426201126.GA32407@dhcp22.suse.cz> <40f72efa-3928-b3c6-acca-0740f1a15ba4@oracle.com> <429c8506-c498-0599-4258-7bac947fe29c@oracle.com> <20170505133029.GC31461@dhcp22.suse.cz> From: Pasha Tatashin Message-ID: Date: Fri, 5 May 2017 11:33:36 -0400 MIME-Version: 1.0 In-Reply-To: <20170505133029.GC31461@dhcp22.suse.cz> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: On 05/05/2017 09:30 AM, Michal Hocko wrote: > On Thu 04-05-17 14:28:51, Pasha Tatashin wrote: >> BTW, I am OK with your patch on top of this "Adaptive hash table" patch, but >> I do not know what high_limit should be from where HASH_ADAPT will kick in. >> 128M sound reasonable to you? > > For simplicity I would just use it unconditionally when no high_limit is > set. What would be the problem with that? Sure, that sounds good. If you look at current users > (and there no new users emerging too often) then most of them just want > _some_ scaling. The original one obviously doesn't scale with large > machines. Are you OK to fold my change to your patch or you want me to > send a separate patch? AFAIK Andrew hasn't posted this patch to Linus > yet. > I would like a separate patch because mine has soaked in mm tree for a while now. Thank you, Pasha -- 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pasha Tatashin Date: Fri, 05 May 2017 15:33:36 +0000 Subject: Re: [PATCH v3 4/4] mm: Adaptive hash table scaling Message-Id: List-Id: References: <1488432825-92126-1-git-send-email-pasha.tatashin@oracle.com> <1488432825-92126-5-git-send-email-pasha.tatashin@oracle.com> <20170303153247.f16a31c95404c02a8f3e2c5f@linux-foundation.org> <20170426201126.GA32407@dhcp22.suse.cz> <40f72efa-3928-b3c6-acca-0740f1a15ba4@oracle.com> <429c8506-c498-0599-4258-7bac947fe29c@oracle.com> <20170505133029.GC31461@dhcp22.suse.cz> In-Reply-To: <20170505133029.GC31461@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Michal Hocko Cc: Andrew Morton , linux-mm@kvack.org, sparclinux@vger.kernel.org, linux-fsdevel@vger.kernel.org, Al Viro On 05/05/2017 09:30 AM, Michal Hocko wrote: > On Thu 04-05-17 14:28:51, Pasha Tatashin wrote: >> BTW, I am OK with your patch on top of this "Adaptive hash table" patch, but >> I do not know what high_limit should be from where HASH_ADAPT will kick in. >> 128M sound reasonable to you? > > For simplicity I would just use it unconditionally when no high_limit is > set. What would be the problem with that? Sure, that sounds good. If you look at current users > (and there no new users emerging too often) then most of them just want > _some_ scaling. The original one obviously doesn't scale with large > machines. Are you OK to fold my change to your patch or you want me to > send a separate patch? AFAIK Andrew hasn't posted this patch to Linus > yet. > I would like a separate patch because mine has soaked in mm tree for a while now. Thank you, Pasha