memory management talk + patches for femalloc+xtbench
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24.org>
To: mm@80x24.org
Cc: Eric Wong <e@80x24.org>
Subject: [PATCH] README: updates about overcommit + release
Date: Thu,  4 Sep 2014 04:15:01 +0000	[thread overview]
Message-ID: <1409804101-13953-1-git-send-email-e@80x24.org> (raw)

---
 README | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/README b/README
index b783514..9be317d 100644
--- a/README
+++ b/README
@@ -38,7 +38,8 @@ is recommended.  We will fix this.
 
 Overheads for small allocations is large, we will fix this.
 
-We should work well on systems VM overcommit disabled, will fix
+We should avoid using too much space for for systems with overcommit
+disabled, will fix.
 
 We will support applications which spawn many more threads than CPUs,
 as we realize it is often easier to spawn extra threads to deal with
@@ -51,7 +52,8 @@ probably needs fixing as the related ptmalloc2 (from glibc) behaves
 horribly sometimes.
 
 Memory is not released back to the OS automatically, only via
-calls to `malloc_trim'.
+calls to `malloc_trim'.  Note: releasing memory back to the OS only to
+re-acquire it again is expensive.
 
 Linux 2.6-and later only for now, FreeBSD support coming.
 
-- 
EW


                 reply	other threads:[~2014-09-04  4:15 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=1409804101-13953-1-git-send-email-e@80x24.org \
    --to=e@80x24.org \
    --cc=mm@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