Searched refs:idempotent (Results 1 – 7 of 7) sorted by relevance
| /linux-6.15/Documentation/filesystems/ext4/ |
| H A D | journal.rst | 692 Fast commits tags are idempotent in nature provided the recovery code follows 709 Let's take an example of a procedure that is not idempotent and see how fast 710 commits make it idempotent. Consider following sequence of operations: 716 If we store this sequence of operations as is then the replay is not idempotent. 720 sequence of operations is not idempotent. However, as mentioned above, instead 736 replay of last inode 11 tag. Thus, by converting a non-idempotent procedure 737 into a series of idempotent outcomes, fast commits ensured idempotence during
|
| /linux-6.15/kernel/module/ |
| H A D | main.c | 3491 struct idempotent { struct 3502 static bool idempotent(struct idempotent *u, const void *cookie) in idempotent() argument 3506 struct idempotent *existing; in idempotent() 3533 static int idempotent_complete(struct idempotent *u, int ret) in idempotent_complete() 3539 struct idempotent *pos; in idempotent_complete() 3564 static int idempotent_wait_for_completion(struct idempotent *u) in idempotent_wait_for_completion() 3605 struct idempotent idem; in idempotent_init_module() 3611 if (!idempotent(&idem, file_inode(f))) { in idempotent_init_module()
|
| /linux-6.15/Documentation/i2c/ |
| H A D | fault-codes.rst | 12 example. Software often retries idempotent operations after transient
|
| /linux-6.15/tools/memory-model/Documentation/ |
| H A D | simple.txt | 144 lockless and should be idempotent.
|
| /linux-6.15/Documentation/networking/ |
| H A D | napi.rst | 49 The control APIs are not idempotent. Control API calls are safe against
|
| /linux-6.15/Documentation/filesystems/ |
| H A D | vfs.rst | 1344 Must be constant and idempotent, and should not take locks if 1361 be constant and idempotent.
|
| H A D | porting.rst | 367 1, or more times (eg. constant, idempotent).
|