Home
last modified time | relevance | path

Searched refs:notification (Results 1 – 25 of 174) sorted by relevance

1234567

/Linux-v5.10/Documentation/ABI/stable/
Dthermal-notification1 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-v5.10/Documentation/networking/
Dmsg_zerocopy.rst23 notification overhead. As a result, MSG_ZEROCOPY is generally only
33 The kernel returns a notification when it is safe to modify data.
106 The notification itself is a simple scalar value. Each socket
156 When a new notification is about to be queued, it checks whether the
157 new value extends the range of the notification at the tail of the
158 queue. If so, it drops the new notification packet and instead increases
159 the range upper value of the outstanding notification.
162 notification can be squashed into the previous one, so that no more
163 than one notification is outstanding at any one point.
173 read_notification() call in the previous snippet. A notification
[all …]
/Linux-v5.10/Documentation/
Dwatch_queue.rst2 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-v5.10/drivers/staging/media/imx/
Dimx-media-dev-common.c251 unsigned int notification) in imx_media_link_notify() argument
262 ret = v4l2_pipeline_link_notify(link, flags, notification); in imx_media_link_notify()
286 if (notification == MEDIA_DEV_NOTIFY_PRE_LINK_CH && in imx_media_link_notify()
296 } else if (notification == MEDIA_DEV_NOTIFY_POST_LINK_CH && in imx_media_link_notify()
313 static void imx_media_notify(struct v4l2_subdev *sd, unsigned int notification, in imx_media_notify() argument
319 if (notification != V4L2_DEVICE_NOTIFY_EVENT) in imx_media_notify()
/Linux-v5.10/include/media/
Dv4l2-mc.h179 unsigned int notification);
211 unsigned int notification) in v4l2_pipeline_link_notify() argument
Dv4l2-device.h54 unsigned int notification, void *arg);
238 unsigned int notification, void *arg) in v4l2_subdev_notify() argument
241 sd->v4l2_dev->notify(sd, notification, arg); in v4l2_subdev_notify()
/Linux-v5.10/Documentation/firmware-guide/acpi/
Dacpi-lid.rst32 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-v5.10/Documentation/filesystems/
Ddnotify.rst9 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-v5.10/fs/notify/fanotify/
DKconfig3 bool "Filesystem wide access notification"
9 notification system which differs from inotify in that it sends
/Linux-v5.10/Documentation/hwmon/
Dacpi_power_meter.rst32 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-v5.10/Documentation/power/
Dpm_qos_interface.rst40 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-v5.10/ipc/
Dmqueue.c1301 static int do_mq_notify(mqd_t mqdes, const struct sigevent *notification) in do_mq_notify() argument
1310 audit_mq_notify(mqdes, notification); in do_mq_notify()
1314 if (notification != NULL) { in do_mq_notify()
1315 if (unlikely(notification->sigev_notify != SIGEV_NONE && in do_mq_notify()
1316 notification->sigev_notify != SIGEV_SIGNAL && in do_mq_notify()
1317 notification->sigev_notify != SIGEV_THREAD)) in do_mq_notify()
1319 if (notification->sigev_notify == SIGEV_SIGNAL && in do_mq_notify()
1320 !valid_signal(notification->sigev_signo)) { in do_mq_notify()
1323 if (notification->sigev_notify == SIGEV_THREAD) { in do_mq_notify()
1332 notification->sigev_value.sival_ptr, in do_mq_notify()
[all …]
/Linux-v5.10/Documentation/driver-api/thermal/
Dx86_pkg_temperature_thermal.rst25 user mode can receive notification via thermal notification mechanism and can
/Linux-v5.10/Documentation/core-api/
Dmemory-hotplug.rst10 Hotplugging events are sent to a notification queue.
12 There are six types of notification defined in ``include/linux/memory.h``:
85 further processing of the notification queue.
87 NOTIFY_STOP stops further processing of the notification queue.
/Linux-v5.10/drivers/thermal/intel/
Dintel_soc_dts_iosf.c406 bool notification; in intel_soc_dts_iosf_init() local
429 notification = false; in intel_soc_dts_iosf_init()
431 notification = true; in intel_soc_dts_iosf_init()
435 notification, trip_count, in intel_soc_dts_iosf_init()
DKconfig21 notification methods.
44 notification methods.The other trip is a critical trip point, which
/Linux-v5.10/fs/notify/
DMakefile2 obj-$(CONFIG_FSNOTIFY) += fsnotify.o notification.o group.o mark.o \
/Linux-v5.10/fs/notify/dnotify/
DKconfig7 Dnotify is a directory-based per-fd file change notification system
/Linux-v5.10/drivers/pci/hotplug/
Dacpiphp_ibm.c77 struct notification { struct
95 static struct notification ibm_note; argument
255 struct notification *note = context; in ibm_handle_events()
/Linux-v5.10/include/linux/
Daudit.h400 extern void __audit_mq_notify(mqd_t mqdes, const struct sigevent *notification);
470 static inline void audit_mq_notify(mqd_t mqdes, const struct sigevent *notification) in audit_mq_notify() argument
473 __audit_mq_notify(mqdes, notification); in audit_mq_notify()
640 const struct sigevent *notification) in audit_mq_notify() argument
/Linux-v5.10/Documentation/admin-guide/cgroup-v1/
Dmemory.rst811 Memory cgroup implements memory thresholds using the cgroups notification
830 memory.oom_control file is for OOM notification and other controls.
832 Memory cgroup implements OOM notifier using the cgroup notification
833 API (See cgroups.txt). It allows to register multiple OOM notification
834 delivery and gets notification when OOM happens.
844 OOM notification doesn't work for the root cgroup.
882 maintaining cache level. Upon notification, the program (typically
902 notification, i.e. groups A and B will not receive it. This is done to avoid
905 notification only if there are no event listers for group C.
916 example, groups A, B, and C will receive notification of memory pressure.
[all …]
/Linux-v5.10/Documentation/virt/kvm/
Ds390-diag.rst52 Subcode 0 - s390-virtio notification and early console printk
61 Subcode 3 - virtio-ccw notification
/Linux-v5.10/virt/kvm/
DKconfig26 # Toggle to switch between direct notification and batch job
/Linux-v5.10/fs/notify/inotify/
DKconfig13 unmount notification.
/Linux-v5.10/include/uapi/sound/
Dfirewire.h28 unsigned int notification; /* DICE-specific bits */ member

1234567