Searched refs:rolling (Results 1 – 23 of 23) sorted by relevance
35 sync by adding 1 dummy line every frame, which causes a rolling effect41 From experiment it was found that during image rolling, the frame44 and remain at that value until rolling stops.54 to correct the rolling/split image.
24 U64 rolling; member37 state->rolling = ~(U32)0; in ZSTD_ldm_gear_init()68 U64 hash = state->rolling; in ZSTD_ldm_gear_reset()103 hash = state->rolling; in ZSTD_ldm_gear_feed()131 state->rolling = hash; in ZSTD_ldm_gear_feed()
16 coherency after rolling back a vendor snapshot.72 The scenario of invalidating a cache when rolling back a vendor
10 different targets were rolling their own data structures, for example:
213 situations (e.g., rolling back snapshots of
37 rolling transactions. The grant head is exported in
48 * rolling over into the next byte
58 * rolling over into the next byte
36 * rolling over into the next byte
105 This results in a series of "rolling transactions" where the inode is locked106 across the entire chain of transactions. Hence while this series of rolling111 It is important to note that a series of rolling transactions in a permanent158 are maintained as part of the transaction rolling mechanism.190 transaction rolling mechanism to re-reserve space on every transaction roll. We253 forwards progress guarantees that rolling permanent transactions require.296 If all rolling transactions obey this rule, then they can all make forwards336 A typical example of a rolling transaction is the removal of extents from an338 of reservation size limitations. Hence a rolling extent removal transaction820 rolling transactions for an example of this). Hence we *must* always have
70 - Support chunk-based data deduplication and rolling-hash compressed data
2566 The transaction rolling in steps 2c and 3 represent a weakness in the repair
53 than rolling your own. For one thing, the standard primitives interact123 Please use them rather than rolling your own.
63 :Fecha: rolling version
57 :Date: rolling version
33 rolling development model which is continually integrating major changes.
188 other driver specific per-object locks removed. The problem is that rolling out544 - Improve late-register debugfs by rolling out the same debugfs pre-register
271 to the driver and modeset objects. This way rolling back an update boils down
381 rolling back pages not migrating.
35 it also keeps a rolling average of the IO sizes per task, and as long as the
48 can. That includes keeping the ball rolling by occasionally retesting with newer160 * Wait for reactions and keep the thing rolling until you can accept the1278 *Wait for reactions and keep the thing rolling until you can accept the
73 that might occur at a particular point -- and how to then get things rolling
123 (which is available on http://kernel.org). Most users "rolling their
