Date: Sun, 12 Mar 2006 15:55:20 +0900 From: SANETO Takanori <sanewo@ba2.so-net.ne.jp> To: jasone@freebsd.org Cc: freebsd-current@FreeBSD.org Subject: malloc options incompatibility between phkmalloc and jemalloc Message-ID: <4413C5D8.70208@ba2.so-net.ne.jp> In-Reply-To: <6A234191-C4DA-4E1B-BB4D-1F3F8043DDA9@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>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <sanewo@ba2.so-net.ne.jp>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4413C5D8.70208>