Home
last modified time | relevance | path

Searched full:sequential (Results 1 – 25 of 100) sorted by relevance

1234

/openbmc/qemu/tests/qemu-iotests/
H A D04694 # Sequential write case: Alloc middle of cluster 2, then write overlapping
115 # Sequential write, but the next cluster is already allocated
127 # Sequential write, but the next cluster is already allocated
143 # Sequential write, and the next cluster is compressed
158 # Reverse sequential write
168 # Reverse sequential write with a gap
H A D25048 # To reproduce bug we need to overflow int by one sequential discard, so we
50 # of 512M sequential data, corresponding to one L1 entry), and we need some
H A D07761 # Sequential RMW requests on the same physical sector
204 # Sequential RMW requests on the same physical sector
/openbmc/u-boot/fs/yaffs2/
H A DKconfig7 writes are sequential regardless of filesystem activity.
/openbmc/qemu/docs/devel/
H A Dzoned-storage.rst6 that are larger than the LBA size. They can only allow sequential writes, which
15 - BLK_Z_HM: The host-managed zoned model only allows sequential writes access
/openbmc/qemu/scripts/simplebench/
H A Dbench_prealloc.py118 'id': f'{name}, aligned sequential 16k',
123 'id': f'{name}, unaligned sequential 64k',
/openbmc/qemu/tests/tcg/aarch64/
H A Dmte-7.c21 /* Store tag in sequential granules. */ in main()
H A Dmte-5.c37 /* Store store two different tags in sequential granules. */ in main()
/openbmc/qemu/linux-user/
H A Dsocket.h14 * @SOCK_SEQPACKET - sequential packet socket
/openbmc/openbmc/meta-openembedded/meta-filesystems/recipes-filesystems/sshfs-fuse/sshfs-fuse/
H A Da1d58ae1be99571a88b8439b027abe6349b74658.patch24 # relies on tests running sequential (i.e., don't dare to use e.g. the xdist
/openbmc/phosphor-power/phosphor-regulators/src/actions/
H A Daction_utils.hpp33 * Executes one or more actions in sequential order.
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-benchmark/tinymembench/
H A Dtinymembench_git.bb2 peak bandwidth of sequential memory accesses and the latency of random memory \
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-benchmark/tiobench/tiobench-0.3.3/
H A D0001-Specify-printf-formats.patch38 @@ -552,7 +552,7 @@ void do_test( ThreadTest *test, int testCase, int sequential,
/openbmc/qemu/include/exec/
H A Dcpu-interrupt.h12 * The numbers assigned here are non-sequential in order to preserve binary
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/xmlrpc-c/
H A Dxmlrpc-c_1.64.0.bb11 file://0001-unix-common.mk-Ensuring-Sequential-Execution-of-rm-a.patch \
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Network/Experimental/
H A DBond.interface.yaml36 sequential order from the first available target through the
/openbmc/qemu/docs/devel/migration/
H A Dmapped-ram.rst16 sequential stream. Having the pages at fixed offsets also allows the
81 Instead of having a sequential stream of pages that follow the
/openbmc/u-boot/common/
H A Dmemsize.c13 * At least on G2 PowerPC cores, sequential accesses to non-existent
/openbmc/qemu/include/standard-headers/linux/
H A Dvirtio_blk.h266 /* Sequential Write Required zone */
268 /* Sequential Write Preferred zone */
/openbmc/qemu/linux-user/mips/
H A Dsockbits.h84 * @SOCK_SEQPACKET - sequential packet socket
/openbmc/qemu/include/io/
H A Dchannel-file.h98 * type of file on which sequential I/O can be
/openbmc/u-boot/arch/x86/include/asm/fsp/
H A Dfsp_fv.h66 /* The number of sequential blocks which are of the same size */
/openbmc/qemu/linux-headers/asm-generic/
H A Dmman-common.h47 #define MADV_SEQUENTIAL 2 /* expect sequential page references */
/openbmc/qemu/include/qemu/
H A Dcoroutine-core.h21 * useful flavor of coroutines that is suitable for writing sequential code,
/openbmc/sdbusplus/tools/sdbusplus/
H A Dnamedelement.py202 # Anything left has at least two sequential upper-case, so it is an

1234