Re: [RFC PATCH 1/1] pthread_detach.3: remove invalid and confusing statement

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Sep 29, 2017 at 9:55 PM, Michael Kerrisk (man-pages)
<mtk.manpages@xxxxxxxxx> wrote:
> Hello Rahul,
>
> A> very late follow-up...
>
> On 13 October 2015 at 05:48, Rahul Bedarkar <rpal143@xxxxxxxxx> wrote:
>> On Fri, Oct 9, 2015 at 2:40 AM, Michael Kerrisk (man-pages)
>> <mtk.manpages@xxxxxxxxx> wrote:
>>> Rahul,
>>>
>>> On 09/26/2015 07:04 AM, Rahul Bedarkar wrote:
>>>> In notes section, statement
>>>>
>>>> "(But note that the resources of all threads are freed when the
>>>> process terminates.)"
>>>>
>>>> is confusing and invalid. In Linux, we don't really need to wait
>>>> until application termination for system resources to be freed unless
>>>> there is bug in application logic.
>>>
>>> While I'm not sure that that sentence is essential, it does serve
>>> to remind the reader that all resources are freed on process
>>> termination, regardless of whether pthread_detach() and pthread_join()
>>> are used.
>>>
>>> It's not clear to me why you find it confusing or invalid.
>>> Can you say more?
>>
>> Hi Michael,
>>
>> Why it should be a special case about pthread that we should mention
>> that all resources are freed on process termination which is feature
>> of an Operating system.
>>
>> When we don't mention it in open.2 or free.3, I thought it should not
>> be mentioned in pthread case, as it is something not related to it.
>>
>> The sentence in bracket looks more confusing if we read previous one.
>>
>> "Either pthread_join(3) or pthread_detach() should be called for each
>> thread that an application creates, so that  system  resources for the
>> thread can be released.  (But note that the resources of all threads
>> are freed when the process terminates.)"
>>
>> I think above sentences convey that you should call either
>> pthread_join() or pthread_detach() so that resources are can be freed.
>> But note that those won't get freed until process is terminated.
>>
>> That's why it looks confusing to me and looks invalid because note in
>> bracket conveys different meaning than intended.
>
> So, I changed that last sentence to try to eliminate such an ambiguity:
>
>        Either  pthread_join(3)  or  pthread_detach()  should  be
>        called for each thread that an  application  creates,  so
>        that  system  resources  for  the thread can be released.
>        (But note that the resources of any threads for which one
>        of these actions has not been done will be freed when the
>        process terminates.)

Thanks for fixing this. It is indeed very clear now.

Regards,
Rahul
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Kernel Documentation]     [Netdev]     [Linux Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux