Lines Matching refs:there

75 log buffers made available by the log manager. By default there are 8 log
97 but only one of those copies needs to be there - the last one "D", as it
108 logical to physical formatting to do the relogging because there is no
125 words, instead of there only being a maximum of 2MB of transaction changes not
126 written to the log at any point in time, there may be a much greater amount
132 recovered filesystem is concerned, there may be many thousands of transactions
233 region headers in the formatting stage, which is problematic as there is per
296 reason for this limit is that to find the head and tail of the log, there must
298 transaction is larger than half the log, then there is the possibility that a
417 This allows transactions to be issued asynchronously even though there may be
455 aggregation of multiple synchronous transactions if there are already
495 there are lots of transactions that only contain an inode core and an inode log
531 very difficult and complex to arrange. It is possible to do, but there is a
554 a CIL push triggered by a log force, only that there is no waiting for the
576 only becomes unpinned when all the transactions complete and there are no
578 as there is a 1:1 relationship with transaction commit and log item completion.
592 the CIL during a transaction commit, then we do not pin it again. Because there
611 code does not break down even when there are transactions coming from 2048
613 there was only one CPU using it, but it does not slow down either.
616 for concurrency from the ground up. It is obvious that there are serialisation
732 With delayed logging, there are new steps inserted into the life cycle:
790 mount option. Fundamentally, there is no reason why the log manager would not