<HTML><BODY><div>From memtx_tuple_new() we call smalloc(). In case it is calling<br>mempool_alloc(), we are passing the pool from memtx->alloc, chosen<br>depending on it's size. Later this tuple may be deleted. Then smfree()<br>is called, which uses mempool_find() to acquire the pool we want to<br>free.<br>In case we are using some other specific pool, current mempool_find()<br>won't be able to find it. This means we need to process this case<br>explicitly and it seems to add noticeable unjustified complexity to the<br>code.<br><br> <blockquote style="border-left:1px solid #0857A6; margin:10px; padding:0 0 0 10px;">Четверг, 6 февраля 2020, 17:29 +03:00 от Konstantin Osipov <kostja.osipov@gmail.com>:<br> <div id=""><div class="js-helper js-readmsg-msg"><style type="text/css"></style><div><div id="style_15809993771824684336_BODY">* Ilya Kosarev <<a href="/compose?To=i.kosarev@tarantool.org">i.kosarev@tarantool.org</a>> [20/02/06 13:51]:<br>><br>> Well, the problem here is that garbage collection won't work properly<br>> in this case.<br><br>I don't understand what GC has to do with it. Please clarify.<br><br>> I guess it can be adjusted, however, there will be some<br>> kind of crutches and it doesn't seem to be a good idea. Just switching<br>> quota on and off seems to be more suitable and convenient for<br>> truncations and deletions.<br>> <br><br>--<br>Konstantin Osipov, Moscow, Russia</div></div></div></div></blockquote> <div> </div><div data-signature-widget="container"><div data-signature-widget="content"><div>--<br>Ilya Kosarev</div></div></div><div> </div></div></BODY></HTML>