mirror of https://github.com/mkerrisk/man-pages
inotify.7: Note rationale and consequences of event coalescing
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
9be479a6e7
commit
8856aab855
|
@ -401,6 +401,9 @@ and
|
||||||
.IR name )
|
.IR name )
|
||||||
then they are coalesced into a single event if the
|
then they are coalesced into a single event if the
|
||||||
older event has not yet been read (but see BUGS).
|
older event has not yet been read (but see BUGS).
|
||||||
|
This reduces the amount of kernel memory required for the event queue,
|
||||||
|
but also means that an application can't use inotify to reliably count
|
||||||
|
file events.
|
||||||
|
|
||||||
The events returned by reading from an inotify file descriptor
|
The events returned by reading from an inotify file descriptor
|
||||||
form an ordered queue.
|
form an ordered queue.
|
||||||
|
|
Loading…
Reference in New Issue