Lines Matching refs:code

68 In the code, a one-shot transaction pattern looks somewhat like this::
437 	   problems with the new code.
464 Put simply, the current logging code formats the changes to each item into an
465 vector array that points to the changed regions in the item. The log write code
468 using the log buffer as the destination of the formatting code, we can use an
473 the changes in a format that is compatible with the log buffer writing code.
525 self-describing object that can be passed to the log buffer write code to be
582 transaction. Fortunately, the XFS log code has no fixed limit on the size of a
583 transaction, nor does the log replay code. The only fundamental limit is that
602 code to write the changes into the log. To do this efficiently, we need to
604 transaction. The current log write code enables us to do this easily with the
621 workloads, just like the existing transaction commit code does. This, however,
627 into the new CIL, then checkpoint transaction commit code cannot use log items
679 start, while the checkpoint flush code works over the log vector chain to
732 result, the code that forces the log to a specific LSN now needs to ensure that
744 mitigation algorithms similar to the current log buffer code to allow
753 synchronisation in the log force code so that we don't need to wait anywhere
759 simple addition to the existing log forcing code to check the sequence numbers
761 the log force code enables the current mechanism for issuing synchronous
763 force the log at the LSN of that transaction) and so the higher level code
816 available when required, then the regrant code will sleep waiting for it.
838 checkpoint flush code.
847 transaction commit code.
904 code does not break down even when there are transactions coming from 2048
905 processors at once. The current transaction code does not go any faster than if
908 As a result, the delayed logging transaction commit code needs to be designed
947 are inserted into the CIL. Because transactions can enter this code
954 The final serialisation point is the checkpoint commit record ordering code
955 that is run as part of the checkpoint commit and log force sequencing. The code