Searched refs:exchange (Results 1 – 25 of 103) sorted by relevance
12345
/linux-6.12.1/scripts/atomic/kerneldoc/ |
D | try_cmpxchg | 3 * ${class}${atomicname}() - atomic compare and exchange with ${desc_order} ordering 14 * Return: @true if the exchange occured, @false otherwise.
|
D | xchg | 3 * ${class}${atomicname}() - atomic exchange with ${desc_order} ordering
|
D | cmpxchg | 3 * ${class}${atomicname}() - atomic compare and exchange with ${desc_order} ordering
|
/linux-6.12.1/Documentation/networking/ |
D | nfc.rst | 17 - Low-level data exchange; 22 data exchange. 26 The low-level data exchange interface is provided by the new socket family 36 | data exchange | operations 72 exchange operation.
|
/linux-6.12.1/Documentation/userspace-api/media/v4l/ |
D | rw.rst | 23 setup to exchange data. It permits command line stunts like this (the 33 must implement one I/O method if they exchange data with applications,
|
D | format.rst | 13 Different devices exchange different kinds of data with applications, 19 data exchange. Negotiation means the application asks for a particular
|
D | biblio.rst | 104 …709-5 "Parameter values for the HDTV standards for production and international programme exchange" 263 …s for ultra-high definition television systems for production and international programme exchange"
|
D | pixfmt-intro.rst | 7 In order to exchange images between drivers and applications, it is
|
/linux-6.12.1/Documentation/networking/device_drivers/atm/ |
D | cxacru.rst | 79 - "exchange" 119 [4942259.656262] ATM dev 0: ADSL line: exchange
|
/linux-6.12.1/drivers/staging/fieldbus/ |
D | Kconfig | 7 Fieldbus device (client) adapters allow data exchange with a PLC aka.
|
/linux-6.12.1/Documentation/driver-api/surface_aggregator/ |
D | ssh.rst | 100 messages corresponding to an exchange are, in part, identified by having the 140 Each exchange begins with |SYN|, followed by a |DATA_SEQ|- or 142 case of a |DATA_NSQ|-type frame, the exchange is then finished. In case of a 156 corresponding to a single exchange thus relies on the sequence ID as well as 161 An example exchange might look like this: 171 previous payload. In case of an error, the exchange would look like this: 189 ``tx`` results again in a valid exchange. Currently, no longer exchanges are
|
/linux-6.12.1/Documentation/userspace-api/ |
D | index.rst | 46 dma-buf-alloc-exchange
|
/linux-6.12.1/net/lapb/ |
D | Kconfig | 11 connection service to exchange data frames with one other host, and
|
/linux-6.12.1/Documentation/devicetree/bindings/mailbox/ |
D | xgene-slimpro-mailbox.txt | 3 interrupt based door bell mechanism and can exchange simple messages using the
|
/linux-6.12.1/drivers/ntb/ |
D | Kconfig | 34 This is a transport driver that enables connected systems to exchange
|
/linux-6.12.1/drivers/isdn/mISDN/ |
D | Kconfig | 37 - dynamic IP exchange, if one or both peers have dynamic IPs
|
/linux-6.12.1/drivers/firmware/imx/ |
D | Kconfig | 11 exchange information with DSP side.
|
/linux-6.12.1/Documentation/infiniband/ |
D | opa_vnic.rst | 14 permitted to exchange encapsulated Ethernet packets across a particular 18 nodes across the fabric exchange encapsulated Ethernet packets over a
|
/linux-6.12.1/drivers/net/hamradio/ |
D | Kconfig | 7 KISS is a protocol used for the exchange of data between a computer 24 6pack is a transmission protocol for the data exchange between your
|
/linux-6.12.1/Documentation/arch/arm/ |
D | kernel_user_helpers.rst | 144 Return zero if `*ptr` was changed or non-zero if no exchange happened. 237 changed or non-zero if no exchange happened.
|
/linux-6.12.1/Documentation/ABI/testing/ |
D | sysfs-class-net-qmi | 13 '802.3' mode, and the driver expects to exchange
|
/linux-6.12.1/Documentation/driver-api/ |
D | ntb.rst | 11 exchange a small amount of information at a fixed address. Message registers can 128 across the ntb, to exchange packets of network data. The Transport client 129 establishes a logical link to the peer, and creates queue pairs to exchange
|
/linux-6.12.1/security/landlock/ |
D | fs.c | 1091 const bool removable, const bool exchange) in current_check_refer_path() argument 1107 if (exchange) { in current_check_refer_path() 1172 exchange ? new_dentry : NULL)) in current_check_refer_path()
|
/linux-6.12.1/drivers/staging/fieldbus/Documentation/ |
D | fieldbus_dev.txt | 33 exchange with a PLC aka "Fieldbus Controller" via process data memory.
|
/linux-6.12.1/Documentation/filesystems/xfs/ |
D | xfs-online-fsck-design.rst | 3991 reverse mapping information up to date with every exchange of mappings. 3992 Therefore, it can only exchange one mapping per transaction, and each 4001 For this use case, an incomplete exchange will not result in a user-visible 4013 of log intent item to track the progress of an operation to exchange two file 4015 The new exchange operation type chains together the same transactions used by 4018 This new functionality is called the file contents exchange (xfs_exchrange) 4021 The new log item records the progress of the exchange to ensure that once an 4022 exchange begins, it will always run to completion, even there are 4029 `file contents exchange 4079 The goal is to exchange all file fork mappings between two file fork offset [all …]
|
12345