From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from baldric (baldric.uwo.ca [129.100.10.225]) by dsl2.external.hp.com (Postfix) with ESMTP id E5416483E for ; Fri, 26 Sep 2003 08:29:51 -0600 (MDT) Date: Fri, 26 Sep 2003 10:24:08 -0400 From: Carlos O'Donell To: wmglo@dent.med.uni-muenchen.de Cc: libc-alpha@sources.redhat.com, parisc-linux@lists.parisc-linux.org Message-ID: <20030926142408.GZ14406@systemhalted> References: <20030925211509.GY14406@systemhalted> <20030926133954.12328.qmail@md.dent.med.uni-muenchen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20030926133954.12328.qmail@md.dent.med.uni-muenchen.de> Subject: [parisc-linux] Re: [RFC] Where to put arch-dependant locking in malloc/thread-m.h Sender: parisc-linux-admin@lists.parisc-linux.org Errors-To: parisc-linux-admin@lists.parisc-linux.org List-Help: List-Post: List-Subscribe: , List-Id: parisc-linux developers list List-Unsubscribe: , List-Archive: On Fri, Sep 26, 2003 at 01:39:54PM -0000, wmglo@dent.med.uni-muenchen.de wrote: > > The following patch fixes the issue, but I'm not content about it's > > placement in malloc/thread-m.h. Any comments about where I might put > > this in order to make maintenance easier? > > Ok, I have become convinced it is best to move thread-m.h into > sysdeps. We should rename it, too (my suggestion: malloc-machine.h), > and make sure that one can put e.g. > > #define DEFAULT_MMAP_THRESHOLD (256*1024) > > in there and have it reflected in malloc. > > I'll send a patch for this tomorrow. Thank you. Sounds like the best solution in this case. c.