Searched refs:idempotent (Results 1 – 4 of 4) sorted by relevance
692 Fast commits tags are idempotent in nature provided the recovery code follows709 Let's take an example of a procedure that is not idempotent and see how fast710 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, instead736 replay of last inode 11 tag. Thus, by converting a non-idempotent procedure737 into a series of idempotent outcomes, fast commits ensured idempotence during
3657 struct idempotent { struct3668 static bool idempotent(struct idempotent *u, const void *cookie) in idempotent() function3672 struct idempotent *existing; in idempotent()3699 static int idempotent_complete(struct idempotent *u, int ret) in idempotent_complete()3705 struct idempotent *pos; in idempotent_complete()3730 static int idempotent_wait_for_completion(struct idempotent *u) in idempotent_wait_for_completion()3782 struct idempotent idem; in idempotent_init_module()3788 if (!idempotent(&idem, file_inode(f))) { in idempotent_init_module()
12 example. Software often retries idempotent operations after transient
144 lockless and should be idempotent.