On Tue, 2014-02-25 at 10:21 +, Eric Wong wrote:
> Nathaniel Yazdani wrote:
> > + * stores triggered eventpoll entries in the 'out' array. The input array
> > is
> > + * _not_ read-only, because the resulting event mask gets written back to
> > each
> > + * entry's ->ep_events field. When
Nathaniel Yazdani wrote:
> + * stores triggered eventpoll entries in the 'out' array. The input array is
> + * _not_ read-only, because the resulting event mask gets written back to
> each
> + * entry's ->ep_events field. When successful, this will be the same as
> before
> + * (plus EPOLLERR &
Nathaniel Yazdani n1ght.4nd@gmail.com wrote:
+ * stores triggered eventpoll entries in the 'out' array. The input array is
+ * _not_ read-only, because the resulting event mask gets written back to
each
+ * entry's -ep_events field. When successful, this will be the same as
before
+ *
On Tue, 2014-02-25 at 10:21 +, Eric Wong wrote:
Nathaniel Yazdani n1ght.4nd@gmail.com wrote:
+ * stores triggered eventpoll entries in the 'out' array. The input array
is
+ * _not_ read-only, because the resulting event mask gets written back to
each
+ * entry's -ep_events
This new system call combines eventpoll entry addition, modification,
deletion, and retrieval into a single call, much like the BSDs' kevent().
Eventpoll entries are described using struct epoll, whose definition
and implementation can be found in prior patches. Its operation is fairly
This new system call combines eventpoll entry addition, modification,
deletion, and retrieval into a single call, much like the BSDs' kevent().
Eventpoll entries are described using struct epoll, whose definition
and implementation can be found in prior patches. Its operation is fairly
6 matches
Mail list logo
