Lines Matching full:notification

2 General notification mechanism
5 The general notification mechanism is built on top of the standard pipe driver
6 whereby it effectively splices notification messages from the kernel into pipes
14 	"General setup"/"General notification queue"
29 additions to the ring - which might end up interleaved with notification
45 Note that when producing a notification, the kernel does not wait for the
54 Notification messages begin with a short header::
62 "type" indicates the source of the notification record and "subtype" indicates
85     notification producer to indicate some meaning specific to the type and
94 Watch List (Notification Source) API
122 Watch Queue (Notification Output) API
125 A "watch queue" is the buffer allocated by an application that notification
146 thus the buffer, into which notification records should be written.  The watch
162 struct watch_notification::info when and if the notification is written into
180     Subscribe a watch to a watch list (notification source).  The
191     watch queue (``wqueue``) and object identifier (``id``).  A notification
199     inaccessible to new watches by this point.  A notification
204 Notification Posting API
207 To post a notification to watch list so that the subscribed watches can see it,
215 The notification should be preformatted and a pointer to the header (``n``)
216 should be passed in.  The notification may be larger than this and the size in
225 Only watches that have the same ID set in them will see this notification.
276     notification record.  The notification is only written into the buffer if::