| /kernel/linux/linux-4.19/Documentation/networking/ |
| D | msg_zerocopy.rst | 23 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
114 Notification Reception
148 Notification Batching
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
[all …]
|
| /kernel/linux/linux-5.10/Documentation/networking/ |
| D | msg_zerocopy.rst | 23 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
114 Notification Reception
148 Notification Batching
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
[all …]
|
| /kernel/linux/linux-4.19/drivers/usb/wusbcore/ |
| D | wa-nep.c | 4 * Notification EndPoint support
9 * This part takes care of getting the notification from the hw
14 * four bytes long, and the longest is the HWA Device Notification,
19 * It is not clear if more than one Device Notification can be packed
20 * in a HWA Notification, I assume no because of the wording in
21 * WUSB1.0[8.5.4.2]. In any case, the bigger any notification could
25 * notification arrives we schedule work to a specific, single thread
27 * notification data. After scheduling the work, we rearm the read from
28 * the notification endpoint.
34 * wa_nep_cb() Callback for the notification
[all …]
|
| /kernel/linux/linux-5.10/Documentation/ |
| 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
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
[all …]
|
| /kernel/liteos_a/testsuites/unittest/libc/posix/mqueue/full/ |
| D | It_posix_queue_206.cpp | 40 struct sigevent notification; in Child() local
47 notification.sigev_notify = 5; // 5, User-defined signal. in Child()
49 ret = mq_notify(mqueue, ¬ification); in Child()
53 notification.sigev_notify = SIGEV_THREAD; in Child()
55 ret = mq_notify(mqueue, ¬ification); in Child()
59 notification.sigev_notify = SIGEV_NONE; in Child()
61 ret = mq_notify(-1, ¬ification); in Child()
65 ret = mq_notify(mqueue, ¬ification); in Child()
72 ret = mq_notify(mqueue, ¬ification); in Child()
90 notification.sigev_notify = SIGEV_SIGNAL; in Child()
[all …]
|
| /kernel/linux/linux-5.10/drivers/net/wimax/i2400m/ |
| D | usb-notif.c | 3 * Notification handling
41 * The notification endpoint is active when the device is not in boot
72 * Process a received notification
75 * on the notification endpoint:
114 * URB callback for the notification endpoint
116 * @urb: the urb received from the notification endpoint
152 dev_err(dev, "notification: URB error %d, retrying\n", in i2400mu_notification_cb()
166 dev_err(dev, "notification: cannot submit URB: %d\n", ret); in i2400mu_notification_cb()
174 dev_err(dev, "maximum errors in notification URB exceeded; " in i2400mu_notification_cb()
185 * setup the notification endpoint
[all …]
|
| /kernel/linux/linux-4.19/drivers/net/wimax/i2400m/ |
| D | usb-notif.c | 3 * Notification handling
41 * The notification endpoint is active when the device is not in boot
72 * Process a received notification
75 * on the notification endpoint:
114 * URB callback for the notification endpoint
116 * @urb: the urb received from the notification endpoint
152 dev_err(dev, "notification: URB error %d, retrying\n", in i2400mu_notification_cb()
166 dev_err(dev, "notification: cannot submit URB: %d\n", ret); in i2400mu_notification_cb()
174 dev_err(dev, "maximum errors in notification URB exceeded; " in i2400mu_notification_cb()
185 * setup the notification endpoint
[all …]
|
| /kernel/linux/linux-4.19/drivers/soc/fsl/dpio/ |
| D | dpio.h | 22 * enum dpio_channel_mode - DPIO notification channel mode
23 * @DPIO_NO_CHANNEL: No support for notification channel
35 * @channel_mode: Notification channel mode
36 * @num_priorities: Number of priorities for the notification channel (1-8);
58 * @channel_mode: Notification channel mode
59 * @num_priorities: Number of priorities for the notification channel (1-8);
|
| /kernel/linux/linux-5.10/drivers/soc/fsl/dpio/ |
| D | dpio.h | 22 * enum dpio_channel_mode - DPIO notification channel mode
23 * @DPIO_NO_CHANNEL: No support for notification channel
35 * @channel_mode: Notification channel mode
36 * @num_priorities: Number of priorities for the notification channel (1-8);
58 * @channel_mode: Notification channel mode
59 * @num_priorities: Number of priorities for the notification channel (1-8);
|
| /kernel/linux/linux-5.10/include/uapi/linux/ |
| D | watch_queue.h | 9 #define O_NOTIFICATION_PIPE O_EXCL /* Parameter to pipe2() selecting notification pipe */
16 WATCH_TYPE_KEY_NOTIFY = 1, /* Key change event notification */
26 * Notification record header. This is aligned to 64-bits so that subclasses
50 * Notification filtering rules (IOC_WATCH_QUEUE_SET_FILTER).
67 * Extended watch removal notification. This is used optionally if the type
80 * Type of key/keyring change notification.
94 * Key/keyring notification record.
|
| /kernel/linux/linux-4.19/include/uapi/xen/ |
| D | gntalloc.h | 54 * Sets up an unmap notification within the page, so that the other side can do
56 * mutexes or close notification on communication channels.
58 * Each mapped page only supports one notification; multiple calls referring to
59 * the same page overwrite the previous notification. You must clear the
60 * notification prior to the IOCTL_GNTALLOC_DEALLOC_GREF if you do not want it
70 * notification we are adjusting.
|
| /kernel/linux/linux-5.10/include/uapi/xen/ |
| D | gntalloc.h | 54 * Sets up an unmap notification within the page, so that the other side can do
56 * mutexes or close notification on communication channels.
58 * Each mapped page only supports one notification; multiple calls referring to
59 * the same page overwrite the previous notification. You must clear the
60 * notification prior to the IOCTL_GNTALLOC_DEALLOC_GREF if you do not want it
70 * notification we are adjusting.
|
| /kernel/linux/linux-4.19/Documentation/acpi/ |
| D | acpi-lid.txt | 26 the lid state upon the last lid notification instead of returning the lid
36 changed to "opened". Thus the "opened" notification is not guaranteed. But
38 state is changed to "closed". The "closed" notification is normally used to
60 events and the unreliable initial state notification, Linux users can use
69 notification is missing.
77 control method is not reliable and the initial lid state notification is
81 and the unreliable initial state notification, Linux users should always
|
| /kernel/linux/linux-4.19/drivers/net/wireless/intel/iwlwifi/fw/api/ |
| D | time-event.h | 140 * @TE_V1_NOTIF_HOST_EVENT_START: request/receive notification on event start
141 * @TE_V1_NOTIF_HOST_EVENT_END:request/receive notification on event end
144 * @TE_V1_NOTIF_HOST_FRAG_START: request/receive notification on frag start
145 * @TE_V1_NOTIF_HOST_FRAG_END:request/receive notification on frag end
150 * A notification (both event and fragment) includes a status indicating weather
152 * notification the status is always success. There is no start/end fragment
153 * notification for monolithic events.
200 * A notification (both event and fragment) includes a status indicating weather
202 * notification the status is always success. There is no start/end fragment
203 * notification for monolithic events.
[all …]
|
| /kernel/linux/linux-5.10/drivers/firmware/arm_scmi/ |
| D | notify.h | 4 * notification header file containing some definitions, structures
5 * and function prototypes related to SCMI Notification handling.
21 * @max_payld_sz: Max possible size for the payload of a notification message
22 * @max_report_sz: Max possible size for the report of a notification message
35 * struct scmi_event_ops - Protocol helpers called by the notification core.
|
| D | notify.c | 3 * System Control and Management Interface (SCMI) Notification support
11 * interested agents via notification messages: this is an implementation
15 * An SCMI Notification core instance is initialized for each active platform
25 * events' delivery using the standard Kernel notification chains machinery.
28 * of the SCMI Protocol itself, the underlying notification chains are created
36 * All users provided callbacks and allocated notification-chains are stored in
42 * and is served by its own dedicated notification chain; information contained
51 * Upon reception of a notification message from the platform the SCMI RX ISR
59 * queued items into the proper notification-chain: notifications processing can
64 * Events' information is then extracted from the SCMI Notification messages and
[all …]
|
| /kernel/linux/linux-4.19/Documentation/power/ |
| D | pm_qos_interface.txt | 48 and recompute the new aggregated target, calling the notification tree if the
53 call the notification tree if the target was changed as a result of removing
64 Adds a notification callback function to the PM QoS class. The callback is
68 Removes the notification callback function for the PM QoS class.
118 and recompute the new aggregated target, calling the notification trees if the
123 call the notification trees if the target was changed as a result of removing
164 Notification mechanisms:
165 The per-device PM QoS framework has a per-device notification tree.
168 Adds a notification callback function for the device.
173 Removes the notification callback function for the device.
|
| /kernel/linux/linux-5.10/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
166 Notification mechanisms:
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.
|
| /kernel/linux/linux-4.19/net/sctp/ |
| D | ulpevent.c | 124 * provided by this notification.
143 * head room to use as notification. in sctp_ulpevent_make_assoc_change()
155 /* Include the notification structure */ in sctp_ulpevent_make_assoc_change()
201 * This field is the total length of the notification data, including in sctp_ulpevent_make_assoc_change()
202 * the notification header. in sctp_ulpevent_make_assoc_change()
287 * This field is the total length of the notification data, including in sctp_ulpevent_make_peer_addr_change()
288 * the notification header. in sctp_ulpevent_make_peer_addr_change()
354 /* Create and initialize an SCTP_REMOTE_ERROR notification.
389 * notification with. in sctp_ulpevent_make_remote_error()
421 /* Create and initialize a SCTP_SEND_FAILED notification.
[all …]
|
| /kernel/linux/linux-5.10/net/sctp/ |
| D | ulpevent.c | 109 * provided by this notification.
128 * head room to use as notification. in sctp_ulpevent_make_assoc_change()
140 /* Include the notification structure */ in sctp_ulpevent_make_assoc_change()
186 * This field is the total length of the notification data, including in sctp_ulpevent_make_assoc_change()
187 * the notification header. in sctp_ulpevent_make_assoc_change()
272 * This field is the total length of the notification data, including in sctp_ulpevent_make_peer_addr_change()
273 * the notification header. in sctp_ulpevent_make_peer_addr_change()
358 /* Create and initialize an SCTP_REMOTE_ERROR notification.
393 * notification with. in sctp_ulpevent_make_remote_error()
425 /* Create and initialize a SCTP_SEND_FAILED notification.
[all …]
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-4.19/Documentation/filesystems/ |
| D | dnotify.txt | 1 Linux Directory Notification
6 The intention of directory notification is to allow user applications
8 The basic mechanism involves the application registering for notification
23 Usually, the application must reregister after each notification, but
41 The notification should work for any local access to files even if the
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-4.19/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.
|
| /kernel/linux/linux-5.10/drivers/net/wireless/intel/iwlwifi/fw/api/ |
| D | time-event.h | 142 * @TE_V1_NOTIF_HOST_EVENT_START: request/receive notification on event start
143 * @TE_V1_NOTIF_HOST_EVENT_END:request/receive notification on event end
146 * @TE_V1_NOTIF_HOST_FRAG_START: request/receive notification on frag start
147 * @TE_V1_NOTIF_HOST_FRAG_END:request/receive notification on frag end
152 * A notification (both event and fragment) includes a status indicating weather
154 * notification the status is always success. There is no start/end fragment
155 * notification for monolithic events.
202 * A notification (both event and fragment) includes a status indicating weather
204 * notification the status is always success. There is no start/end fragment
205 * notification for monolithic events.
[all …]
|