Corin,
I think you are referring to STACK_WIND/UNWIND when you say
"stack-based" design. The STACK_WIND/UNWIND macros in effect implement
a continuation-like mechanism in C.
The original reason we introduced this was to make file operations
asynchronous, in that we didn't have to wait for the rep
Hi Corin,
What do you mean by stack based design?
On Wed, Jan 14, 2009 at 8:59 PM, Corin Langosch wrote:
> Hi again,
>
> I thought glusterfs is using the stack based design instead of a
> threaded one to simplify the internal design etc, for example to get rid
> of nastly thread locking/ synchro
Hi again,
I thought glusterfs is using the stack based design instead of a
threaded one to simplify the internal design etc, for example to get rid
of nastly thread locking/ synchronization issues.
So I wonder if it is safe to use the io-threads translator in front of
any other translator than th
