From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.25.44.205 with SMTP id s196mr2849923lfs.3.1466516352640; Tue, 21 Jun 2016 06:39:12 -0700 (PDT) X-Received: by 10.157.37.168 with SMTP id q37mr676104ota.13.1466516352549; Tue, 21 Jun 2016 06:39:12 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!goblin1!goblin.stu.neva.ru!oe3no7003211lbb.1!news-out.google.com!f5ni27513lbb.0!nntp.google.com!w10no5204487lbo.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Tue, 21 Jun 2016 06:39:12 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=198.135.236.252; posting-account=ENgozAkAAACH-stq5yXctoDQeZQP2E6J NNTP-Posting-Host: 198.135.236.252 References: <66c14298-c62d-4f4b-b0c0-e969454f9334@googlegroups.com> <4da8ad8e-f6b4-46b3-b81d-b255c030a45c@googlegroups.com> <6100770a-774c-41a7-b1d9-498f80426835@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <9fbca33f-6663-422d-aeeb-9a116d0d00c8@googlegroups.com> Subject: Re: Generic Embedded List Nodes From: Warren Injection-Date: Tue, 21 Jun 2016 13:39:12 +0000 Content-Type: text/plain; charset=UTF-8 Xref: news.eternal-september.org comp.lang.ada:30857 Date: 2016-06-21T06:39:12-07:00 List-Id: On Tuesday, 21 June 2016 07:57:12 UTC-4, Dmitry A. Kazakov wrote: > On 21/06/2016 12:32, Warren wrote: > > On Tuesday, 21 June 2016 03:22:11 UTC-4, Dmitry A. Kazakov wrote: > >> On 21/06/2016 04:28, Warren wrote: > >> > >>> Also any use of malloc/free where > >>> possible must be avoided because these are performance killers (even > >>> when using jremalloc). > >> > >> That is no problem, if node life cycle is known a custom pool deploying > >> a FIFO arena in some chunk of memory is used. > > > > My C++ implementation maintains a pool of objects. But I want to > > combine Node and Object as one. > > No problem either. The pool takes care of that. That's not completely true- you would have the overhead of TWO pools, instead of one. Warren