| /spdk/doc/ |
| H A D | ftl.md | 28 a band follow the same pattern - a batch of logical blocks is written to one zone, another batch 63 Bands are written sequentially (in a way that was described earlier). Before a band can be written 65 state. Then the band moves to the `OPEN` state and actual user data can be written to the 66 band. Once the whole available space is filled, tail metadata is written and the band transitions to 74 Nvcache data space is divided into chunks. Chunks are written in sequential manner. 75 When number of free chunks is below assigned threshold data from fully written chunks 101 written block for a ZNS drive, this data will stay there until the whole zone is reset. This might …
|
| H A D | compression.md | 37 Storage from the backing storage device will be allocated, read, and written to in 4KB units for 113 * Entry 2 in the logical map is "X". This means no part of this 16KB has been written to yet. 147 * Entry 0 in the logical map is "X". This means no part of this 16KB has been written to yet. 181 * Entry 1 in the logical map is "X". This means no part of this 16KB has been written to yet. 182 * Since no data has been written to this chunk, return all 0's to satisfy the read I/O. 192 be written later back to disk. 270 after a chunk map is updated, but before it is written to the logical map - that everything
|
| H A D | ssd_internals.md | 21 each bit may be written to (i.e. have its bit flipped from 0 to 1) with 32 Flash is selected and written and the mapping of the logical block to its 61 As SSDs are written to, the internal log will eventually consume all of the
|
| H A D | about.md | 17 written as a C library with a single public header. See @ref nvme for more
|
| H A D | usdt.md | 19 probe description. SPDK bpftrace scripts can be written with an __EXE__ 25 written with a __PID__ marker, and bpftrace.sh will dynamically replace
|
| H A D | shfmt.md | 12 The majority of tests (and scripts overall) in the SPDK repo are written
|
| H A D | event.md | 19 Simple server applications can be written in a single-threaded fashion. This
|
| H A D | template_pg.md | 48 … want to highlight things they need to think about in *their* design. If you have written test code
|
| H A D | blob.md | 54 …Blobs are read and written in units of pages by specifying an offset from the start of the blob. A… 290 form a linked list. The first page in the list will be written in place on update, while all other … 291 be written to fresh locations. This requires the backing device to support an atomic write size gre… 444 allocated to the blob will be written on the device. This device must have a size equal or greater 509 …able metadata for the blob; one copy is the current metadata and the other is the last copy written
|
| H A D | nvme_spec.md | 34 associated with the command. This host memory is the data to be written on a
|
| H A D | accel_fw.md | 44 functions exposed by the individual low level libraries. Thus, code written this
|
| H A D | nvmf_tgt_pg.md | 18 This guide is written assuming that the reader is familiar with both NVMe and
|
| /spdk/scripts/env_dpdk/22.11/ |
| H A D | 23.07-rte_bus_pci.h.patch | 40 - * A data buffer containing the bytes should be written. 46 - * Number of bytes written on success, negative on error.
|
| H A D | 23.11-rte_bus_pci.h.patch | 137 - * A data buffer containing the bytes should be written. 143 - * Number of bytes written on success, negative on error.
|
| /spdk/test/unit/lib/scsi/scsi_bdev.c/ |
| H A D | scsi_bdev_ut.c | 626 int written, i; in scsi_name_padding_test() local 631 written = bdev_scsi_pad_scsi_name(buf, name); in scsi_name_padding_test() 633 CU_ASSERT(written == 252); in scsi_name_padding_test() 640 written = bdev_scsi_pad_scsi_name(buf, name); in scsi_name_padding_test() 642 CU_ASSERT(written == 256); in scsi_name_padding_test() 651 written = bdev_scsi_pad_scsi_name(buf, name); in scsi_name_padding_test() 653 CU_ASSERT(written == 256); in scsi_name_padding_test()
|
| /spdk/lib/nvmf/ |
| H A D | nvmf_fc.h | 808 int32_t written; in nvmf_fc_dump_buf_print() 811 written = vsnprintf(dump_info->buffer + dump_info->offset, avail, fmt, ap); in nvmf_fc_dump_buf_print() 812 if (written >= avail) { in nvmf_fc_dump_buf_print() 815 dump_info->offset += written; in nvmf_fc_dump_buf_print() 806 int32_t written; nvmf_fc_dump_buf_print() local
|
| /spdk/licenses/ |
| H A D | bsd-3-clause.txt | 7 …o endorse or promote products derived from this software without specific prior written permission.
|
| /spdk/go/rpc/ |
| H A D | LICENSE | 15 this software without specific prior written permission.
|
| H A D | README.md | 6 This directory contains JSON-RPC client written in Go. The main goal is to ease communication with
|
| /spdk/scripts/ |
| H A D | spdx.sh | 21 * from this software without specific prior written permission.
|
| /spdk/ |
| H A D | CODE_OF_CONDUCT.md | 78 **Consequence**: A private, written warning from SPDK core maintainers, providing
|