On Fri, Mar 19, 2010 at 8:42 AM, Shuo Chen wrote:
> Hi there,
>
> Is it possible that libevent 2.0 utilizes timerfd and/or signalfd
> provided by recent Linux kernels?
>
> - timerfd features a better timing resolution (microseconds) than
> epoll (milliseconds), and
I wouldn't mind support for th
On Thu, Mar 18, 2010 at 12:52 PM, Roman Puls wrote:
> Hi Folks,
>
> I thought libevent would work multithreaded in the sense we can create
> (let's say) 4 worker threads that poll the same event_base. Is that
> assumption wrong?
Yes.
Each event base can only have one thread invoking
event_base_d
On Fri, Mar 19, 2010 at 10:27 PM, Shuo Chen wrote:
> Hi there,
>
> Now the log callback takes two parameters:
>
> typedef void (*event_log_cb)(int severity, const char *msg);
>
> How about adding another two or thee:
>
> typedef void (*event_log_cb)(int severity, const char *msg, const
> char* fil
Hi there,
Now the log callback takes two parameters:
typedef void (*event_log_cb)(int severity, const char *msg);
How about adding another two or thee:
typedef void (*event_log_cb)(int severity, const char *msg, const
char* file, int line /*, const char* func*/);
Given many logging libraries l
This package is built success with VC6 or VS2003 on Windows XP platform.
It need to use libevent-1.4.7-stable-iocp-1\WIN32-Prj\libevent.dsw .
Which libevent version do you use currently?
I should port iocp related things to that version.
2010/3/19 Patrick Galbraith :
> Hi again Stephen,
>
> More
Hi there,
Is it possible that libevent 2.0 utilizes timerfd and/or signalfd
provided by recent Linux kernels?
- timerfd features a better timing resolution (microseconds) than
epoll (milliseconds), and
- signalfd makes signal handling like reading a file descriptor
Seems libevent already uses
