unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <contact.ng0@cryptolab.net>
To: Tobias Geerinckx-Rice <me@tobias.gr>, guix-devel@gnu.org
Subject: Re: Adding ‘--enable-openbsd-malloc’ configure-flag to Tor.
Date: Tue, 31 Jan 2017 12:07:59 +0000	[thread overview]
Message-ID: <8737fzfn4w.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <8760kvfo3k.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me>

ng0 <contact.ng0@cryptolab.net> writes:

> Tobias Geerinckx-Rice <me@tobias.gr> writes:
>
>> Guix,
>>
>> On 30/01/17 23:44, Ludovic Courtès wrote:
>>> Re: [PATCH] gnu: tor: Add hardening configure-flags.
>>> 
>>> Applied, thanks.
>>
>> Ah, just too late :-) Although this isn't hardening-related.
>>
>> I'd like to also add the ‘--enable-openbsd-malloc’ configure flag to our 
>> Tor <https://www.torproject.org/docs/faq.html.en#RelayMemory>.
>>
>> Since adding it, I've been able to serve more traffic more reliably on a 
>> memory-constrained relay — without any noticable increase in load. This 
>> might be different on a SoC, although I'd suspect RAM would be the 
>> limiting factor there too.
>>
>> To anyone willing to give it a try & give their opinion on the matter: 
>> I'd be very grateful.
>>
>> Kind regards,
>>
>> T G-R
>>
>> PS: Sorry, no patch, because of
>>
>> -- 
>> Sent from a Web browser. Excuse/enjoy my brevity.
>>
>
> The tradeoff is more CPU load. For tor-relays I know how annoying
> this can be, but I'm not sure if less RAM, more CPU is a good
> idea (or any improvement) for the client-only side.
>
> I need to read more about this and comment again once I know
> more.
> -- 
> ng0 -- https://www.inventati.org/patternsinthechaos/

I try to take the www documentation of torproject with a grain of
salt, they have seen some improvement but usually it's better to
read the sourcecode and commits.

In commit 6a17067d38679224e8f59dd486132400e6869dc6 Andrew made
--enable-openbsd-mallow no longer the default, you now have to opt-in
to it if I understand the short commit right. This was in June
2008. Some commit before that, and in 2012 was  the last openbsd
malloc related commit.
It also seems to depend on glibc, at least according to some
commit in 2008, tor 0.2.0 which removed the option entirely for a
while (https://marc.info/?l=tor-cvs&m=121946290600768&w=2).

commit 6a17067d38679224e8f59dd486132400e6869dc6
Author: Andrew Lewman <andrew@torproject.org>
Date:   Sat Jun 21 13:44:03 2008 +0000

    with all of these fancy memory fixes, openbsd malloc appears
    to not be
        needed any more.


    svn:r15390
-- 
ng0 -- https://www.inventati.org/patternsinthechaos/

      reply	other threads:[~2017-01-31 12:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-31  0:15 Adding ‘--enable-openbsd-malloc’ configure-flag to Tor Tobias Geerinckx-Rice
2017-01-31 11:47 ` ng0
2017-01-31 12:07   ` ng0 [this message]

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8737fzfn4w.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me \
    --to=contact.ng0@cryptolab.net \
    --cc=guix-devel@gnu.org \
    --cc=me@tobias.gr \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).