Searched refs:rolling (Results 1 – 19 of 19) 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.
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
24 U64 rolling; member37 state->rolling = ~(U32)0; in ZSTD_ldm_gear_init()76 hash = state->rolling; in ZSTD_ldm_gear_feed()104 state->rolling = hash; in ZSTD_ldm_gear_feed()
37 rolling transactions. The grant head is exported in
48 * rolling over into the next byte
58 * rolling over into the next byte
35 * 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
53 than rolling your own. For one thing, the standard primitives interact123 Please use them rather than rolling your own.
271 to the driver and modeset objects. This way rolling back an update boils down
184 other driver specific per-object locks removed. The problem is tha rolling out
58 :Date: rolling version
33 rolling development model which is continually integrating major changes.
392 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
123 (which is available on http://kernel.org). Most users "rolling their