Searched +full:erase +full:- +full:size (Results 1 – 25 of 26) sorted by relevance
12
| /Documentation/driver-api/mmc/ |
| D | mmc-dev-attrs.rst | 11 force_ro Enforce read-only access even if write protect switch is off.
17 All attributes are read-only.
34 erase_size Erase group size
35 preferred_erase_size Preferred erase size
36 raw_rpmb_size_mult RPMB partition size
45 Note on Erase Size and Preferred Erase Size:
47 "erase_size" is the minimum size, in bytes, of an erase
48 operation. For MMC, "erase_size" is the erase group size
50 to trim or secure trim operations where the minimum size is
52 if the card is block-addressed, 0 otherwise.
[all …]
|
| /Documentation/driver-api/mtd/ |
| D | spi-nor.rst | 6 -----------------------------------
11 standard set of internal read-only parameter tables.
17 on its SFDP data. All one has to do is to specify the "jedec,spi-nor"
28 -----------------------------
31 section, after the ``---`` marker.
41 root@1:~# cat /sys/bus/spi/devices/spi0.0/spi-nor/partname
43 root@1:~# cat /sys/bus/spi/devices/spi0.0/spi-nor/jedec_id
45 root@1:~# cat /sys/bus/spi/devices/spi0.0/spi-nor/manufacturer
47 root@1:~# xxd -p /sys/bus/spi/devices/spi0.0/spi-nor/sfdp
69 root@1:~# sha256sum /sys/bus/spi/devices/spi0.0/spi-nor/sfdp
[all …]
|
| D | spi-intel.rst | 2 Upgrading BIOS using spi-intel
14 The spi-intel driver makes it possible to read and write the SPI serial
16 any of them set, the whole MTD device is made read-only to prevent
18 contents as read-only but it can be changed from kernel command line,
31 2) Install mtd-utils package [2]. We need this in order to erase the SPI
33 name "mtd-utils".
43 dev: size erasesize name
63 7) Erase the SPI serial flash. After this step, do not reboot the
67 Erasing 4 Kibyte @ 7ff000 -- 100 % complete
86 ----------
[all …]
|
| /Documentation/driver-api/nvdimm/ |
| D | security.rst | 6 ---------------
11 "unlock unit", "freeze lock", "secure erase", and "overwrite". A security_ops
16 ------------------
28 update <old_keyid> <new_keyid> - enable or update passphrase.
29 disable <keyid> - disable enabled security and remove key.
30 freeze - freeze changing of security states.
31 erase <keyid> - delete existing user encryption key.
32 overwrite <keyid> - wipe the entire nvdimm.
33 master_update <keyid> <new_keyid> - enable or update master passphrase.
34 master_erase <keyid> - delete existing user encryption key.
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-mtd | 4 Contact: linux-mtd@lists.infradead.org
12 Contact: linux-mtd@lists.infradead.org
22 Contact: linux-mtd@lists.infradead.org
24 These directories provide the corresponding read-only device
30 Contact: linux-mtd@lists.infradead.org
34 read-write device so <minor> will be even.
39 Contact: linux-mtd@lists.infradead.org
42 to the read-only variant of the MTD device (in
48 Contact: linux-mtd@lists.infradead.org
50 "Major" erase size for the device. If numeraseregions is
[all …]
|
| D | sysfs-c2port | 13 The /sys/class/c2port/c2portX/ directory is related to X-th
37 access to the on-board flash of the connected micro.
45 the on-board flash block size of the connected micro.
52 the on-board flash blocks number of the connected micro.
59 the content of the on-board flash of the connected micro.
66 the "erase" command on the on-board flash of the connected
|
| D | sysfs-bus-cxl | 4 Contact: linux-cxl@vger.kernel.org
14 Contact: linux-cxl@vger.kernel.org
17 Memory Device Output Payload in the CXL-2.0
21 What: /sys/bus/cxl/devices/memX/ram/size
24 Contact: linux-cxl@vger.kernel.org
28 Payload in the CXL-2.0 specification.
34 Contact: linux-cxl@vger.kernel.org
40 class-ids can be compared against a similar "qos_class"
42 that the endpoints map their local memory-class to a
45 side-effects that may result. First class-id is displayed.
[all …]
|
| D | sysfs-driver-ufs | 3 Contact: linux-scsi@vger.kernel.org
5 This file contains the auto-hibernate idle timer setting of a
6 UFS host controller. A value of '0' means auto-hibernate is not
11 10-bit values with a power-of-ten multiplier which allows a
273 written during the pre-soldering phase of the PSA flow.
307 Description: This file shows the MIPI M-PHY version number in BCD format.
342 Description: This file shows the segment size. This is one of the UFS
352 Description: This file shows the allocation unit size. This is one of
362 Description: This file shows the minimum addressable block size. This
373 Description: This file shows the optimal read block size. This is one
[all …]
|
| /Documentation/core-api/ |
| D | maple_tree.rst | 1 .. SPDX-License-Identifier: GPL-2.0+
13 The Maple Tree is a B-Tree data type which is optimized for storing
14 non-overlapping ranges, including ranges of size 1. The tree was designed to
17 entry in a cache-efficient manner. The tree can also be put into an RCU-safe
24 use the normal API. An :ref:`maple-tree-advanced-api` exists for more complex
34 :ref:`maple-tree-advanced-api`, but are blocked by the normal API.
37 size (or larger).
39 Pre-allocating of nodes is also supported using the
40 :ref:`maple-tree-advanced-api`. This is useful for users who must guarantee a
45 .. _maple-tree-normal-api:
[all …]
|
| D | circular-buffers.rst | 12 (1) Convenience functions for determining information about power-of-2 sized
27 (*) Measuring power-of-2 buffers.
30 - The producer.
31 - The consumer.
39 fixed, finite size into which there are two indices:
41 (1) A 'head' index - the point at which the producer inserts items into the
44 (2) A 'tail' index - the point at which the consumer finds the next item in
56 Typically, items will all be of the same unit size, but this isn't strictly
58 than 1 if multiple items or variable-sized items are to be included in the
60 be careful, however, as a region more than one unit in size may wrap the end of
[all …]
|
| D | rbtree.rst | 2 Red-black Trees (rbtree) in Linux
9 What are red-black trees, and what are they for?
10 ------------------------------------------------
12 Red-black trees are a type of self-balancing binary search tree, used for
16 be easily traversed in order, and must be tuned for a specific size and
19 Red-black trees are similar to AVL trees, but provide faster real-time bounded
26 There are a number of red-black trees in use in the kernel.
29 The high-resolution timer code uses an rbtree to organize outstanding
31 red-black tree. Virtual memory areas (VMAs) are tracked with red-black
38 Linux Weekly News article on red-black trees
[all …]
|
| /Documentation/filesystems/ |
| D | ubifs.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 UBIFS file-system stands for UBI File System. UBI stands for "Unsorted
13 is completely different to any traditional file-system in Linux, like
14 Ext2, XFS, JFS, etc. UBIFS represents a separate class of file-systems
16 file-system of this class is JFFS2.
22 rather large size, typically about 128KiB. Block devices consist of
24 2 MTD devices support 3 main operations - read from some offset within an
25 eraseblock, write to some offset within an eraseblock, and erase a whole
26 eraseblock. Block devices support 2 main operations - read a whole
29 re-write its contents. Blocks may be just re-written.
[all …]
|
| D | ubifs-authentication.rst | 1 .. SPDX-License-Identifier: GPL-2.0
24 binary to perform a malicious action when executed [DMC-CBC-ATTACK]. Since
28 Other full disk encryption systems like dm-crypt cover all filesystem metadata,
31 time. For dm-crypt and other filesystems that build upon the Linux block IO
32 layer, the dm-integrity or dm-verity subsystems [DM-INTEGRITY, DM-VERITY]
34 These can also be combined with dm-crypt [CRYPTSETUP2].
44 ----------------
50 addition, it deals with flash-specific wear-leveling and transparent I/O error
51 handling. UBI offers logical erase blocks (LEBs) to the layers on top of it
52 and maps them transparently to physical erase blocks (PEBs) on the flash.
[all …]
|
| /Documentation/devicetree/bindings/mtd/ |
| D | mtd-physmap.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/mtd/mtd-physmap.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: CFI or JEDEC memory-mapped NOR flash, MTD-RAM (NVRAM...)
10 - Rob Herring <robh@kernel.org>
17 - $ref: mtd.yaml#
18 - $ref: /schemas/memory-controllers/mc-peripheral-props.yaml#
23 - items:
24 - enum:
[all …]
|
| /Documentation/scsi/ |
| D | st.rst | 1 .. SPDX-License-Identifier: GPL-2.0
23 flexible method and applicable to single-user workstations. However,
28 parameters, like block size and density using the MTSETDRVBUFFER ioctl.
32 drive performs auto-detection of the tape format well (like some
33 QIC-drives). The result is that any tape can be read, writing can be
37 does not perform auto-detection well enough and there is a single
40 or not :-).
57 between formats in multi-tape operations (the explicitly overridden
71 The driver supports fixed and variable block size (within buffer
72 limits). Both the auto-rewind (minor equals device number) and
[all …]
|
| /Documentation/filesystems/ext4/ |
| D | allocators.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 ---------------------------------
11 but locality can increase the size of each transfer request while
13 effect of concentrating writes on a single erase block, which can speed
17 The first tool that ext4 uses to combat fragmentation is the multi-block
23 files) then the file data gets written out in a single multi-block
44 groups; these mini-containers are used as outlined above to try to
45 maintain data locality. However, there is a deliberate quirk -- when a
49 over a disk; as the top-level directory/file blobs fill up one block
53 the end of a spinning drive get a raw deal performance-wise.
|
| /Documentation/arch/arm/sa1100/ |
| D | assabet.rst | 2 The Intel Assabet (SA-1110 evaluation) board
13 -------------------
25 -----------------------
39 John Dorsey has produced add-on patches to add support for Assabet and
55 - ftp://ftp.netwinder.org/users/n/nico/
56 - ftp://ftp.arm.linux.org.uk/pub/linux/arm/people/nico/
57 - ftp://ftp.handhelds.org/pub/linux/arm/sa-1100-patches/
59 Look for redboot-assabet*.tgz. Some installation infos are provided in
60 redboot-assabet*.txt.
64 -----------------------------
[all …]
|
| /Documentation/ABI/stable/ |
| D | sysfs-class-ubi | 6 The ubi/ class sub-directory belongs to the UBI subsystem and
7 provides general UBI information, per-UBI device information
8 and per-UBI volume information.
15 This file contains version of the latest supported UBI on-media
17 However, if in the future UBI needs on-flash format changes
20 future backward-compatible (but forward-incompatible)
70 Maximum logical eraseblock size this UBI device may provide. UBI
71 volumes may have smaller logical eraseblock size because of their
79 Maximum physical eraseblock erase counter value.
93 Minimum input/output unit size. All the I/O may only be done
[all …]
|
| /Documentation/sound/designs/ |
| D | oss-emulation.rst | 2 Notes on Kernel OSS-Emulation
13 as add-on kernel modules, snd-pcm-oss, snd-mixer-oss and snd-seq-oss.
18 is called. The alias is defined ``sound-service-x-y``, where x and y are
22 Only necessary step for auto-loading of OSS modules is to define the
25 alias sound-slot-0 snd-emu10k1
27 As the second card, define ``sound-slot-1`` as well.
29 ``alias sound-slot-0 snd-card-0`` doesn't work any more like the old
38 after the corresponding OSS-emulation module is loaded. Don't worry
79 snd-pcm-oss and snd-rawmidi. In the case of PCM, the following
80 options are available for snd-pcm-oss:
[all …]
|
| /Documentation/admin-guide/ |
| D | bcache.rst | 11 This is the git repository of bcache-tools:
12 https://git.kernel.org/pub/scm/linux/kernel/git/colyli/bcache-tools.git/
17 It's designed around the performance characteristics of SSDs - it only allocates
18 in erase block sized buckets, and it uses a hybrid btree/log to track cached
19 extents (which can be anywhere from a single sector to the bucket size). It's
20 designed to avoid random writes at all costs; it fills up an erase block
25 great lengths to protect your data - it reliably handles unclean shutdown. (It
29 Writeback caching can use most of the cache for buffering writes - writing
36 average is above the cutoff it will skip all IO from that task - instead of
47 You'll need bcache util from the bcache-tools repository. Both the cache device
[all …]
|
| /Documentation/dev-tools/ |
| D | kmemleak.rst | 9 Valgrind tool (``memcheck --leak-check``) to detect the memory leaks in
10 user-space applications.
13 -----
20 # mount -t debugfs nodev /sys/kernel/debug/
41 Memory scanning parameters can be modified at run-time by writing to the
44 - off
46 - stack=on
48 - stack=off
50 - scan=on
52 - scan=off
[all …]
|
| /Documentation/admin-guide/mm/ |
| D | nommu-mmap.rst | 2 No-MMU memory mapping support
5 The kernel has limited support for memory mapping under no-MMU conditions, such
16 The behaviour is similar between the MMU and no-MMU cases, but not identical;
21 In the MMU case: VM regions backed by arbitrary pages; copy-on-write
24 In the no-MMU case: VM regions backed by arbitrary contiguous runs of
31 the no-MMU case doesn't support these, behaviour is identical to
39 In the no-MMU case:
41 - If one exists, the kernel will re-use an existing mapping to the
45 - If possible, the file mapping will be directly on the backing device
50 - If the backing device can't or won't permit direct sharing,
[all …]
|
| /Documentation/filesystems/caching/ |
| D | cachefiles.rst | 1 .. SPDX-License-Identifier: GPL-2.0
31 (*) On-demand Read.
40 CacheFiles uses a userspace daemon to do some of the cache management - such as
49 CacheFiles creates a misc character device - "/dev/cachefiles" - that is used
58 space if necessary - see the "Cache Culling" section. This means it can be
71 - dnotify.
73 - extended attributes (xattrs).
75 - openat() and friends.
77 - bmap() support on files in the filesystem (FIBMAP ioctl).
79 - The use of bmap() to detect a partial page at the end of the file.
[all …]
|
| /Documentation/networking/device_drivers/ethernet/intel/ |
| D | e1000e.rst | 1 .. SPDX-License-Identifier: GPL-2.0+
8 Copyright(c) 2008-2018 Intel Corporation.
13 - Identifying Your Adapter
14 - Command Line Parameters
15 - Additional Configurations
16 - Support
48 ---------------------
49 :Valid Range: 0,1,3,4,100-100000
77 "Bulk traffic", for large amounts of packets of normal size; "Low latency",
82 - 0: Off
[all …]
|
| /Documentation/sound/ |
| D | alsa-configuration.rst | 2 Advanced Linux Sound Architecture - Driver Configuration guide
38 ----------
47 limiting card index for auto-loading (1-8);
49 For auto-loading more than one card, specify this option
50 together with snd-card-X aliases.
63 Module snd-pcm-oss
64 ------------------
86 regarding opening the device. When this option is non-zero,
90 Module snd-rawmidi
91 ------------------
[all …]
|
12