All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Williamson <jwilliamson@suse.de>
To: Sage Weil <sage@newdream.net>
Cc: Allen Samuels <Allen.Samuels@sandisk.com>,
	Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Memory Pooling and Containers
Date: Wed, 28 Sep 2016 14:16:32 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LSU.2.20.1609281413450.13361@ancalagon.suse.de> (raw)
In-Reply-To: <alpine.DEB.2.11.1609281316210.19847@piezo.us.to>

On Wed, 28 Sep 2016, Sage Weil wrote:

> It would be nice to build this on top of existing allocator libraries if
> we can.  For example, something in boost.  I took a quick peek the other
> day and didn't find something that allowed simple interrogation about
> utilization, though, which was surprising.

Boost::pool look to me like it should fufill most of the requirements, but 
I haven't used it in production:
http://www.boost.org/doc/libs/1_62_0/libs/pool/doc/html/index.html

By "iterrogation about utilization", do you mean statistics about the 
allocator activity?

-Jesse

  parent reply	other threads:[~2016-09-28 21:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-27 20:30 Memory Pooling and Containers Allen Samuels
2016-09-27 23:00 ` Gregory Farnum
2016-09-28  9:13   ` Allen Samuels
2016-09-28 13:16   ` Sage Weil
2016-09-28 13:27 ` Sage Weil
2016-09-28 13:34   ` Haomai Wang
2016-09-28 15:56     ` Allen Samuels
2016-09-28 19:39     ` Allen Samuels
2016-09-28 15:56   ` Allen Samuels
2016-09-28 21:16   ` Jesse Williamson [this message]
2016-09-28 21:31     ` Allen Samuels
2016-09-30 14:22       ` Sage Weil
2016-09-30 14:30         ` Allen Samuels
2016-09-30 21:47           ` Jesse Williamson
2016-09-30 18:54         ` Gregory Farnum

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LSU.2.20.1609281413450.13361@ancalagon.suse.de \
    --to=jwilliamson@suse.de \
    --cc=Allen.Samuels@sandisk.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sage@newdream.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.