public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Arkadiusz Mi??kiewicz <arekm@maven.pl>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 3/3] xfsprogs: allow linking against libtcmalloc
Date: Sat, 19 Nov 2011 13:45:07 -0500	[thread overview]
Message-ID: <20111119184507.GA11208@infradead.org> (raw)
In-Reply-To: <201111180804.06413.arekm@maven.pl>

On Fri, Nov 18, 2011 at 08:04:06AM +0100, Arkadiusz Mi??kiewicz wrote:
> On Monday 14 of November 2011, Christoph Hellwig wrote:
> > Allow linking against the libtcmalloc library from Google's performance
> > tools, which at least for repair reduces the memory usage dramatically.
> 
> Should -fno-builtin-malloc be also used?

The documentation suggests that it's not strictly required, but probably
a good idea.  I'll fold this into the next version, together with your
autoconf updates from irc.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2011-11-19 18:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-14 15:57 [PATCH 0/3] xfs_repair malloc optimizations Christoph Hellwig
2011-11-14 15:57 ` [PATCH 1/3] repair: allocate and free inode records individually Christoph Hellwig
2011-11-14 15:57 ` [PATCH 2/3] repair: allocate and free extent " Christoph Hellwig
2011-11-14 15:57 ` [PATCH 3/3] xfsprogs: allow linking against libtcmalloc Christoph Hellwig
2011-11-18  7:04   ` Arkadiusz Miśkiewicz
2011-11-19 18:45     ` Christoph Hellwig [this message]
2011-11-21 11:59       ` [PATCH 3/3 v2] " Christoph Hellwig

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=20111119184507.GA11208@infradead.org \
    --to=hch@infradead.org \
    --cc=arekm@maven.pl \
    --cc=xfs@oss.sgi.com \
    /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