Lines Matching refs:logging

19 the basic concepts covered, the design of the delayed logging mechanism is
28 logging mechanisms are varied and complex, combining intents, logical and
29 physical logging mechanisms to provide the necessary recovery guarantees the
42 logging overhead as low as possible. Some items are very frequently modified,
44 the overhead of metadata logging low is of prime importance.
48 the method used for logging a particular object or chaining modifications
50 performed. The logging subsystem only cares that certain specific rules are
134 However, the logging subsystem does provide global ordering guarantees, such
144 Synchronous transactions are rarely used, however, because they limit logging
153 It has been mentioned a number of times now that the logging subsystem needs to
287 "Re-logging" the locked items on every transaction roll ensures that the items
292 move the tail of the log forwards to free up write grant space. Re-logging the
303 Re-logging Explained
309 method called "re-logging". Conceptually, this is quite simple - all it requires
376 The key thing to note about the asynchronous logging combined with the
390 is the fundamental goal of delayed logging.
399 Delayed logging is the name we've given to keeping and tracking transactional
408 One of the key changes that delayed logging makes to the operation of the
414 crash is much greater than for the existing logging mechanism.
423 It should be noted that delayed logging is not an innovative new concept that
431 The fundamental requirements for delayed logging in XFS are simple:
457 the delayed logging tracking lock to commit the transaction. However, the
458 flushing thread has the delayed logging tracking lock already held, and is
461 was the barrier to implementing delayed logging for so long.
464 Put simply, the current logging code formats the changes to each item into an
481 formatting method and the delayed logging formatting can be seen in the
495 Delayed logging vector::
716 mechanism, it does not work for delayed logging because transactions are not
720 As discussed in the checkpoint section, delayed logging uses per-checkpoint
764 behaves the same regardless of whether delayed logging is being used or not.
784 An example of the differences would be logging directory changes versus logging
790 comparison, if we are logging full directory buffers, they are typically 4KB
853 manner that is done for the existing logging method. A discussion point is
872 For delayed logging, however, we have an asymmetric transaction commit to
908 As a result, the delayed logging transaction commit code needs to be designed
1026 With delayed logging, there are new steps inserted into the life cycle::
1075 logging methods are in the middle of the life cycle - they still have the same
1078 Hence delayed logging should not introduce any constraints on log item
1081 As a result of this zero-impact "insertion" of delayed logging infrastructure
1083 can basically switch between delayed logging and the existing mechanism with a
1086 characteristics, but this should not be necessary if delayed logging works as