memory management talk + patches for femalloc+xtbench
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24.org>
To: xtmalloc-public@80x24.org
Subject: xtmalloc - cross-thread malloc implementation
Date: Wed, 30 Jul 2014 07:16:40 +0000	[thread overview]
Message-ID: <20140730071640.GC24216@dcvr.yhbt.net> (raw)

xtmalloc is malloc implementation designed for applications which
communicate and share allocations across different threads.  It is not
intended to be the fastest allocator in synthetic benchmarks.

xtmalloc is based on a version (aka dlmalloc 2.8.6) of malloc/free/realloc
written by Doug Lea and released to the public domain, as explained at
http://creativecommons.org/publicdomain/zero/1.0/
The original version of dlmalloc is available at
ftp://gee.cs.oswego.edu/pub/misc/

xtmalloc chooses the LGPL to allow static linking with Userspace RCU
library <http://urcu.so/>.  Non-URCU-related improvements are
encouraged to be placed in the public domain so they may be used
in future version of dlmalloc by Doug Lea.

git clone git://80x24.org/xtmalloc

                 reply	other threads:[~2014-07-30  7:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20140730071640.GC24216@dcvr.yhbt.net \
    --to=e@80x24.org \
    --cc=xtmalloc-public@80x24.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox