Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 11 Apr 2014 15:50:07 -0400 (EDT)
From:      Daniel Eischen <deischen@freebsd.org>
To:        Konstantin Belousov <kostikbel@gmail.com>
Cc:        freebsd-hackers@freebsd.org, Karl Pielorz <kpielorz_lst@tdx.co.uk>
Subject:   Re: Stuck CLOSED sockets / sshd / zombies...
Message-ID:  <Pine.GSO.4.64.1404111547210.23644@sea.ntplx.net>
In-Reply-To: <20140411183949.GX21331@kib.kiev.ua>
References:  <20140409111917.GH21331@kib.kiev.ua> <851413886E3982D2CCFEA9D9@Mail-PC.tdx.co.uk> <20140410184855.GP21331@kib.kiev.ua> <211BD03C086DDB1A07FDF036@Mail-PC.tdx.co.uk> <20140411131649.GR21331@kib.kiev.ua> <652B8CA4866C0B9E4650430B@Mail-PC.tdx.co.uk> <20140411141526.GT21331@kib.kiev.ua> <464979E8F6FCBD7EA7DAA38B@Mail-PC.tdx.co.uk> <20140411160628.GV21331@kib.kiev.ua> <Pine.GSO.4.64.1404111320250.23129@sea.ntplx.net> <20140411183949.GX21331@kib.kiev.ua>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 11 Apr 2014, Konstantin Belousov wrote:

> On Fri, Apr 11, 2014 at 01:23:00PM -0400, Daniel Eischen wrote:
>> On Fri, 11 Apr 2014, Konstantin Belousov wrote:
>>> The correct solution is to merge libthr into libc. Some neccessary
>>> preparations were already done, but the main work did not started yet.
>>> This is huge efforts, and it probably should be coordinated with some
>>> other ABI changes planed for libthr to support process-shared locks.
>>
>> Eek, no, I don't think that is necessary.  When we go to using real
>> structs instead of pointers for synchronization types (mutex, CV)
>> in libthr, then I don't think there will be a problem.
>
> Could you, please, clarify what do you consider not neccessary ?
> The merge, the (unrelated) ABI change, or coordination ?

Sorry, I should have elided parts of the email to which I
was not responding.  I mean merging libthr into libc.  I
think we should wait until we change mutex, CV, and perhaps
pthread to be structs, then see if merging libthr into
libc is still necessary.

-- 
DE



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.64.1404111547210.23644>