DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=NRgFYdr3ApELDXf85h6SzXC9ZJYhmIAozwsct81B1iXa7ygXcAiYW
	0VVYpj3ERBST7LdnxkHH395/mXvpnQlYAb7wFhL04yFX5kAaFs2uBuZJoU6jQpr9
	1cNbHjOB6qAzK4JwNblzYUv5RiBSsbj0o15R9MWfWDy7FiUhhiB5G8=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Thu, 26 Nov 2015 10:30:44 +0100
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com, cygwin-developers@cygwin.com
Subject: Re: Jemalloc under CYGWIN
Message-ID: <20151126093044.GI2755@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com, cygwin-developers@cygwin.com
References: <CAJygYd2T9JSJCDT178F8mzmuA79MsBbWCLsr8eF7Aguxk_-YWQ@mail.gmail.com> <CAJygYd1tU+Nc5+owTw0Lfuk8SWQQS2vE1mhKjoz5br4c9zVF8A@mail.gmail.com> <20151021105300.GN5319@calimero.vinschen.de> <CAJygYd3o5tjmLx8e8zCFi+T5LxzBLk02nMrcC03Fp-MbnuBsHQ@mail.gmail.com> <20151021141523.GV5319@calimero.vinschen.de> <CAJygYd1a82LVP0EuKyDtrux=6uJ=rN95yRghy3sdkKU+_9yt5Q@mail.gmail.com> <20151021154021.GA19868@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="IvGM3kKqwtniy32b"
Content-Disposition: inline
In-Reply-To: <20151021154021.GA19868@calimero.vinschen.de>
User-Agent: Mutt/1.5.23 (2014-03-12)

--IvGM3kKqwtniy32b
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi Yucong Sun,

On Oct 21 17:40, Corinna Vinschen wrote:
> On Oct 21 22:43, Yucong Sun wrote:
> > On Wed, Oct 21, 2015 at 10:15 PM, Corinna Vinschen
> > <corinna-cygwin@cygwin.com> wrote:
> > > On Oct 21 21:49, Yucong Sun wrote:
> > >> > What exactly is the malloc problem you're seeing?
> > >>
> > >> The specific problem I'm having is that jemalloc's malloc_init() cal=
ls
> > >> needs to use pthread_mutex_init()  or even pthread_mutex with a
> > >> initializer.   Both in-turn uses malloc, triggering this issue.
> > >>
> > >> A quick fix would be somehow make pthread always use system
> > >> malloc/free, which shouldn't be that bad.
> > >
> > > What about using a native critical section instead?  It shouldn't be =
too
> > > tricky to conditionalize this in jemalloc.
> >=20
> > Possibly, jemalloc already have support of this.  However I wasn't so
> > sure that this was possible before,
> >=20
> > see https://github.com/jemalloc/jemalloc/blob/dev/include/jemalloc/inte=
rnal/mutex.h#L80
>=20
> Yes, that looks good.  Please use critical sections for the time being.
> We're going to drop XP support end of this year, but up to that point we
> can't use SRW locks.

did you manage to include jemalloc into Cygwin in the meantime?  It
would be very cool to get a patch to replace dlmalloc with jemalloc :}


Thanks,
Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--IvGM3kKqwtniy32b
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJWVtFEAAoJEPU2Bp2uRE+gMGoP/iDpIIak5u1IcRj3bFi7ZWOA
xafJrWFi6ooQzY+jx4fTENTFt3D+GnIcuxJdsFgCaCu+B97f/iOZxW96YN8NGHVs
mf+Jg1vDrG02bDmayV4In/pdBgXOxXBzHzQtqX+HP5EuX4cDpq+GQD+AaPOBw1fJ
Wpd/s27NFgwvrhJsQpVsTeOaPcFw2qGxlWOBBhqlxxEYBZGBWUYwZAiEi9qTT+Ey
c9dq16woWxb97dFpuwa5vlzK+amHXYOAVPlC2k89jv5aQj5XTmCwzqcNJhq1BTcl
djAh9eiY/yjxGGNZRvs6GxA4x94Ang1FWwyM+B3zScKaDhgtPDS6PRFV+zLt0Jb6
qO9oMnMyx3QaSEvUMeoWj2FRxlbvL2BFk5OOvsRz1WPeSVCt7ElWvJLQ8tx/9X+D
YHM0RhVlO2vDcnthsFs8M8xpdN3f5A3M/bo2nDViMM0D1LarOU3SqWGNONXpaXz4
7LU4wsPxj29BCTgzw8GBLmu6pkhRs+fY5RKoMqYuWrB6Hq8yuqwuZFlXqquaxUsw
G+9h8PJnl1Cp9p8L6XLiyi1EaAqCUOHyaJfCTdSbbjaKHcHkCcDR10SH4s8352bj
eBtJvggd8cyFwXFWnHylfBhBe1zq7bsJ8f1hP5lWJKs59OE93JVweOgPOnhpsr64
nMRZHDyLfH6/fJoiWEct
=E09M
-----END PGP SIGNATURE-----

--IvGM3kKqwtniy32b--