Searched refs:ahead (Results 1 – 25 of 55) sorted by relevance
123
| /Linux-v5.4/fs/hpfs/ |
| D | buffer.c | 72 int ahead) in hpfs_map_sector() argument
78 hpfs_prefetch_sectors(s, secno, ahead); in hpfs_map_sector()
115 int ahead) in hpfs_map_4sectors() argument
128 hpfs_prefetch_sectors(s, secno, 4 + ahead); in hpfs_map_4sectors()
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | fuse-io.txt | 12 No read-ahead takes place. Shared mmap is disabled.
15 read-ahead by the kernel to fill the cache. The cache is always kept consistent
|
| D | journalling.rst | 35 Now you can go ahead and start modifying the underlying filesystem.
|
| /Linux-v5.4/arch/sh/lib64/ |
| D | copy_page.S | 75 alloco r2, 0x40 ! alloc destination line 2 lines ahead
|
| /Linux-v5.4/drivers/staging/sm750fb/ |
| D | readme | 27 ahead of parameters,so,it looks like:
|
| /Linux-v5.4/Documentation/power/ |
| D | apm-acpi.rst | 30 Go ahead and start both. If ACPI or APM is not available on your
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-class-bdi | 31 Size of the read-ahead window in kilobytes
|
| D | sysfs-class-rtc | 90 future, or if there is a leading +=, seconds ahead of the
|
| /Linux-v5.4/fs/verity/ |
| D | Kconfig | 28 protection against malicious disks vs. an ahead-of-time hash.
|
| /Linux-v5.4/drivers/block/drbd/ |
| D | Kconfig | 60 64 read ahead
|
| /Linux-v5.4/Documentation/networking/ |
| D | driver.txt | 7 there is no way your device can tell ahead of time when it's
|
| D | xfrm_sync.txt | 29 machine is known ahead of time since the decay of the time countdown
|
| /Linux-v5.4/Documentation/devicetree/bindings/ |
| D | submitting-patches.txt | 59 maintainers after a few weeks, go ahead and take it.
|
| /Linux-v5.4/arch/x86/math-emu/ |
| D | README | 194 The performance under Linux is improved by the use of look-ahead code.
196 Linux due to the look-ahead code. Also given are the times for the
199 [ Linus' note: I changed look-ahead to be the default under linux, as
204 look-ahead 'soft' lib
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | security-bugs.rst | 80 assigned ahead of public disclosure, they will need to contact the private
|
| /Linux-v5.4/arch/m68k/fpsp040/ |
| D | x_store.S | 148 beqs dbl_inf |if positive, go ahead and write it
|
| /Linux-v5.4/Documentation/sound/designs/ |
| D | oss-emulation.rst | 160 do not fill silence ahead to avoid clicks
199 filled. The latter stops writing the silence data ahead
|
| /Linux-v5.4/Documentation/trace/ |
| D | ring-buffer-design.txt | 291 be several pages ahead. If the tail page catches up to the commit
347 the head page will be pushed ahead one. If the buffer is in producer/consumer
778 the tail page ahead several pages:
|
| /Linux-v5.4/Documentation/devicetree/ |
| D | of_unittest.txt | 12 It is recommended to read the following documents before moving ahead.
|
| /Linux-v5.4/Documentation/driver-api/md/ |
| D | raid5-cache.rst | 84 checksumed too. The checksum is stored in the meta data ahead of the data. The
|
| /Linux-v5.4/Documentation/scsi/ |
| D | st.txt | 262 Read ahead for fixed block mode (ST_READ_AHEAD). Filling the buffer is
435 MT_ST_READ_AHEAD read ahead (mode)
562 When using read ahead or buffered writes the position within the file
567 (The driver always backs over a filemark crossed by read ahead if the
|
| /Linux-v5.4/arch/arm/mm/ |
| D | Kconfig | 939 bool "Enable the Broadcom Brahma-B15 read-ahead cache controller"
943 This option enables the Broadcom Brahma-B15 read-ahead cache
944 controller. If disabled, the read-ahead cache remains off.
|
| /Linux-v5.4/Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-mt7622.txt | 84 related physical number is also put ahead of those names which helps cross
|
| /Linux-v5.4/Documentation/vm/ |
| D | unevictable-lru.rst | 314 If the page is still associated with its mapping, we'll go ahead and call
403 we go ahead and clear PG_mlocked up front, as this might be the only chance we
404 have. If we can successfully isolate the page, we go ahead and
|
| /Linux-v5.4/Documentation/block/ |
| D | queue-sysfs.rst | 177 Maximum number of kilobytes to read-ahead for filesystems on this block
|
123
