Re: [RFC PATCH 5/5] epoll: introduce epoll connected components (remove the epmutex)

2015-01-16 Thread Jason Baron
On 01/15/2015 06:10 PM, Eric Wong wrote: > Jason Baron wrote: >> I've done a bit of performance evaluation on a dual socket, 10 core, hyper >> threading enabled box: Intel(R) Xeon(R) CPU E5-2650 v3 @ 2.30GHz. For the >> simple epfdN->epfdN->pipefdN topology case where each thread has its >> own un

Re: [RFC PATCH 5/5] epoll: introduce epoll connected components (remove the epmutex)

2015-01-15 Thread Eric Wong
Jason Baron wrote: > I've done a bit of performance evaluation on a dual socket, 10 core, hyper > threading enabled box: Intel(R) Xeon(R) CPU E5-2650 v3 @ 2.30GHz. For the > simple epfdN->epfdN->pipefdN topology case where each thread has its > own unique files and is doing EPOLL_CTL_ADD and EPOLL

[RFC PATCH 5/5] epoll: introduce epoll connected components (remove the epmutex)

2015-01-15 Thread Jason Baron
We currently use the global'epmutex' in the epoll code to serialize when files are being closed (and we need to remove them from epoll) and in certain cases when we are doing epoll_ctl(EPOLL_CTL_ADD). The requirements for epoll_ctl(EPOLL_CTL_ADD) are that we don't create an epoll topology with loop