From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <kostja.osipov@gmail.com>
Received: from mail-lf1-f65.google.com (mail-lf1-f65.google.com
 [209.85.167.65])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by dev.tarantool.org (Postfix) with ESMTPS id A9E44469719
 for <tarantool-patches@dev.tarantool.org>;
 Fri, 21 Feb 2020 10:15:02 +0300 (MSK)
Received: by mail-lf1-f65.google.com with SMTP id s23so700004lfs.10
 for <tarantool-patches@dev.tarantool.org>;
 Thu, 20 Feb 2020 23:15:02 -0800 (PST)
Date: Fri, 21 Feb 2020 10:15:00 +0300
From: Konstantin Osipov <kostja.osipov@gmail.com>
Message-ID: <20200221071500.GB15098@atlas>
References: <20200214132220.29830-1-gorcunov@gmail.com>
 <20200214132220.29830-3-gorcunov@gmail.com>
 <20200214141704.GA10968@atlas> <20200214142220.GY21061@uranus>
 <20200214142919.GB10968@atlas> <20200214143135.GZ21061@uranus>
 <20200220210026.tdicjidbhky3guvu@tkn_work_nb>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20200220210026.tdicjidbhky3guvu@tkn_work_nb>
Subject: Re: [Tarantool-patches] [PATCH v8 2/2] fiber: leak slab if unable
 to bring prots back
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: Alexander Turenko <alexander.turenko@tarantool.org>
Cc: tml <tarantool-patches@dev.tarantool.org>, Vladislav Shpilevoy <v.shpilevoy@tarantool.org>

* Alexander Turenko <alexander.turenko@tarantool.org> [20/02/21 00:02]:

It's a complicated matter which has a lot of options.

One option is to do nothing, btw, there is a system-wide
workaround - increase /proc/sys/vm/max_map_count - just document
it.


-- 
Konstantin Osipov, Moscow, Russia