post 3.1 xlator/io-threads instability on NetBSD (was: NULL frame->conn cause a crash)

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

 



On Tue, Jul 05, 2011 at 09:32:23AM +0000, Emmanuel Dreyfus wrote:
> Let us forget my previous batch of crashes that were with 3.2.1. This
> one iw with today's code from git:

I made some progress on that problem. Removing the io-threads xlator 
fixes the stability problem. It also greatly improves performances
while the server load decrease from 14 to 3 for the same operations.

It seems there have been some refactoring of xlatorx/io-threads since 3.1.
It does not use sem_timedwait() anymore, that was replaced by 
pthread_cond_timedwait(). 

Anyone has ideas here?

-- 
Emmanuel Dreyfus
manu@xxxxxxxxxx



[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux