From owner-freebsd-current@FreeBSD.ORG Sun Mar 12 09:16:51 2006 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4ED4016A600; Sun, 12 Mar 2006 09:16:51 +0000 (GMT) (envelope-from sanewo@ba2.so-net.ne.jp) Received: from mx10.ms.so-net.ne.jp (mx10.ms.so-net.ne.jp [202.238.82.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 515FC455D4; Sun, 12 Mar 2006 06:55:43 +0000 (GMT) (envelope-from sanewo@ba2.so-net.ne.jp) Received: from [127.0.0.1] (pd35c7f.tkyoac00.ap.so-net.ne.jp [220.211.92.127]) by mx10.ms.so-net.ne.jp with ESMTP id k2C6tLTY015397; Sun, 12 Mar 2006 15:55:42 +0900 (JST) Message-ID: <4413C5D8.70208@ba2.so-net.ne.jp> Date: Sun, 12 Mar 2006 15:55:20 +0900 From: SANETO Takanori User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: jasone@freebsd.org References: <200601161150.k0GBoamk010563@locutus.newmillennium.net.au> <91B40C65-A11B-427E-B352-8B6EF8A55864@freebsd.org> <43CECA2C.6030400@ba2.so-net.ne.jp> <6A234191-C4DA-4E1B-BB4D-1F3F8043DDA9@freebsd.org> In-Reply-To: <6A234191-C4DA-4E1B-BB4D-1F3F8043DDA9@freebsd.org> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org Subject: malloc options incompatibility between phkmalloc and jemalloc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Mar 2006 09:16:51 -0000 I don't think this is serious problem, but it's annoying. When I put 'k' in /etc/malloc.conf, some commands (cvsup and vmware-checkvm) show warning about unknown character. These commands seem to have phkmalloc implementation linked statically. On the other hand, when I put '>' in /etc/malloc.conf, many commands will show warnings. For second case, isn't it reasonable for jemalloc to just ignore phkmalloc specific characters? For first case, how about introducing new option source (i.e. /etc/jemalloc.conf, JEMALLOC_OPTIONS or something like that)? What do you think? -- SANETO Takanori