I am not sure about another deadlock.
I have not yet repeated the higher load test where I think it has occurred - I
first need solve some problems in my code.
Thanks,
Avi
-Original Message-
From: owner-libevent-us...@freehaven.net
[mailto:owner-libevent-us...@freehaven.net] On Behal
Thanks a lot you both.
I appreciate example code and guides very much!! I will look into them.
Stef Bon
2010/7/5 Tero Marttila :
> On 07/05/2010 08:45 PM, Nick Mathewson wrote:
>>
>> On Sun, Jul 4, 2010 at 10:06 AM, Stef Bon wrote:
>>>
>>> I'm wondering, when writing a fuse module to get access
On Mon, Jul 5, 2010 at 11:17 AM, Phil Budne wrote:
> It's _almost_ enough to make one admit that VMS' "QIO" interface got it right
> (for a narrow class of high-performance server applications).
Yes. I've been regretting how I dismissed it as too complicated
back when I first saw it in its heyda
Nick wrote:
> Well, Libevent is only a library that provides compatibility across
> different operating systems' asynchronous IO facilities. As such, it
> is basically never *required* for a new project; you could always
> replace it with direct calls to the underlying OS facilities. Since
> FUSE
On 07/05/2010 08:45 PM, Nick Mathewson wrote:
On Sun, Jul 4, 2010 at 10:06 AM, Stef Bon wrote:
I'm wondering, when writing a fuse module to get access to an Internet
service like Flickr or a webservice
like a cloud, is libevent required??
As for the question of whether you *should* or *could
On Sun, Jul 4, 2010 at 10:06 AM, Stef Bon wrote:
> 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 wo
On Mon, Jul 5, 2010 at 3:03 AM, Avi Bab wrote:
>
> I now have a clearer view of things.
> Like Zhou said - there is a thread adding an event to the sender's event_base
> which is blocked on writing to base->th_notify_fd[1]:
Oho! Indeed, this is absolutely right. My apologies to Zhou Li for
not
I now have a clearer view of things.
Like Zhou said - there is a thread adding an event to the sender's event_base
which is blocked on writing to base->th_notify_fd[1]:
#0 0x0030c1c0cadb in __write_nocancel () from
/opt/breach-proxy/lib64/libpthread.so.0
#1 0x2accdd4e in evthread_
On Sun, Jul 4, 2010 at 6:43 AM, Nick Mathewson wrote:
> 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 pos
