From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <v.shpilevoy@tarantool.org>
Received: from smtp37.i.mail.ru (smtp37.i.mail.ru [94.100.177.97])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by dev.tarantool.org (Postfix) with ESMTPS id 2EDC846970E
 for <tarantool-patches@dev.tarantool.org>;
 Thu, 30 Jan 2020 00:59:54 +0300 (MSK)
References: <20200127193907.34019-1-georgy@tarantool.org>
 <20200129214839.GD31458@atlas>
From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Message-ID: <1a73267e-524f-e43e-e870-4709eb4a34a1@tarantool.org>
Date: Wed, 29 Jan 2020 22:59:52 +0100
MIME-Version: 1.0
In-Reply-To: <20200129214839.GD31458@atlas>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [Tarantool-patches] [PATCH] do not keep a slab in cache if new
 allocation does not fit
List-Id: Tarantool development patches <tarantool-patches.dev.tarantool.org>
List-Unsubscribe: <https://lists.tarantool.org/mailman/options/tarantool-patches>, 
 <mailto:tarantool-patches-request@dev.tarantool.org?subject=unsubscribe>
List-Archive: <https://lists.tarantool.org/pipermail/tarantool-patches/>
List-Post: <mailto:tarantool-patches@dev.tarantool.org>
List-Help: <mailto:tarantool-patches-request@dev.tarantool.org?subject=help>
List-Subscribe: <https://lists.tarantool.org/mailman/listinfo/tarantool-patches>, 
 <mailto:tarantool-patches-request@dev.tarantool.org?subject=subscribe>
To: Konstantin Osipov <kostja.osipov@gmail.com>, Georgy Kirichenko <georgy@tarantool.org>, tarantool-patches@dev.tarantool.org

Hi! Ok, will do after FOSDEM. If it won't be
pushed until that.

On 29/01/2020 22:48, Konstantin Osipov wrote:
> * Georgy Kirichenko <georgy@tarantool.org> [20/01/27 22:39]:
>> Do not allocate a new slab if there is a free slab in a region cache.
>> If a cached slab is not big enough then free it.
>>
>> Follow up 67d7ab44ab09df3356929e3692a03321b31f3ebb
>>
> 
> LGTM
> 
> Vlad, it would be nice if you do a second review, since this is 
> a fix in a stable release.
>