| /linux/Documentation/networking/ |
| H A D | msg_zerocopy.rst | 24 notification overhead. As a result, MSG_ZEROCOPY is generally only 34 The kernel returns a notification when it is safe to modify data. 107 The notification itself is a simple scalar value. Each socket 157 When a new notification is about to be queued, it checks whether the 158 new value extends the range of the notification at the tail of the 159 queue. If so, it drops the new notification packet and instead increases 160 the range upper value of the outstanding notification. 163 notification can be squashed into the previous one, so that no more 164 than one notification is outstanding at any one point. 174 read_notification() call in the previous snippet. A notification [all …]
|
| /linux/Documentation/core-api/ |
| H A D | watch_queue.rst | 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 62 "type" indicates the source of the notification record and "subtype" indicates 85 notification producer to indicate some meaning specific to the type and 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 [all …]
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-fc_host | 5 These files contain the number of congestion notification 7 performance impact notification (FPIN) event. 15 performance impact notification (FPIN) event. 23 performance impact notification (FPIN) event.
|
| H A D | sysfs-class-fc_remote_ports | 5 These files contain the number of congestion notification 7 performance impact notification (FPIN) event. 15 performance impact notification (FPIN) event. 23 performance impact notification (FPIN) event.
|
| /linux/Documentation/ABI/stable/ |
| H A D | thermal-notification | 1 What: A notification mechanism for thermal related events 3 This interface enables notification for thermal related events. 4 The notification is in the form of a netlink event.
|
| /linux/drivers/soc/qcom/ |
| H A D | pmic_glink_altmode.c | 49 __le32 notification; member 270 u32 notification; in pmic_glink_altmode_sc8180xp_notify() local 285 notification = le32_to_cpu(msg->notification); in pmic_glink_altmode_sc8180xp_notify() 286 port = FIELD_GET(SC8180X_PORT_MASK, notification); in pmic_glink_altmode_sc8180xp_notify() 287 orientation = FIELD_GET(SC8180X_ORIENTATION_MASK, notification); in pmic_glink_altmode_sc8180xp_notify() 288 mux = FIELD_GET(SC8180X_MUX_MASK, notification); in pmic_glink_altmode_sc8180xp_notify() 289 mode = FIELD_GET(SC8180X_MODE_MASK, notification); in pmic_glink_altmode_sc8180xp_notify() 290 hpd_state = FIELD_GET(SC8180X_HPD_STATE_MASK, notification); in pmic_glink_altmode_sc8180xp_notify() 291 hpd_irq = FIELD_GET(SC8180X_HPD_IRQ_MASK, notification); in pmic_glink_altmode_sc8180xp_notify()
|
| /linux/tools/testing/selftests/net/packetdrill/ |
| H A D | tcp_zerocopy_fastopen-client.pkt | 5 // kernel returns the notification ID. 9 // zerocopy notification counter is not incremented. Verify this too. 24 // Read from error queue: no zerocopy notification 45 // Read from error queue: now has first zerocopy notification
|
| H A D | tcp_zerocopy_fastopen-server.pkt | 5 // kernel returns the notification ID. 31 // Read from error queue: now has first zerocopy notification
|
| H A D | tcp_zerocopy_closed.pkt | 7 // First send on a closed socket and wait for (absent) notification. 8 // Then connect and send and verify that notification nr. is zero.
|
| /linux/Documentation/wmi/ |
| H A D | acpi-interface.rst | 32 0x10 2 2 character method ID or single byte notification ID. 37 The WMI object flags control whether the method or notification ID is used: 42 - 0x8: Data block describes a WMI event, use notification ID instead 46 The method/notification ID is used to construct the ACPI method names used for 81 the ACPI method are the notification ID of the data block describing the WMI 103 holding the notification ID of the event. This method should be evaluated every 104 time an ACPI notification is received, since some ACPI implementations use a
|
| /linux/drivers/staging/media/imx/ |
| H A D | imx-media-dev-common.c | 236 unsigned int notification) in imx_media_link_notify() argument 247 ret = v4l2_pipeline_link_notify(link, flags, notification); in imx_media_link_notify() 271 if (notification == MEDIA_DEV_NOTIFY_PRE_LINK_CH && in imx_media_link_notify() 283 } else if (notification == MEDIA_DEV_NOTIFY_POST_LINK_CH && in imx_media_link_notify() 302 static void imx_media_notify(struct v4l2_subdev *sd, unsigned int notification, in imx_media_notify() argument 308 if (notification != V4L2_DEVICE_NOTIFY_EVENT) in imx_media_notify()
|
| /linux/Documentation/firmware-guide/acpi/ |
| H A D | acpi-lid.rst | 32 the lid state upon the last lid notification instead of returning the lid 43 changed to "opened". Thus the "opened" notification is not guaranteed. But 45 state is changed to "closed". The "closed" notification is normally used to 71 events and the unreliable initial state notification, Linux users can use 82 notification is missing. 93 control method is not reliable and the initial lid state notification is 97 and the unreliable initial state notification, Linux users should always
|
| /linux/include/media/ |
| H A D | v4l2-mc.h | 194 unsigned int notification); 226 unsigned int notification) in v4l2_pipeline_link_notify() argument
|
| /linux/Documentation/filesystems/ |
| H A D | dnotify.rst | 9 The intention of directory notification is to allow user applications 11 The basic mechanism involves the application registering for notification 28 Usually, the application must reregister after each notification, but 46 The notification should work for any local access to files even if the
|
| /linux/ipc/ |
| H A D | mqueue.c | 1272 static int do_mq_notify(mqd_t mqdes, const struct sigevent *notification) in do_mq_notify() argument 1280 audit_mq_notify(mqdes, notification); in do_mq_notify() 1284 if (notification != NULL) { in do_mq_notify() 1285 if (unlikely(notification->sigev_notify != SIGEV_NONE && in do_mq_notify() 1286 notification->sigev_notify != SIGEV_SIGNAL && in do_mq_notify() 1287 notification->sigev_notify != SIGEV_THREAD)) in do_mq_notify() 1289 if (notification->sigev_notify == SIGEV_SIGNAL && in do_mq_notify() 1290 !valid_signal(notification->sigev_signo)) { in do_mq_notify() 1293 if (notification->sigev_notify == SIGEV_THREAD) { in do_mq_notify() 1302 notification->sigev_value.sival_ptr, in do_mq_notify() [all …]
|
| /linux/Documentation/driver-api/thermal/ |
| H A D | x86_pkg_temperature_thermal.rst | 25 user mode can receive notification via thermal notification mechanism and can
|
| /linux/Documentation/admin-guide/ |
| H A D | filesystem-monitoring.rst | 15 By design, a FAN_FS_ERROR notification exposes sufficient information 26 error that occurred for a file system since the last notification, and 69 notification.
|
| /linux/drivers/staging/media/tegra-video/ |
| H A D | video.c | 30 unsigned int notification, void *arg) in tegra_v4l2_dev_notify() argument 35 if (notification != V4L2_DEVICE_NOTIFY_EVENT) in tegra_v4l2_dev_notify()
|
| /linux/fs/notify/ |
| H A D | Makefile | 2 obj-$(CONFIG_FSNOTIFY) += fsnotify.o notification.o group.o mark.o \
|
| /linux/drivers/pci/hotplug/ |
| H A D | acpiphp_ibm.c | 77 struct notification { struct 95 static struct notification ibm_note; argument 255 struct notification *note = context; in ibm_handle_events()
|
| /linux/fs/notify/dnotify/ |
| H A D | Kconfig | 7 Dnotify is a directory-based per-fd file change notification system
|
| /linux/Documentation/userspace-api/ |
| H A D | seccomp_filter.rst | 127 notification fd, if it is attached, or ``-ENOSYS`` if it is not. See 199 To acquire a notification FD, use the ``SECCOMP_FILTER_FLAG_NEW_LISTENER`` 213 The interface for a seccomp notification fd consists of two structures: 250 seccomp notification fd to receive a ``struct seccomp_notif``, which contains 254 notification also contains the ``data`` passed to seccomp, and a filters flag. 274 The notifying process can be preempted, resulting in the notification being 279 such that when a user notification is received by the supervisor, the notifying 281 are sent prior to the notification being received by userspace are handled
|
| /linux/include/linux/ |
| H A D | audit.h | 435 extern void __audit_mq_notify(mqd_t mqdes, const struct sigevent *notification); 506 static inline void audit_mq_notify(mqd_t mqdes, const struct sigevent *notification) in audit_mq_notify() argument 509 __audit_mq_notify(mqdes, notification); in audit_mq_notify() 684 const struct sigevent *notification) in audit_mq_notify() argument
|
| /linux/Documentation/networking/device_drivers/ethernet/freescale/dpaa2/ |
| H A D | ethernet-driver.rst | 114 When frames are available on ingress queues, a data availability notification 116 queues in the same channel have available frames, only one notification is sent. 117 After a channel fires a notification, is must be explicitly rearmed.
|
| /linux/Documentation/driver-api/ |
| H A D | wbrf.rst | 69 2. Call `amd_wbrf_register_notifier` to register for notification 74 4. On receiving a notification for frequency band change, run
|