On Wed, Jun 18, 2025 at 09:03:59AM +0900, Sungwoo Chang wrote:
> I created a new patch that throws an exception if we try to call
> destroy on a dsm segment that is still in use.
> I added a function in dsm.h that returns a refcnt of a given dsm
> segment. The destroy function uses that refcnt
> ge
Hi,
I created a new patch that throws an exception if we try to call
destroy on a dsm segment that is still in use.
I added a function in dsm.h that returns a refcnt of a given dsm
segment. The destroy function uses that refcnt
getter to check if the dsm segment is in use.
2025년 6월 16일 (월) 오후 11:
On Mon, Jun 16, 2025 at 09:02:22AM +0900, Sungwoo Chang wrote:
> 2025년 6월 14일 (토) 오전 6:50, Nathan Bossart 님이 작성:
>> Could your use-case be handled with a DSA? On the other thread [0], we're
>> talking about adding a GetNamedDSA() function, which returns a DSA that you
>> can use to allocate and fr
2025년 6월 14일 (토) 오전 6:50, Nathan Bossart 님이 작성:
> I suspect detaching/destroying segments would be applicable elsewhere, I'm
> just not sure about providing something with the aforementioned behavior.
>
> Could your use-case be handled with a DSA? On the other thread [0], we're
> talking about add
On Fri, Jun 13, 2025 at 08:03:00AM +0900, Sungwoo Chang wrote:
>> One of the reasons I avoided adding detach/destroy functionality originally
>> is because this seems difficult to do correctly. How would an extension
>> ensure that it doesn't end up with one set of backends attached to a new
>> se
-- Forwarded message -
보낸사람: Sungwoo Chang
Date: 2025년 6월 13일 (금) 오전 8:03
Subject: Re: dsm_registry: Add detach and destroy features
To: Nathan Bossart
> One of the reasons I avoided adding detach/destroy functionality originally
> is because this seems difficult to do correctly
