On Wed, May 11, 2016 at 10:04:48AM +0200, Otto Moerbeek wrote:

> On Fri, Apr 29, 2016 at 08:42:00AM +0200, Otto Moerbeek wrote:
> 
> > Hi,
> > 
> > new diff in http://www.drijf.net/openbsd/malloc/
> > 
> > Should fix the issue Ted spotted and contains initial code to only set
> > up multiple pools if threaded. This one is only lightly tested by me,
> > but I wanted to post this before I'll be away for a semi-long weekend,
> > 
> > I don't think this is ready for wide testing, but of course I
> > encourage playing, testing, reviewing or printing out and using as
> > wallpaper ;-)
> > 
> >     -Otto
> 
> And I just publsihed a new diff at http://www.drijf.net/openbsd/malloc
> 
> Changes:
> 
> - diff against current. Due to the TIB work quite some things changed.
> MOst importnat change is that I now have direct access to the thread
> id. Since this is a random value, I can use the lower bits directly
> to compute the "home" pool for a thread.
> 
> - Realized wrterror() is since some years unconditionally a dead(-end)
> function. I'm using this in the multi-thread related parts, but this
> could probably be used in other places as well.
> 
> Please be very sure you are running current packages, otherwise you
> are not testing what you think you are testing.
> 
>       -Otto

New diff posted in http://www.drijf.net/openbsd/malloc.

The intention is that this is close to commitable. But while a
straight merge of most recent diff with the current src, a bug
might have crept in. So beware etc.

        -Otto




Reply via email to