Searched refs:idempotent (Results 1 – 7 of 7) sorted by relevance
| /Linux-v6.6/Documentation/filesystems/ext4/ |
| 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-v6.6/kernel/module/ |
| D | main.c | 3061 struct idempotent { struct
3072 static bool idempotent(struct idempotent *u, const void *cookie) in idempotent() argument
3076 struct idempotent *existing; in idempotent()
3103 static int idempotent_complete(struct idempotent *u, int ret) in idempotent_complete()
3109 struct idempotent *pos; in idempotent_complete()
3153 struct idempotent idem; in idempotent_init_module()
3159 if (idempotent(&idem, file_inode(f))) { in idempotent_init_module()
|
| /Linux-v6.6/Documentation/i2c/ |
| D | fault-codes.rst | 12 example. Software often retries idempotent operations after transient
|
| /Linux-v6.6/Documentation/networking/ |
| D | napi.rst | 49 The control APIs are not idempotent. Control API calls are safe against
|
| /Linux-v6.6/tools/memory-model/Documentation/ |
| D | simple.txt | 144 lockless and should be idempotent.
|
| /Linux-v6.6/Documentation/filesystems/ |
| D | vfs.rst | 1323 Must be constant and idempotent, and should not take locks if
1340 be constant and idempotent.
|
| D | porting.rst | 367 1, or more times (eg. constant, idempotent).
|
