Searched full:transaction (Results 1 – 25 of 122) sorted by relevance
12345
| /Documentation/filesystems/xfs/ |
| D | xfs-delayed-logging-design.rst | 13 themselves with the general concepts of how transaction processing in XFS works.
16 transaction reservations are structured and accounted, and then move into how we
59 transactions. Permanent transaction reservations can take reservations that span
68 In the code, a one-shot transaction pattern looks somewhat like this::
72 <join item to transaction>
76 As items are modified in the transaction, the dirty regions in those items are
77 tracked via the transaction handle. Once the transaction is committed, all
79 space that was taken at the transaction allocation time.
81 In contrast, a permanent transaction is made up of multiple linked individual
97 While this might look similar to a one-shot transaction, there is an important
[all …]
|
| /Documentation/netlink/specs/ |
| D | binder.yaml | 15 Attributes included within a transaction failure report. The elements
16 correspond directly with the specific transaction that failed, along
27 doc: The binder context where the transaction occurred.
51 doc: When present, indicates the failed transaction is a reply.
55 doc: The bitmask of enum transaction_flags from the transaction.
59 doc: The application-defined code from the transaction.
63 doc: The transaction payload size in bytes.
71 binder transaction failures. The generated report provides the full
72 details of the specific transaction that failed. The intention is for
|
| /Documentation/arch/powerpc/ |
| D | transactional_memory.rst | 21 A simple transaction looks like this::
41 /* Retry the transaction if it failed because it conflicted with
50 example, the transaction completes as though it were normal straight-line code
58 transaction, the transaction will be aborted by the CPU. Register and memory
66 Causes of transaction aborts
78 Syscalls made from within an active transaction will not be performed and the
79 transaction will be doomed by the kernel with the failure code TM_CAUSE_SYSCALL
82 Syscalls made from within a suspended transaction are performed as normal and
83 the transaction is not explicitly doomed by the kernel. However, what the
84 kernel does to perform the syscall may result in the transaction being doomed
[all …]
|
| D | syscall64-abi.rst | 88 transaction state, and the syscall can affect the behavior of the transaction.
94 in the transaction being doomed by hardware.
101 be performed and the transaction will be doomed by the kernel with the
153 may or may not result in the transaction being doomed by hardware.
|
| /Documentation/filesystems/ |
| D | journalling.rst | 42 this use jbd2_journal_start() which returns a transaction handle.
45 which indicates the end of a transaction are nestable calls, so you can
46 reenter a transaction if necessary, but remember you must call
48 jbd2_journal_start() before the transaction is completed (or more
52 Inside each transaction you need to wrap the modifications to the
59 uncommitted transaction. At this point you are at last ready to modify a
74 single outstanding transaction at any one time, remember nothing commits
76 the transaction at the end of each file/inode/address etc. operation you
83 if there isn't enough space in the journal for your transaction (based
96 transaction. I advise having a look at at least ext4_jbd.h to see the
[all …]
|
| /Documentation/i2c/busses/ |
| D | i2c-mlxcpld.rst | 19 The next transaction types are supported:
29 Bits [6:5] - transaction length. b01 - 72B is supported,
43 It should be written last as it triggers an I2C transaction.
45 Number of data bytes to write in read transaction
47 Number of address bytes to write in read transaction.
49 Bit 0 - transaction is completed.
52 For write transaction address is specified in four first bytes
54 For read transactions address is sent in a separate transaction and
|
| /Documentation/locking/ |
| D | ww-mutex-design.rst | 36 In the RDBMS literature, a reservation ticket is associated with a transaction.
39 If the transaction holding the lock is younger, the locking transaction waits.
40 If the transaction holding the lock is older, the locking transaction backs off
43 If the transaction holding the lock is younger, the locking transaction
44 wounds the transaction holding the lock, requesting it to die.
45 If the transaction holding the lock is older, it waits for the other
46 transaction. Hence Wound-Wait.
47 The two algorithms are both fair in that a transaction will eventually succeed.
53 running transaction. Note that this is not the same as process preemption. A
54 Wound-Wait transaction is considered preempted when it dies (returning
[all …]
|
| /Documentation/i2c/ |
| D | i2c-address-translators.rst | 53 in the transaction and based on the alias table.
66 Transaction:
68 - Slave X driver requests a transaction (on adapter B), slave address 0x10
71 - Physical I2C transaction on bus A, slave address 0x20
72 - ATR chip detects transaction on address 0x20, finds it in table,
73 propagates transaction on bus B with address translated to 0x10,
75 - Slave X chip (on bus B) detects transaction at its own physical
|
| D | i2c-protocol.rst | 25 Simple send transaction
33 Simple receive transaction
47 condition P a start condition S is sent and the transaction continues.
70 In a combined transaction, no 'S Addr Wr/Rd [A]' is generated at some
|
| D | dev-interface.rst | 69 /* ERROR HANDLING: I2C transaction failed */
82 /* ERROR HANDLING: I2C transaction failed */
87 /* ERROR HANDLING: I2C transaction failed */
94 transactions (mixing read and write messages in the same transaction)
128 Do combined read/write transaction without stop in between.
201 performs an SMBus transaction using i2c-core-smbus.c:i2c_smbus_xfer().
|
| /Documentation/ABI/testing/ |
| D | debugfs-driver-habanalabs | 44 transaction while reading from the file generates a read
45 transaction. This custom interface is needed (instead of using
48 move the bar before and after the transaction.
59 write transaction while reading from the file generates a read
60 transaction. This custom interface is needed (instead of using
63 move the bar before and after the transaction.
105 Description: Specify the size of the DMA transaction when using DMA to read
139 Description: Sets I2C device address for I2C transaction that is generated
147 Description: Sets I2C bus address for I2C transaction that is generated by
155 Description: Triggers an I2C transaction that is generated by the device's
[all …]
|
| D | sysfs-bus-iio-ina2xx-adc | 12 save the additional i2c transaction, which will improve the bandwidth
|
| /Documentation/arch/xtensa/ |
| D | atomctl.rst | 22 doing a Cached (WB) transaction and use the Memory RCW for un-cached
48 1 RCW Transaction RCW Transaction RCW Transaction
|
| /Documentation/filesystems/ext4/ |
| D | journal.rst | 11 data transaction is fully written to the disk and flushed from the disk write
70 - One transaction
73 Notice that a transaction begins with either a descriptor and some data,
74 or a block revocation list. A finished transaction always ends with a
76 transaction will be discarded during replay.
102 - One transaction
131 - The transaction ID that goes with this block.
145 written through the journal during a transaction.
148 transaction.
244 - Limit of journal blocks per transaction. (Not used?)
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | persistent-data.rst | 42 The transaction manager
45 dm-transaction-manager.[hc]
49 transaction manager is by shadowing an existing block (ie. doing
51 the same transaction so performance is reasonable. The commit method
|
| /Documentation/driver-api/dmaengine/ |
| D | client.rst | 23 - Get a descriptor for transaction
25 - Submit the transaction
76 3. Get a descriptor for transaction
98 the given transaction.
152 For slave DMA, the subsequent transaction may not be available
155 transaction.
260 4. Submit the transaction
287 issue_pending API. If channel is idle then the first transaction in
360 completion of a specific DMA transaction.
|
| D | provider.rst | 134 transaction descriptor is done.
145 Supported transaction types
148 The next thing you need is to set which transaction types your device
152 various types of transaction supported, and you need to modify this
154 transaction types you support as an argument.
232 we just have a single transaction type that is supposed to
309 associated with a transaction. The DMA controller role is to transfer the
370 implement, obviously depend on the transaction types you reported as
419 that is supposed to push the current transaction descriptor to a
424 transaction has completed. In the earlier code the function pointer
[all …]
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-mux-gpmux.yaml | 55 - between setup of the multiplexer and the child bus I2C transaction
56 - between the child bus I2C transaction and releasing of the multiplexer
61 for the full duration of the complete multiplexed I2C transaction (i.e.
65 adapter for the complete multiplexed I2C transaction.
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | st,stm32-fmc2-ebi-props.yaml | 14 st,fmc2-ebi-cs-transaction-type:
103 end of current read/write transaction and the next transaction.
132 write transaction and the next transaction in nanoseconds.
|
| /Documentation/devicetree/bindings/net/ |
| D | brcm,mdio-mux-iproc.yaml | 14 external to SoCs and could accept MDIO transaction compatible to C-22 or
16 properties as well to generate desired MDIO transaction on appropriate bus.
|
| /Documentation/driver-api/ |
| D | firewire.rst | 37 Firewire core transaction interfaces
40 .. kernel-doc:: drivers/firewire/core-transaction.c
|
| /Documentation/core-api/ |
| D | gfp_mask-from-fs-io.rst | 17 transaction context).
45 lock shared with the reclaim context or when a transaction context
|
| /Documentation/devicetree/bindings/ata/ |
| D | baikal,bt1-ahci.yaml | 61 transaction size can't exceed 16 beats (AxLEN[3:0]).
68 transaction size can't exceed 16 beats (AxLEN[3:0]).
|
| /Documentation/usb/ |
| D | ehci.rst | 22 interact with the EHCI controller through a "Transaction Translator"
60 transaction translators (TTs) in USB 2.0 hubs. But you may find bugs.
65 Full Speed Isochronous transfer support, through transaction translators,
66 is not yet available. Note that split transaction support for ISO
146 transaction translators are in use; some drivers have been seen to behave
|
| /Documentation/hwmon/ |
| D | lm90.rst | 615 ADM1032 chip. However, in the case of a combined transaction (SMBus Read
618 of the message belongs to a different transaction. As a result, the CRC
622 the bus supports the SMBus Send Byte and Receive Byte transaction types.
628 SMBus Send Byte transaction with PEC is similar to a Write Byte transaction
634 to use two SMBus transaction for reads, this overhead jumps to +50%. Worse,
636 transaction completion, effectively doubling the register cache refresh time.
|
12345