| /linux-6.12.1/Documentation/networking/ |
| 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-6.12.1/Documentation/ABI/testing/ |
| 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.
|
| 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-6.12.1/Documentation/ABI/stable/ |
| 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-6.12.1/Documentation/core-api/ |
| 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 …]
|
| D | memory-hotplug.rst | 10 Hotplugging events are sent to a notification queue.
12 There are six types of notification defined in ``include/linux/memory.h``:
82 further processing of the notification queue.
84 NOTIFY_STOP stops further processing of the notification queue.
|
| /linux-6.12.1/drivers/soc/qcom/ |
| D | pmic_glink_altmode.c | 48 __le32 notification; member
263 u32 notification; in pmic_glink_altmode_sc8180xp_notify() local
278 notification = le32_to_cpu(msg->notification); in pmic_glink_altmode_sc8180xp_notify()
279 port = FIELD_GET(SC8180X_PORT_MASK, notification); in pmic_glink_altmode_sc8180xp_notify()
280 orientation = FIELD_GET(SC8180X_ORIENTATION_MASK, notification); in pmic_glink_altmode_sc8180xp_notify()
281 mux = FIELD_GET(SC8180X_MUX_MASK, notification); in pmic_glink_altmode_sc8180xp_notify()
282 mode = FIELD_GET(SC8180X_MODE_MASK, notification); in pmic_glink_altmode_sc8180xp_notify()
283 hpd_state = FIELD_GET(SC8180X_HPD_STATE_MASK, notification); in pmic_glink_altmode_sc8180xp_notify()
284 hpd_irq = FIELD_GET(SC8180X_HPD_IRQ_MASK, notification); in pmic_glink_altmode_sc8180xp_notify()
|
| /linux-6.12.1/tools/testing/selftests/net/packetdrill/ |
| D | tcp_zerocopy_fastopen-client.pkt | 5 // kernel returns the notification ID.
9 // zerocopy notification counter is not incremented. Verify this too.
22 // Read from error queue: no zerocopy notification
43 // Read from error queue: now has first zerocopy notification
|
| D | tcp_zerocopy_fastopen-server.pkt | 5 // kernel returns the notification ID.
29 // Read from error queue: now has first zerocopy notification
|
| 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-6.12.1/Documentation/wmi/ |
| 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
96 holding the notification ID of the event. This method should be evaluated every
97 time an ACPI notification is received, since some ACPI implementations use a
|
| /linux-6.12.1/drivers/staging/media/imx/ |
| 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-6.12.1/Documentation/firmware-guide/acpi/ |
| 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-6.12.1/include/media/ |
| D | v4l2-mc.h | 194 unsigned int notification);
226 unsigned int notification) in v4l2_pipeline_link_notify() argument
|
| D | v4l2-device.h | 52 unsigned int notification, void *arg);
239 unsigned int notification, void *arg) in v4l2_subdev_notify() argument
242 sd->v4l2_dev->notify(sd, notification, arg); in v4l2_subdev_notify()
|
| /linux-6.12.1/drivers/firmware/arm_scmi/vendors/imx/ |
| D | imx95.rst | 50 - Get notification on ON/OFF button activity.
324 | |Set to 1 to send notification. |
325 | |Set to 0 if no notification. |
327 | |Set to 1 to send notification. |
328 | |Set to 0 if no notification. |
330 | |Set to 1 to send notification. |
331 | |Set to 0 if no notification |
337 |int32 status |SUCCESS: notification configuration was successfully |
358 | |Set to 1 to send notification. |
359 | |Set to 0 if no notification |
[all …]
|
| /linux-6.12.1/Documentation/filesystems/ |
| 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-6.12.1/fs/notify/fanotify/ |
| D | Kconfig | 3 bool "Filesystem wide access notification"
9 notification system which differs from inotify in that it sends
|
| /linux-6.12.1/Documentation/hwmon/ |
| D | acpi_power_meter.rst | 32 socket and a poll notification will be sent to the appropriate
42 the netlink event socket and a poll notification will be sent to the
49 well as sent as a poll notification to a sysfs file. The events are as
|
| /linux-6.12.1/Documentation/power/ |
| D | pm_qos_interface.rst | 40 value and recompute the new aggregated target, calling the notification tree
45 and call the notification tree if the target was changed as a result of
56 Adds a notification callback function to the CPU latency QoS. The callback is
60 Removes the notification callback function from the CPU latency QoS.
115 value and recompute the new aggregated target, calling the notification
120 and call the notification trees if the target was changed as a result of
168 The per-device PM QoS framework has a per-device notification tree.
171 Adds a notification callback function for the device for a particular request
178 Removes the notification callback function for the device.
|
| /linux-6.12.1/ipc/ |
| D | mqueue.c | 1317 static int do_mq_notify(mqd_t mqdes, const struct sigevent *notification) in do_mq_notify() argument
1326 audit_mq_notify(mqdes, notification); in do_mq_notify()
1330 if (notification != NULL) { in do_mq_notify()
1331 if (unlikely(notification->sigev_notify != SIGEV_NONE && in do_mq_notify()
1332 notification->sigev_notify != SIGEV_SIGNAL && in do_mq_notify()
1333 notification->sigev_notify != SIGEV_THREAD)) in do_mq_notify()
1335 if (notification->sigev_notify == SIGEV_SIGNAL && in do_mq_notify()
1336 !valid_signal(notification->sigev_signo)) { in do_mq_notify()
1339 if (notification->sigev_notify == SIGEV_THREAD) { in do_mq_notify()
1348 notification->sigev_value.sival_ptr, in do_mq_notify()
[all …]
|
| /linux-6.12.1/Documentation/driver-api/thermal/ |
| D | x86_pkg_temperature_thermal.rst | 25 user mode can receive notification via thermal notification mechanism and can
|
| /linux-6.12.1/Documentation/admin-guide/ |
| 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-6.12.1/drivers/staging/media/tegra-video/ |
| 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-6.12.1/fs/notify/ |
| D | Makefile | 2 obj-$(CONFIG_FSNOTIFY) += fsnotify.o notification.o group.o mark.o \
|