| /openbmc/linux/Documentation/userspace-api/media/drivers/ |
| H A D | imx-uapi.rst | 35 sync by adding 1 dummy line every frame, which causes a rolling effect
41 From experiment it was found that during image rolling, the frame
44 and remain at that value until rolling stops.
54 to correct the rolling/split image.
|
| /openbmc/linux/lib/zstd/compress/ |
| H A D | zstd_ldm.c | 24 U64 rolling; member
37 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()
|
| /openbmc/linux/Documentation/admin-guide/device-mapper/ |
| H A D | era.rst | 16 coherency after rolling back a vendor snapshot.
72 The scenario of invalidating a cache when rolling back a vendor
|
| H A D | persistent-data.rst | 10 different targets were rolling their own data structures, for example:
|
| H A D | cache.rst | 213 situations (e.g., rolling back snapshots of
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-fs-xfs | 37 rolling transactions. The grant head is exported in
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/minifi-cpp/ |
| H A D | minifi-cpp_0.15.0.bb | 156 sed -i "s|#appender.rolling.directory=.*|appender.rolling.directory=${MINIFI_LOG}|g" \
|
| /openbmc/linux/lib/raid6/ |
| H A D | altivec.uc | 48 * rolling over into the next byte
|
| H A D | int.uc | 58 * rolling over into the next byte
|
| H A D | neon.uc | 36 * rolling over into the next byte
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | xfs-delayed-logging-design.rst | 105 This results in a series of "rolling transactions" where the inode is locked
106 across the entire chain of transactions. Hence while this series of rolling
111 It is important to note that a series of rolling transactions in a permanent
158 are maintained as part of the transaction rolling mechanism.
190 transaction rolling mechanism to re-reserve space on every transaction roll. We
253 forwards progress guarantees that rolling permanent transactions require.
296 If all rolling transactions obey this rule, then they can all make forwards
336 A typical example of a rolling transaction is the removal of extents from an
338 of reservation size limitations. Hence a rolling extent removal transaction
820 rolling transactions for an example of this). Hence we *must* always have
|
| H A D | erofs.rst | 70 - Support chunk-based data deduplication and rolling-hash compressed data
|
| /openbmc/linux/tools/memory-model/Documentation/ |
| H A D | simple.txt | 53 than rolling your own. For one thing, the standard primitives interact
123 Please use them rather than rolling your own.
|
| /openbmc/linux/Documentation/process/ |
| H A D | kernel-docs.rst | 57 :Date: rolling version
|
| H A D | 2.Process.rst | 33 rolling development model which is continually integrating major changes.
|
| /openbmc/linux/Documentation/translations/sp_SP/process/ |
| H A D | kernel-docs.rst | 63 :Fecha: rolling version
|
| /openbmc/linux/Documentation/gpu/ |
| H A D | todo.rst | 188 other driver specific per-object locks removed. The problem is that rolling out
543 - Improve late-register debugfs by rolling out the same debugfs pre-register
|
| H A D | drm-kms.rst | 271 to the driver and modeset objects. This way rolling back an update boils down
|
| /openbmc/openbmc/poky/documentation/ref-manual/ |
| H A D | system-requirements.rst | 120 has no plans to support rolling-releases or development
|
| /openbmc/linux/Documentation/mm/ |
| H A D | hmm.rst | 381 rolling back pages not migrating.
|
| /openbmc/docs/designs/ |
| H A D | redfish-authorization.md | 144 rolling out a new BMC firmware.
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | bcache.rst | 35 it also keeps a rolling average of the IO sizes per task, and as long as the
|
| H A D | reporting-issues.rst | 48 can. That includes keeping the ball rolling by occasionally retesting with newer
160 * Wait for reactions and keep the thing rolling until you can accept the
1278 *Wait for reactions and keep the thing rolling until you can accept the
|
| H A D | quickly-build-trimmed-linux.rst | 73 that might occur at a particular point -- and how to then get things rolling
|
| /openbmc/linux/Documentation/networking/ |
| H A D | bonding.rst | 123 (which is available on http://kernel.org). Most users "rolling their
|