Re: [Gluster-devel] Review request - patch #15036

[Amar Tumballi]

Have just 1 comment. Once you answer it, its good to go.

On Fri, May 12, 2017 at 9:48 AM, Raghavendra G 
wrote:

> I'll wait for a day on this. If there are no reviews, I'll assume that as
> a +1 and will go ahead and merge it. If anyone needs more time, please let
> me know and I can wait.
>
> On Thu, May 11, 2017 at 12:22 PM, Raghavendra Gowdappa <
> rgowd...@redhat.com> wrote:
>
>> All,
>>
>> Reviews are requested on [1]. Impact is non-trivial as it introduces more
>> concurrency in execution wrt processing of messages read from network.
>>
>> All tests are passed, though gerrit is not reflecting the last smoke
>> which was successful.
>>
>> For reference, below is the verbatim copy of commit msg:
>>
>> 
>>
>> event/epoll: Add back socket for polling of events immediately after
>> reading the entire rpc message from the wire Currently socket is added back
>> for future events after higher layers (rpc, xlators etc) have processed the
>> message. If message processing involves signficant delay (as in writev
>> replies processed by Erasure Coding), performance takes hit. Hence this
>> patch modifies transport/socket to add back the socket for polling of
>> events immediately after reading the entire rpc message, but before
>> notification to higher layers.
>>
>> credits: Thanks to "Kotresh Hiremath Ravishankar" 
>> for assitance in fixing a regression in bitrot caused by this patch.
>>
>> BUG: 1448364
>> 
>>
>> @Nigel,
>>
>> Is there a way to override -1 from smoke, as last instance of it is
>> successful?
>>
>> [1] https://review.gluster.org/#/c/15036/
>>
>> regards,
>> Raghavendra
>> ___
>> Gluster-devel mailing list
>> Gluster-devel@gluster.org
>> http://lists.gluster.org/mailman/listinfo/gluster-devel
>>
>
>
>
> --
> Raghavendra G
>
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel
>



-- 
Amar Tumballi (amarts)
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Review request - patch #15036

[Raghavendra G]

I'll wait for a day on this. If there are no reviews, I'll assume that as a
+1 and will go ahead and merge it. If anyone needs more time, please let me
know and I can wait.

On Thu, May 11, 2017 at 12:22 PM, Raghavendra Gowdappa 
wrote:

> All,
>
> Reviews are requested on [1]. Impact is non-trivial as it introduces more
> concurrency in execution wrt processing of messages read from network.
>
> All tests are passed, though gerrit is not reflecting the last smoke which
> was successful.
>
> For reference, below is the verbatim copy of commit msg:
>
> 
>
> event/epoll: Add back socket for polling of events immediately after
> reading the entire rpc message from the wire Currently socket is added back
> for future events after higher layers (rpc, xlators etc) have processed the
> message. If message processing involves signficant delay (as in writev
> replies processed by Erasure Coding), performance takes hit. Hence this
> patch modifies transport/socket to add back the socket for polling of
> events immediately after reading the entire rpc message, but before
> notification to higher layers.
>
> credits: Thanks to "Kotresh Hiremath Ravishankar" 
> for assitance in fixing a regression in bitrot caused by this patch.
>
> BUG: 1448364
> 
>
> @Nigel,
>
> Is there a way to override -1 from smoke, as last instance of it is
> successful?
>
> [1] https://review.gluster.org/#/c/15036/
>
> regards,
> Raghavendra
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel
>



-- 
Raghavendra G
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Coverity covscan for 2017-05-11-1a8fa910 (master branch)

[staticanalysis]

GlusterFS Coverity covscan results are available from
http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-05-11-1a8fa910
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] lock_revocation.t is hanging in regression tests

[Raghavendra G]

On Thu, May 11, 2017 at 3:58 AM, Vijay Bellur  wrote:

>
>
> On Wed, May 10, 2017 at 9:01 AM, Jeff Darcy  wrote:
>
>>
>>
>>
>> On Wed, May 10, 2017, at 06:30 AM, Raghavendra G wrote:
>>
>> marking it bad won't help as even bad tests are run by build system (and
>> they might hang).
>>
>>
>> This is news to me.  Did something change to make it this way?  If so, we
>> should change it back.  There's no point in having a way to mark tests as
>> bad if the build system ignores it.
>>
>
> skip_bad_tests is set to "yes" by default in run-tests.sh. So the
> regression job  should skip bad tests during a run.
>

My mistake. Sorry about the confusion.


>
> Nigel can probably educate us if the behavior is different :).
>
> -Vijay
>
>
>
>
>
>>
>>
>> ___
>> Gluster-devel mailing list
>> Gluster-devel@gluster.org
>> http://lists.gluster.org/mailman/listinfo/gluster-devel
>>
>
>
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel
>



-- 
Raghavendra G
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Review request - patch #15036

[Raghavendra Gowdappa]

All,

Reviews are requested on [1]. Impact is non-trivial as it introduces more 
concurrency in execution wrt processing of messages read from network.

All tests are passed, though gerrit is not reflecting the last smoke which was 
successful.

For reference, below is the verbatim copy of commit msg:



event/epoll: Add back socket for polling of events immediately after reading 
the entire rpc message from the wire Currently socket is added back for future 
events after higher layers (rpc, xlators etc) have processed the message. If 
message processing involves signficant delay (as in writev replies processed by 
Erasure Coding), performance takes hit. Hence this patch modifies 
transport/socket to add back the socket for polling of events immediately after 
reading the entire rpc message, but before notification to higher layers. 

credits: Thanks to "Kotresh Hiremath Ravishankar"  for 
assitance in fixing a regression in bitrot caused by this patch.

BUG: 1448364


@Nigel,

Is there a way to override -1 from smoke, as last instance of it is successful?

[1] https://review.gluster.org/#/c/15036/

regards,
Raghavendra
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel