Searched full:large (Results 1 – 25 of 365) sorted by relevance
12345678910>>...15
| /Documentation/driver-api/mmc/ |
| D | mmc-dev-attrs.rst | 54 SD/MMC cards can erase an arbitrarily large area up to and
55 including the whole card. When erasing a large area it may
65 3. The erase timeout becomes too large to be very
68 the value can end up being several minutes for large
74 size for erasing large areas.
|
| /Documentation/filesystems/ext4/ |
| D | eainode.rst | 3 Large Extended Attribute Values
13 sharing of large xattr values between multiple owning inodes. For
|
| /Documentation/infiniband/ |
| D | ipoib.rst | 48 which reduces the number of IP packets needed for handling large UDP
49 datagrams, TCP segments, etc and increases the performance for large
61 TCP/IP checksum and/or Large Send (LSO) offloading capability to the
64 Large Receive (LRO) offloading is also implemented and may be turned
|
| /Documentation/spi/ |
| D | spi-sc18is602.rst | 34 similar large accesses have to be split into multiple chunks of no more than
36 means that programs such as "cp" or "od", which automatically use large block
|
| /Documentation/trace/ |
| D | events-kmem.rst | 95 consecutively imply the zone->lock being taken once. Large amounts of per-CPU
98 lists should be a larger size. Finally, large amounts of refills on one CPU
99 and drains on another could be a factor in causing large amounts of cache
115 Large numbers of this event implies that memory is fragmenting and
|
| /Documentation/userspace-api/media/v4l/ |
| D | metafmt-uvc.rst | 22 Each UVC payload header can be between 2 and 12 bytes large. Buffers can
27 perform rate limiting when the device sends a large number of headers.
|
| /Documentation/arch/x86/ |
| D | xstate.rst | 11 trapped by the kernel because by default the required large XSTATE buffers
65 are large enough to accommodate the resulting large signal frame. It
79 the handler allocates a larger xstate buffer for the task so the large
|
| /Documentation/admin-guide/ |
| D | efi-stub.rst | 66 initrd-large.img
72 to boot with the initrd-large.img file if the current working
75 fs0:\Kernels> bzImage.efi initrd=\Kernels\initrd-large.img
|
| D | ext4.rst | 8 scalability and reliability enhancements for supporting large filesystems
66 the filesystem with a large journal can also be helpful for
88 * large file support
89 * inode allocation using large virtual block groups via flex_bg
91 * large block (up to pagesize) support
123 used on large case-insensitive directories with DX feature. On DX
193 to very large values will improve performance. Note that due to
375 This is useful in memory constrained environments, where a very large
502 pool, so that small files are packed closely together. Each large file
|
| /Documentation/virt/kvm/x86/ |
| D | mmu.rst | 24 need to scale to large memory and large vcpu guests
156 Examples include real mode translation, large guest pages backed by small
442 Large pages
445 The mmu supports all combinations of large and small guest and host pages.
450 To instantiate a large spte, four constraints must be satisfied:
452 - the spte must point to a large host page
453 - the guest pte must be a large pte of at least equivalent size (if tdp is
455 - if the spte will be writeable, the large page frame may not overlap any
460 arrays for each memory slot and large page size. Every write protected page
462 a large spte. The frames at the end of an unaligned memory slot have
|
| /Documentation/core-api/ |
| D | pin_user_pages.rst | 31 This is in order to avoid creating a large number of wrapper functions to cover
58 For large folios, the GUP_PIN_COUNTING_BIAS scheme is not used. Instead,
62 This approach for large folios avoids the counting upper limit problems
68 This also means that huge pages and large folios do not suffer
107 large value (GUP_PIN_COUNTING_BIAS, initially chosen to be 1024: 10 bits) to
275 fields, and to better report on large folios in general. Specifically,
276 for large folios, the exact pincount is reported.
|
| /Documentation/arch/x86/x86_64/ |
| D | 5level-paging.rst | 34 User-space and large virtual address space
61 about large address space without manually tracking allocated virtual
|
| /Documentation/driver-api/ |
| D | io-mapping.rst | 10 usage is to support the large graphics aperture on 32-bit processors where
20 mappable, while 'size' indicates how large a mapping region to
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-iio-light-si1133 | 14 dark photodiodes. "large" indicate the surface area capturing
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-io.rst | 50 I/O to a large region but doesn't want to allocate a large number of individual
|
| /Documentation/process/ |
| D | cve.rst | 41 explains the seemingly large number of CVEs that are issued by the Linux
105 Also, as the source tree is so large, and any one system only uses a
107 large numbers of assigned CVEs are not relevant for their systems.
|
| /Documentation/admin-guide/hw-vuln/ |
| D | multihit.rst | 42 the illusion of a very large memory for processors. This virtual space is split
52 paging structure so that the same linear address using large page size (2 MB, 4
107 This erratum can be mitigated by restricting the use of large page sizes to
119 (non-nested) page tables. For simplicity, KVM will make large pages
|
| /Documentation/filesystems/ |
| D | ceph.rst | 30 across storage nodes in large chunks to distribute workload and
36 Metadata servers effectively form a large, consistent, distributed
45 extremely large directories can be fragmented and managed by
77 This makes the identification of large disk space consumers relatively quick,
|
| D | hpfs.rst | 161 (one directory, if it's large, has dirents in tree on HPFS) must be replaced
278 Fixed some incompatibilities with large extended attributes (but it's still
288 Fixed a bug that it set badly one flag in large anode tree (it was not
298 Fixed possible problem on large disks
303 1.97 Support for HPFS v3 (on large partitions)
349 2.08 Creating new files is not so slow on large disks
|
| /Documentation/arch/arm64/ |
| D | memory.rst | 17 ARMv8.2 adds optional support for Large Virtual Address space. This is
124 spaces, the VMEMMAP must be sized large enough for 52-bit VAs and
125 also must be sized large enough to accommodate a fixed PAGE_OFFSET.
139 sized large enough or that addresses are positioned close enough for
|
| /Documentation/admin-guide/mm/ |
| D | concepts.rst | 72 large memory working set will experience performance hit because of
199 necessary to allocate large physically contiguous memory areas. Such
200 need may arise, for instance, when a device driver requires a large
205 together at the beginning of the zone and allocations of large
|
| /Documentation/mm/ |
| D | page_tables.rst | 50 would be very sparse, because large portions of the virtual memory usually
51 remains unused. By using hierarchical page tables large holes in the virtual
53 to mark large areas as unmapped at a higher level in the page table hierarchy.
59 traverse deeper in the hierarchy when you find a large mapped range like this.
257 pages contain large contiguous physical regions that usually span from 2MB to
|
| /Documentation/timers/ |
| D | timers-howto.rst | 34 possible overflow when passing large arguments to udelay.
88 usleep function would likely introduce a large number
|
| /Documentation/scsi/ |
| D | ChangeLog.ips | 43 4.70.15 - Fix Breakup for very large ( non-SG ) requests
51 4.70.09 - Use a Common ( Large Buffer ) for Flashing from the JCRM CD
|
| /Documentation/driver-api/firmware/ |
| D | built-in-fw.rst | 28 * Some firmware files may be really large in size. The remote-proc subsystem
|
12345678910>>...15