All of lore.kernel.org
 help / color / mirror / Atom feed
From: Allen Samuels <Allen.Samuels@sandisk.com>
To: Gregory Farnum <gfarnum@redhat.com>
Cc: Sage Weil <sage@newdream.net>,
	Ceph Development <ceph-devel@vger.kernel.org>
Subject: RE: Memory Pooling and Containers
Date: Wed, 28 Sep 2016 09:13:32 +0000	[thread overview]
Message-ID: <BLUPR0201MB1524DEE54B0808968D29E3DBE8CF0@BLUPR0201MB1524.namprd02.prod.outlook.com> (raw)
In-Reply-To: <CAJ4mKGYQLrP_Z28iitj9Vwt3dSfVp2yQ3bnGt2jcTC9LahnvUg@mail.gmail.com>

Should work in any C++ context -- nothing that's BlueStore dependent.


Allen Samuels
SanDisk |a Western Digital brand
2880 Junction Avenue, San Jose, CA 95134
T: +1 408 801 7030| M: +1 408 780 6416
allen.samuels@SanDisk.com


> -----Original Message-----
> From: Gregory Farnum [mailto:gfarnum@redhat.com]
> Sent: Wednesday, September 28, 2016 1:01 AM
> 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
> 
> On Tue, Sep 27, 2016 at 1:30 PM, Allen Samuels
> <Allen.Samuels@sandisk.com> wrote:
> > As we discussed in the Bluestore standup this morning. This is intended to
> start a discussion about creating some internal memory pooling technology
> to try to get a better handle on the internal usage of memory by Ceph. Let's
> start by discussing the requirements...
> 
> I'm afraid I don't have any useful thoughts on this, but I'm curious if there's
> any chance of using these memory pools effectively outside of BlueStore.
> Many of the features you discuss would be nice in the MDS, which currently
> uses boost::pool for some of its metadata types, but could really use
> something with a little more control (at least than we've set up so far).
> -Greg

  reply	other threads:[~2016-09-28  9:13 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 [this message]
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
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=BLUPR0201MB1524DEE54B0808968D29E3DBE8CF0@BLUPR0201MB1524.namprd02.prod.outlook.com \
    --to=allen.samuels@sandisk.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=gfarnum@redhat.com \
    --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.