gluster-devel
[Top][All Lists]
Advanced

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

Re: [Gluster-devel] Gluster driver for Archipelago - Development process


From: Alex Pyrgiotis
Subject: Re: [Gluster-devel] Gluster driver for Archipelago - Development process
Date: Wed, 05 Feb 2014 12:40:18 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131103 Icedove/17.0.10

Hi all,

Just wondering, do we have any news on that?

Thanks,
Alex

On 12/18/2013 04:24 PM, Alex Pyrgiotis wrote:
> Hi Vijay,
> 
> On 12/17/2013 07:54 PM, Vijay Bellur wrote:
>> On 12/06/2013 07:46 PM, Alex Pyrgiotis wrote:
>>
>> Alex: Thanks for this very detailed mail. It makes things quite clear to me.
>>
> 
> That's good to hear.
> 
>>>
>>> Summing up:
>>>
>>> My opinion is that persistent locking is of secondary importance, as it
>>> can be handled in application level. Async open with O_CREAT on the
>>> other hand isn't.
>>>
>>> Thus, I propose for the first phase to make the open() call non-blocking
>>> and possibly add the O_CREAT flag. For our part, we can benchmark the
>>> performance of the current driver and measure it against any
>>> improvements that occur along the road.
>>>
>>> For the second phase, we can work out a persistent locking scheme that
>>> would benefit both parties.
>>>
>>> Finally, the third phase can revolve around making the rest of the
>>> blocking calls non-blocking.
>>>
>>> So, what do you think?
>>>
>>
>> Agree with you here. We can knock off things in the order that you 
>> mention. We will start working on the non-blocking open() implementation 
>> and let you folks know when it is ready. We can then pick up subsequent 
>> integration activities.
>>
> 
> That sounds good. We'll be waiting eagerly to measure the performance
> gain and move forward with the rest of the things.
> 
> Kind Regards,
> Alex
> 


-- 
Alex | address@hidden



reply via email to

[Prev in Thread] Current Thread [Next in Thread]