All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Williamson <jwilliamson@suse.de>
To: Allen Samuels <Allen.Samuels@sandisk.com>
Cc: Sage Weil <sage@newdream.net>,
	Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Memory Pooling and Containers
Date: Fri, 30 Sep 2016 14:47:05 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LSU.2.20.1609301112330.8582@ancalagon.suse.de> (raw)
In-Reply-To: <0AA35578-9667-4B81-BE6A-71C8326B76F1@sandisk.com>

On Fri, 30 Sep 2016, Allen Samuels wrote:

> I'm expecting the "in-object" capabilities of the slab_xxxxx containers 
> to dramatically reduce malloc/free calls. Also having some visibility 
> into where the memory is actually going will also spur a bit more 
> development that will likely have more significant positive effects.

Definitely sounds useful! I see that some works been done with massif, 
too.

Also, I took a quick peek into boost::pool. It's built exactly as you 
said-- specifically for the manu-small-objects situation. I didn't see an 
"obvious" way to hook in a new freelist scheme.

Have a great weekend,

-Jesse


  reply	other threads:[~2016-09-30 21:47 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
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 [this message]
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.1609301112330.8582@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.