- Original Message -
> From: "Amar Tumballi"
> To: "Raghavendra Gowdappa"
> Cc: "Pranith Kumar Karampuri" , "Gluster Devel"
>
> Sent: Tuesday, July 25, 2017 4:06:27 PM
> Subject: Re: [Gluster-devel] Changing the relative
>>> - Original Message -
>>> > From: "Pranith Kumar Karampuri"
>>> > To: "Raghavendra G"
>>> > Cc: "Gluster Devel"
>>> > Sent: Tuesday, July 25, 2017 7:51:07 AM
>>> > Subject: Re
t;
>> > Cc: "Gluster Devel"
>> > Sent: Tuesday, July 25, 2017 7:51:07 AM
>> > Subject: Re: [Gluster-devel] Changing the relative order of read-ahead
>> andopen-behind
>> >
>> >
>> >
>> > On Mon, Jul 24, 2017 a
On Tue, Jul 25, 2017 at 9:33 AM, Raghavendra Gowdappa
wrote:
>
>
> - Original Message -
> > From: "Pranith Kumar Karampuri"
> > To: "Raghavendra G"
> > Cc: "Gluster Devel"
> > Sent: Tuesday, July 25, 2017 7:51:07 AM
>
- Original Message -
> From: "Pranith Kumar Karampuri"
> To: "Raghavendra G"
> Cc: "Gluster Devel"
> Sent: Tuesday, July 25, 2017 7:51:07 AM
> Subject: Re: [Gluster-devel] Changing the relative order of read-ahead and
> open-b
On Mon, Jul 24, 2017 at 5:11 PM, Raghavendra G
wrote:
>
>
> On Fri, Jul 21, 2017 at 6:39 PM, Vijay Bellur wrote:
>
>>
>> On Fri, Jul 21, 2017 at 3:26 AM, Raghavendra Gowdappa <
>> rgowd...@redhat.com> wrote:
>>
>>> Hi all,
>>>
>>> We've a bug [1], due to which read-ahead is completely disabled w
+Milind
On Mon, Jul 24, 2017 at 5:11 PM, Raghavendra G
wrote:
>
>
> On Fri, Jul 21, 2017 at 6:39 PM, Vijay Bellur wrote:
>
>>
>> On Fri, Jul 21, 2017 at 3:26 AM, Raghavendra Gowdappa <
>> rgowd...@redhat.com> wrote:
>>
>>> Hi all,
>>>
>>> We've a bug [1], due to which read-ahead is completely d
On Fri, Jul 21, 2017 at 6:39 PM, Vijay Bellur wrote:
>
> On Fri, Jul 21, 2017 at 3:26 AM, Raghavendra Gowdappa > wrote:
>
>> Hi all,
>>
>> We've a bug [1], due to which read-ahead is completely disabled when the
>> workload is read-only. One of the easy fix was to make read-ahead as an
>> ancest
On Fri, Jul 21, 2017 at 3:26 AM, Raghavendra Gowdappa
wrote:
> Hi all,
>
> We've a bug [1], due to which read-ahead is completely disabled when the
> workload is read-only. One of the easy fix was to make read-ahead as an
> ancestor of open-behind in xlator graph (Currently its a descendant). A
>
Hi all,
We've a bug [1], due to which read-ahead is completely disabled when the
workload is read-only. One of the easy fix was to make read-ahead as an
ancestor of open-behind in xlator graph (Currently its a descendant). A patch
has been sent out by Rafi to do the same. As noted in one of the
10 matches
Mail list logo