Lines Matching refs:mtx
47 * 2) ep->mtx (mutex)
58 * mutex (ep->mtx). It is acquired during the event transfer loop,
66 * It is possible to drop the "ep->mtx" and to use the global
68 * but having "ep->mtx" will make the interface more scalable.
70 * normal operations the epoll private "ep->mtx" will guarantee
183 struct mutex mtx;
392 * all the associated resources. Must be called with "mtx" held.
444 * We do not need to hold "ep->mtx" here because the epoll file
472 mutex_destroy(&ep->mtx);
536 * "ep->mtx" after "epmutex" because ep_remove() requires it when called
546 mutex_lock(&ep->mtx);
548 mutex_unlock(&ep->mtx);
562 mutex_init(&ep->mtx);
578 * are protected by the "mtx" mutex, and ep_find() must be called with
579 * "mtx" held.
718 * Must be called with "mtx" held.
771 * protected by "mtx", and ep_insert() is called with "mtx" held.
806 * list, since that is used/cleaned only inside a section bound by "mtx".
807 * And ep_insert() is called with "mtx" held.
821 * has a match in the current file status. Must be called with "mtx" held.
888 mutex_lock(&ep->mtx);
906 * Items cannot vanish during the loop because we are holding "mtx".
915 * because we are holding the "mtx" and this will guarantee
924 * "mtx", so no operations coming from userspace can change
940 * "mtx" and the poll callback will queue them in ep->ovflist.
989 mutex_unlock(&ep->mtx);
1167 mutex_lock(&ep->mtx);
1170 * Try to lookup the file inside our RB tree, Since we grabbed "mtx"
1200 mutex_unlock(&ep->mtx);