Hello,
I'm building a construction serving the user in his/her homedirectory
easy access to various resources like
a SMB share, USB stick, partition on harddisks etc. See:
http://linux.bononline.nl/projects/mount.md5key.new/
I'm wondering, when writing a fuse module to get access to an Internet
On Sun, Jul 4, 2010 at 4:29 AM, Avi Bab wrote:
>
> Indeed it seems that someone, some when, failed to release the lock.
> At the time of the deadlock the third thread (The ReceiverThread) is
> dispatching on a different eventbase.
>
> This third thread does do some manipulation on bufferevents th
On Sat, Jul 3, 2010 at 2:10 AM, Zhou Li wrote:
> I met such deadlock too. It happened under very high load just as you said.
> I think the cause is that the call write(th_notify_fd[1]) got blocked (
> sorry I didn't remember the exact position of this call to write
> th_notify_fd).
> In event.c li
Apologies - this seems to be incorrect
From: owner-libevent-us...@freehaven.net
[mailto:owner-libevent-us...@freehaven.net] On Behalf Of Avi Bab
Sent: Sunday, July 04, 2010 2:04 PM
To: libevent-us...@freehaven.net
Subject: RE: [Libevent-users] deadlock in libevent-2.0.5-beta
Prior to this modif
Prior to this modification the deadlock occurred when the thread that deletes
events from the event_base had consumed ~100% CPU (each thread has a dedicated
CPU).
Now it happens when the thread that adds events to the event_base consumes
~100% CPU.
Avi
From: owner-libevent-us...@freehaven.ne
This made a great improvement - the deadlock still appears but only on even
higher loads.
Thanks,
Avi
From: owner-libevent-us...@freehaven.net
[mailto:owner-libevent-us...@freehaven.net] On Behalf Of Zhou Li
Sent: Saturday, July 03, 2010 9:11 AM
To: libevent-us...@freehaven.net
Subject: Re:
Indeed it seems that someone, some when, failed to release the lock.
At the time of the deadlock the third thread (The ReceiverThread) is
dispatching on a different eventbase.
This third thread does do some manipulation on bufferevents that are registered
with the Sender's event_base:
void CB
