1 .\" Copyright (C) 2003 Davide Libenzi
2 .\" Davide Libenzi <davidel@xmailserver.org>
3 .\" and Copyright 2009, 2014, 2016, 2018, 2019 Michael Kerrisk <tk.manpages@gmail.com>
5 .\" %%%LICENSE_START(GPLv2+_SW_3_PARA)
6 .\" This program is free software; you can redistribute it and/or modify
7 .\" it under the terms of the GNU General Public License as published by
8 .\" the Free Software Foundation; either version 2 of the License, or
9 .\" (at your option) any later version.
11 .\" This program is distributed in the hope that it will be useful,
12 .\" but WITHOUT ANY WARRANTY; without even the implied warranty of
13 .\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
14 .\" GNU General Public License for more details.
16 .\" You should have received a copy of the GNU General Public
17 .\" License along with this manual; if not, see
18 .\" <http://www.gnu.org/licenses/>.
21 .TH EPOLL_CTL 2 2021-03-22 "Linux" "Linux Programmer's Manual"
23 epoll_ctl \- control interface for an epoll file descriptor
26 .B #include <sys/epoll.h>
28 .BI "int epoll_ctl(int " epfd ", int " op ", int " fd \
29 ", struct epoll_event *" event );
32 This system call is used to add, modify, or remove
33 entries in the interest list of the
36 referred to by the file descriptor
38 It requests that the operation
40 be performed for the target file descriptor,
48 Add an entry to the interest list of the epoll file descriptor,
50 The entry includes the file descriptor,
52 a reference to the corresponding open file description (see
56 and the settings specified in
60 Change the settings associated with
62 in the interest list to the new settings specified in
66 Remove (deregister) the target file descriptor
68 from the interest list.
71 argument is ignored and can be NULL (but see BUGS below).
75 argument describes the object linked to the file descriptor
83 typedef union epoll_data {
91 uint32_t events; /* Epoll events */
92 epoll_data_t data; /* User data variable */
101 structure specifies data that the kernel should save and then return (via
103 when this file descriptor becomes ready.
109 structure is a bit mask composed by ORing together zero or more of
110 the following available event types:
113 The associated file is available for
118 The associated file is available for
122 .BR EPOLLRDHUP " (since Linux 2.6.17)"
123 Stream socket peer closed connection,
124 or shut down writing half of connection.
125 (This flag is especially useful for writing simple code to detect
126 peer shutdown when using edge-triggered monitoring.)
129 There is an exceptional condition on the file descriptor.
130 See the discussion of
136 Error condition happened on the associated file descriptor.
137 This event is also reported for the write end of a pipe when the read end
141 will always report for this event; it is not necessary to set it in
147 Hang up happened on the associated file descriptor.
150 will always wait for this event; it is not necessary to set it in
155 Note that when reading from a channel such as a pipe or a stream socket,
156 this event merely indicates that the peer closed its end of the channel.
157 Subsequent reads from the channel will return 0 (end of file)
158 only after all outstanding data in the channel has been consumed.
161 Requests edge-triggered notification for the associated file descriptor.
162 The default behavior for
167 for more detailed information about edge-triggered and
168 level-triggered notification.
170 This flag is an input flag for the
174 it is never returned by
177 .BR EPOLLONESHOT " (since Linux 2.6.2)"
178 Requests one-shot notification for the associated file descriptor.
179 This means that after an event notified for the file descriptor by
181 the file descriptor is disabled in the interest list and no other events
182 will be reported by the
189 to rearm the file descriptor with a new event mask.
191 This flag is an input flag for the
195 it is never returned by
198 .BR EPOLLWAKEUP " (since Linux 3.5)"
199 .\" commit 4d7e30d98939a0340022ccd49325a3d70f7e0238
204 are clear and the process has the
207 ensure that the system does not enter "suspend" or
208 "hibernate" while this event is pending or being processed.
209 The event is considered as being "processed" from the time
210 when it is returned by a call to
212 until the next call to
217 the closure of that file descriptor,
218 the removal of the event file descriptor with
222 for the event file descriptor with
226 This flag is an input flag for the
230 it is never returned by
233 .BR EPOLLEXCLUSIVE " (since Linux 4.5)"
234 Sets an exclusive wakeup mode for the epoll file descriptor that is being
235 attached to the target file descriptor,
237 When a wakeup event occurs and multiple epoll file descriptors
238 are attached to the same target file using
240 one or more of the epoll file descriptors will receive an event with
242 The default in this scenario (when
244 is not set) is for all epoll file descriptors to receive an event.
246 is thus useful for avoiding thundering herd problems in certain scenarios.
248 If the same file descriptor is in multiple epoll instances,
251 flag, and others without, then events will be provided to all epoll
252 instances that did not specify
254 and at least one of the epoll instances that did specify
257 The following values may be specified in conjunction with
267 can also be specified, but this is not required:
268 as usual, these events are always reported if they occur,
269 regardless of whether they are specified in
271 Attempts to specify other values in
277 may be used only in an
279 operation; attempts to employ it with
290 pair yields an error.
297 and specifies the target file descriptor
299 as an epoll instance will likewise fail.
300 The error in all of these cases is
305 flag is an input flag for the
309 it is never returned by
315 When an error occurs,
319 is set to indicate the error.
326 is not a valid file descriptor.
332 and the supplied file descriptor
334 is already registered with this epoll instance.
345 or the requested operation
347 is not supported by this interface.
350 An invalid event type was specified along with
370 flag has previously been applied to this
380 refers to an epoll instance.
384 refers to an epoll instance and this
386 operation would result in a circular loop of epoll instances
387 monitoring one another or a nesting depth of epoll instances
398 is not registered with this epoll instance.
401 There was insufficient memory to handle the requested
407 .I /proc/sys/fs/epoll/max_user_watches
408 was encountered while trying to register
409 .RB ( EPOLL_CTL_ADD )
410 a new file descriptor on an epoll instance.
420 This error can occur if
422 refers to, for example, a regular file or a directory.
425 was added to the kernel in version 2.6.
426 .\" To be precise: kernel 2.5.44.
427 .\" The interface should be finalized by Linux kernel 2.5.66.
428 Library support is provided in glibc starting with version 2.3.2.
435 interface supports all file descriptors that support
438 In kernel versions before 2.6.9, the
440 operation required a non-null pointer in
442 even though this argument is ignored.
445 can be specified as NULL
448 Applications that need to be portable to kernels before 2.6.9
449 should specify a non-null pointer in
456 but the caller does not have the
457 .BR CAP_BLOCK_SUSPEND
461 .IR "silently ignored" .
462 This unfortunate behavior is necessary because no validity
463 checks were performed on the
465 argument in the original implementation, and the addition of the
467 with a check that caused the call to fail if the caller did not have the
469 capability caused a breakage in at least one existing user-space
470 application that happened to randomly (and uselessly) specify this bit.
471 .\" commit a8159414d7e3af7233e7a5a82d1c5d85379bd75c (behavior change)
472 .\" https://lwn.net/Articles/520198/
473 A robust application should therefore double check that it has the
475 capability if attempting to use the
479 .BR epoll_create (2),