| /linux-6.15/Documentation/filesystems/bcachefs/ |
| D | casefolding.rst | 7 lookups using the regular `chattr +F` (`S_CASEFOLD`, `FS_CASEFOLD_FL`)
29 name with the regular name in the dirent.
33 * Regular: [dirent data][regular name][nul][nul]...
34 * Casefolded: [dirent data][reg len][cf len][regular name][casefolded name][nul][nul]...
41 it has identical performance to a regular lookup:
53 the regular name and casefolded name contiguously / 2 as the length. This would
54 assume that the regular length == casefolded length, but that could potentially
|
| /linux-6.15/Documentation/power/ |
| D | suspend-and-cpuhotplug.rst | 11 How does the regular CPU hotplug code differ from how the Suspend-to-RAM
21 What happens when regular CPU hotplug and Suspend-to-RAM race with each other
79 Disable regular cpu hotplug
99 | Decrease cpu_hotplug_disabled, thereby enabling regular cpu hotplug
117 Regular CPU hotplug call path
149 regular CPU hotplug]
154 regular CPU hotplug and the suspend code path converge at the _cpu_down() and
156 in that during regular CPU hotplug, 0 is passed for the 'tasks_frozen'
207 a regular CPU hotplug operation, upon receiving the CPU_DEAD notification
259 Are there any known problems when regular CPU hotplug and suspend race
[all …]
|
| /linux-6.15/scripts/lib/abi/ |
| D | abi_regex.py | 7 Convert ABI what into regular expressions
19 """Extends AbiParser to search ABI nodes with regular expressions"""
25 # Tuples with regular expressions to be compiled and replacement data
102 Get a search group for a subset of regular expressions.
105 regular expressions is at least O(n^2). When there are wildcards,
110 mean that searches will be confined to a small number of regular
115 regular expression. So, we need to discard nodes that have
118 If it can't obtain a subgroup, place the regular expression inside
150 Given an ABI devnode, return a list of all regular expressions that
184 msg = f"{self.search_string} is not a valid regular expression"
|
| /linux-6.15/tools/testing/selftests/bpf/progs/ |
| D | test_tcp_hdr_options.c | 90 struct tcp_opt regular; in store_option() member
103 write_opt.regular.kind = test_kind; in store_option()
104 write_opt.regular.len = option_total_len(test_opt->flags); in store_option()
105 write_opt.regular.data32 = 0; in store_option()
106 write_test_option(test_opt, write_opt.regular.data); in store_option()
107 err = bpf_store_hdr_opt(skops, &write_opt.regular, in store_option()
108 sizeof(write_opt.regular), 0); in store_option()
135 struct tcp_opt regular; in load_option() member
150 search_opt.regular.kind = test_kind; in load_option()
151 search_opt.regular.len = 0; in load_option()
[all …]
|
| /linux-6.15/Documentation/mm/ |
| D | balance.rst | 29 regular memory requests by allocating one from the dma pool, instead
30 of incurring the overhead of regular zone balancing.
34 right ratio of dma and regular memory, it is quite possible that balancing
58 Note that if the size of the regular zone is huge compared to dma zone,
60 deciding whether to balance the regular zone. The first solution
68 fall back into regular zone. This also makes sure that HIGHMEM pages
|
| D | transhuge.rst | 15 can continue working on the regular pages or regular pte mappings.
18 regular pages should be gracefully allocated instead and mixed in
24 backed by regular pages should be relocated on hugepages
101 regular pmd from under you (split_huge_pmd can run in parallel to the
|
| D | hmm.rst | 6 memory like GPU on board memory) into regular kernel path, with the cornerstone
34 driver and regular application memory (private anonymous, shared memory, or
35 regular file backed memory). From here on I will refer to this aspect as split
86 be considered the same as regular memory from the kernel point of view.
417 For now, device memory is accounted as any regular page in rss counters (either
424 device memory and not a lot of regular system memory and thus not freeing much
431 against same memory cgroup a regular page would be accounted to. This does
433 back from device memory to regular memory cannot fail because it would
|
| /linux-6.15/tools/perf/pmu-events/arch/x86/jaketown/ |
| D | uncore-cache.json | 1305 "BriefDescription": "iMC RPQ Credits Empty - Regular; Channel 0",
1310 …regular' credits available for posting reads from the HA into the iMC. In order to send reads int…
1315 "BriefDescription": "iMC RPQ Credits Empty - Regular; Channel 1",
1320 …regular' credits available for posting reads from the HA into the iMC. In order to send reads int…
1325 "BriefDescription": "iMC RPQ Credits Empty - Regular; Channel 2",
1330 …regular' credits available for posting reads from the HA into the iMC. In order to send reads int…
1335 "BriefDescription": "iMC RPQ Credits Empty - Regular; Channel 3",
1340 …regular' credits available for posting reads from the HA into the iMC. In order to send reads int…
1350 …redit for the iMC's RPQ (read pending queue). This queue is broken into regular credits/buffers t…
1360 …redit for the iMC's RPQ (read pending queue). This queue is broken into regular credits/buffers t…
[all …]
|
| /linux-6.15/include/linux/ |
| D | instrumented.h | 17 * instrument_read - instrument regular read access
21 * Instrument a regular read access. The instrumentation should be inserted
31 * instrument_write - instrument regular write access
35 * Instrument a regular write access. The instrumentation should be inserted
45 * instrument_read_write - instrument regular read-write access
49 * Instrument a regular write access. The instrumentation should be inserted
|
| /linux-6.15/Documentation/admin-guide/device-mapper/ |
| D | dm-zoned.rst | 6 ZAC compliant devices) as a regular block device without any write
40 metadata. It can also use a regular block device together with the zoned
41 block device; in that case the regular block device will be split logically
95 chunk, resulting in native random write performance similar to a regular
134 If a regular device is used in conjunction with the zoned block device,
139 are located at the start of the regular block device.
154 regular block device as the first device.
|
| /linux-6.15/arch/x86/lib/ |
| D | kaslr.c | 5 * kernel and memory randomization is done early when the regular
7 * normally linked in the regular.
17 * When built for the regular kernel, several functions need to be stubbed out
18 * or changed to their regular kernel equivalent.
|
| /linux-6.15/Documentation/driver-api/soundwire/ |
| D | bra.rst | 19 The regular control channel uses Column 0 and can only send/retrieve
52 (6) The regular read/write commands can be issued in parallel with
73 the paging registers used for the regular command/control
219 Concurrency between BRA and regular read/write
227 mutex for regular read/write and BRA is a show-stopper. Independent
241 "regular" read/writes in parallel with the command channel, and last
276 is available or not, and use a regular read-write command channel in
284 For regular audio transfers, the machine driver exposes a dailink
316 concept of multi-link aggregation allowed by regular DAI links.
|
| /linux-6.15/scripts/ |
| D | get_abi.py | 102 description="Search ABI using a regular expression")
122 The search logic tries to minimize the number of regular expressions to
129 is contained on a limit of ~150 regular expressions, using a single CPU
131 regular expressions to check is at the order of ~30000, using multiple
151 help="search string regular expression to limit symbol search")
|
| /linux-6.15/Documentation/arch/powerpc/ |
| D | pmu-ebb.rst | 46 concurrently with regular 'perf' commands, or any other perf events.
52 The exclusion between EBB events and regular events is implemented using the
55 If an EBB event and a regular event are both pinned, then whichever is enabled
118 regular event. If this is the last EBB event the PMU will be deconfigured and
125 The EBB handler is just regular userspace code, however it must be written in
|
| /linux-6.15/tools/perf/Documentation/ |
| D | perf-amd-ibs.txt | 39 IBS VS. REGULAR CORE PMU
43 no skid. Whereas the IP recorded by regular core PMU will have some skid
45 regular core PMU might not help for profiling with instruction level
47 question. On the other hand, regular core PMU has it's own advantages like
51 Three regular core PMU events are internally forwarded to IBS Op PMU when
|
| /linux-6.15/Documentation/devicetree/bindings/pinctrl/ |
| D | thead,th1520-pinctrl.yaml | 25 Pinconf is fairly regular except for a few pads in group 1 that either can't
97 description: Enable the regular 48kOhm pull-up
99 description: Enable the strong 2.1kOhm pull-up or regular 48kOhm pull-up
105 description: Enable the regular 44kOhm pull-down
|
| /linux-6.15/fs/ |
| D | fs_types.c | 33 * * DT_REG - Regular file
69 * * FT_REG_FILE - Regular file
97 * * DT_REG - Regular file
|
| /linux-6.15/Documentation/hid/ |
| D | hidraw.rst | 146 for regular input reports, but allows the host to request the value of a
149 the regular device read() interface. The format of the buffer issued with this report
156 This is slower on most devices where a dedicated Out endpoint exists for regular
159 updates via the regular device write() interface. The format of the buffer issued
168 via a HIDIOCSOUTPUT request, or the regular device write() interface. The format
|
| /linux-6.15/Documentation/userspace-api/ |
| D | perf_ring_buffer.rst | 26 3.1 The relationship between AUX and regular ring buffers
592 AUX ring buffer and the regular ring buffer, then the second part will
593 examine how the AUX ring buffer co-works with the regular ring buffer,
597 3.1 The relationship between AUX and regular ring buffers
600 Generally, the AUX ring buffer is an auxiliary for the regular ring
601 buffer. The regular ring buffer is primarily used to store the event
608 regular profile samples that write to the regular ring buffer cause an
610 using interrupts would be overwhelming for the regular ring buffer
614 The AUX ring buffer reuses the same algorithm with the regular ring
619 During the initialisation phase, besides the mmap()-ed regular ring
[all …]
|
| /linux-6.15/Documentation/bpf/ |
| D | bpf_prog_run.rst | 64 which means the semantics are not quite as straight-forward as the regular test
77 via the same trace points as for regular XDP programs.
80 the regular (non-live) mode. The XDP program will be executed as though the
108 immediately. If a packet ends up being passed to the regular networking stack
|
| /linux-6.15/drivers/net/slip/ |
| D | Kconfig | 23 allows you to use SLIP over a regular dial up shell connection. If
29 Internet connectivity if you have a regular dial up shell account on
56 allows you to use SLIP over a regular dial up shell connection, you
|
| /linux-6.15/arch/s390/include/asm/ |
| D | isc.h | 15 /* Regular I/O interrupts. */
16 #define IO_SCH_ISC 3 /* regular I/O subchannels */
|
| /linux-6.15/Documentation/admin-guide/mm/ |
| D | nommu-mmap.rst | 69 (#) Regular file / blockdev, MAP_SHARED, PROT_READ / PROT_EXEC / PROT_WRITE
77 (#) Memory backed regular file, MAP_SHARED, PROT_READ / PROT_EXEC / PROT_WRITE
79 In the MMU case: As for ordinary regular files.
90 In the MMU case: As for ordinary regular files.
92 In the no-MMU case: As for memory backed regular files, but the
99 In the MMU case: As for ordinary regular files.
|
| /linux-6.15/io_uring/ |
| D | opdef.h | 16 /* hash wq insertion if file is a regular file */
18 /* unbound wq insertion if file is a non-regular file */
|
| /linux-6.15/Documentation/filesystems/ |
| D | squashfs.rst | 53 file type, i.e. regular file, directory, symbolic link, and block/char device
185 (regular file, directory, device, etc.), the inode contents and length
188 To further maximise compression, two types of regular file inode and
190 regular files and directories, and extended types where extra
226 Regular files consist of a sequence of contiguous compressed blocks, and/or a
245 Regular files can contain a fragment index which is mapped to a fragment
255 For space efficiency regular files store uid and gid indexes, which are
|