Lines Matching refs:events

104 Any text format data consists of a stream of events, such as URB submission,
137   events.
195 only the events are delivered in binary format. Each event is sent in
225 These events can be received from a character device by reading with read(2),
242 events contain no data, so if this call returns zero, it does not mean that
243 no events are available.
254 The member "queued" refers to the number of events currently queued in the
255 buffer (and not to the number of events processed since the last reset).
257 The member "dropped" is the number of events lost since the last call
274 These calls wait for events to arrive if none were in the kernel buffer,
296 	uint32_t *offvec;	/* Vector of events fetched */
297 	uint32_t nfetch;	/* Number of events to fetch (out: fetched) */
298 	uint32_t nflush;	/* Number of events to flush */
303 First, it removes and discards up to nflush events from the kernel buffer.
304 The actual number of events discarded is returned in nflush.
315 This call removes a number of events from the kernel buffer. Its argument
316 is the number of events to remove. If the buffer contains fewer events
317 than requested, all events present are removed, and no error is reported.
318 This works when no events are available too.
352 Thus, the main idea is to execute only one ioctl per N events.