That (full) in projects: kernel - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:that (Results 1 – 25 of 11769) sorted by relevance

12 3 4 5 6 7 8 9 10 >>...471

/kernel/linux/linux-4.19/include/media/
D	v4l2-ioctl.h	25 * @vidioc_querycap: pointer to the function that implements 27 * @vidioc_enum_fmt_vid_cap: pointer to the function that implements 30 * @vidioc_enum_fmt_vid_overlay: pointer to the function that implements 33 * @vidioc_enum_fmt_vid_out: pointer to the function that implements 36 * @vidioc_enum_fmt_vid_cap_mplane: pointer to the function that implements 39 * @vidioc_enum_fmt_vid_out_mplane: pointer to the function that implements 42 * @vidioc_enum_fmt_sdr_cap: pointer to the function that implements 45 * @vidioc_enum_fmt_sdr_out: pointer to the function that implements 48 * @vidioc_enum_fmt_meta_cap: pointer to the function that implements 51 * @vidioc_g_fmt_vid_cap: pointer to the function that implements [all …]
/kernel/linux/linux-5.10/include/media/
D	v4l2-ioctl.h	25 * @vidioc_querycap: pointer to the function that implements 27 * @vidioc_enum_fmt_vid_cap: pointer to the function that implements 30 * @vidioc_enum_fmt_vid_overlay: pointer to the function that implements 33 * @vidioc_enum_fmt_vid_out: pointer to the function that implements 36 * @vidioc_enum_fmt_sdr_cap: pointer to the function that implements 39 * @vidioc_enum_fmt_sdr_out: pointer to the function that implements 42 * @vidioc_enum_fmt_meta_cap: pointer to the function that implements 45 * @vidioc_enum_fmt_meta_out: pointer to the function that implements 48 * @vidioc_g_fmt_vid_cap: pointer to the function that implements 51 * @vidioc_g_fmt_vid_overlay: pointer to the function that implements [all …]
/kernel/linux/linux-5.10/Documentation/process/
D	management-style.rst	14 to do with reality. It started as a lark, but that doesn't mean that it 27 making it painfully obvious to the questioner that we don't have a clue 37 Everybody thinks managers make decisions, and that decision-making is 39 manager must be to make it. That's very deep and obvious, but it's not 47 competent to make that decision for them. 51 Namely that you are in the wrong job, and that they should be managing 60 It helps to realize that the key difference between a big decision and a 62 can be made small by just always making sure that if you were wrong (and 67 And people will even see that as true leadership (cough bullshit 71 things that can't be undone. Don't get ushered into a corner from which [all …]
D	6.Followthrough.rst	8 patches. One of the biggest mistakes that even experienced kernel 9 developers can make is to conclude that their work is now done. In truth, 13 It is a rare patch which is so good at its first posting that there is no 16 code. You, as the author of that code, will be expected to work with the 17 kernel community to ensure that your code is up to the kernel's quality 32 value and why you went to the trouble of writing it. But that value 36 to substantial rewrites - come from the understanding that Linux will 49 be working on the kernel years from now, but they understand that their 54 What all of this comes down to is that, when reviewers send you comments, 55 you need to pay attention to the technical observations that they are [all …]
/kernel/linux/linux-4.19/Documentation/process/
D	management-style.rst	13 to do with reality. It started as a lark, but that doesn't mean that it 26 making it painfully obvious to the questioner that we don't have a clue 36 Everybody thinks managers make decisions, and that decision-making is 38 manager must be to make it. That's very deep and obvious, but it's not 46 competent to make that decision for them. 50 Namely that you are in the wrong job, and that they should be managing 59 It helps to realize that the key difference between a big decision and a 61 can be made small by just always making sure that if you were wrong (and 66 And people will even see that as true leadership (cough bullshit 70 things that can't be undone. Don't get ushered into a corner from which [all …]
D	6.Followthrough.rst	8 patches. One of the biggest mistakes that even experienced kernel 9 developers can make is to conclude that their work is now done. In truth, 13 It is a rare patch which is so good at its first posting that there is no 16 code. You, as the author of that code, will be expected to work with the 17 kernel community to ensure that your code is up to the kernel's quality 32 value and why you went to the trouble of writing it. But that value 36 to substantial rewrites - come from the understanding that Linux will 49 be working on the kernel years from now, but they understand that their 54 What all of this comes down to is that, when reviewers send you comments, 55 you need to pay attention to the technical observations that they are [all …]
/kernel/linux/linux-4.19/Documentation/filesystems/
D	path-lookup.md	20 exploration is needed to discover, is that it is complex. There are 21 many rules, special cases, and implementation alternatives that all 24 tool that we will make extensive use of is "divide and conquer". For 39 of elements: "slashes" that are sequences of one or more "`/`" 40 characters, and "components" that are sequences of one or more 41 non-"`/`" characters. These form two kinds of paths. Those that 50 component, but that isn't always accurate: a pathname can lack both 60 it must identify a directory that already exists, otherwise an error 66 pathname that is just slashes have a final component. If it does 73 tempting to consider that to have an empty final component. In many [all …]
D	xfs-delayed-logging-design.txt	12 required for objects that are frequently logged. Some parts of inodes are more 17 The reason that this is such a concern is that XFS allows multiple separate 21 "re-logging". Conceptually, this is quite simple - all it requires is that any 23 changes in the new transaction that is written to the log. 25 That is, if we have a sequence of changes A through to F, and the object was 43 that an object being relogged does not prevent the tail of the log from ever 56 progresses, ensuring that current operation never gets blocked by itself if the 59 Hence it can be seen that the relogging operation is fundamental to the correct 63 the log over and over again. Worse is the fact that objects tend to get 67 Another feature of the XFS transaction subsystem is that most transactions are [all …]
/kernel/linux/linux-5.10/Documentation/filesystems/
D	path-lookup.rst	22 exploration is needed to discover, is that it is complex. There are 23 many rules, special cases, and implementation alternatives that all 26 tool that we will make extensive use of is "divide and conquer". For 41 of elements: "slashes" that are sequences of one or more "``/``" 42 characters, and "components" that are sequences of one or more 43 non-"``/``" characters. These form two kinds of paths. Those that 52 component, but that isn't always accurate: a pathname can lack both 62 it must identify a directory that already exists, otherwise an error 68 pathname that is just slashes have a final component. If it does 75 tempting to consider that to have an empty final component. In many [all …]
D	xfs-delayed-logging-design.rst	15 required for objects that are frequently logged. Some parts of inodes are more 20 The reason that this is such a concern is that XFS allows multiple separate 24 "re-logging". Conceptually, this is quite simple - all it requires is that any 26 changes in the new transaction that is written to the log. 28 That is, if we have a sequence of changes A through to F, and the object was 46 that an object being relogged does not prevent the tail of the log from ever 59 progresses, ensuring that current operation never gets blocked by itself if the 62 Hence it can be seen that the relogging operation is fundamental to the correct 66 the log over and over again. Worse is the fact that objects tend to get 70 Another feature of the XFS transaction subsystem is that most transactions are [all …]
/kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/goldmont/
D	cache.json	4 …"PublicDescription": "Counts memory requests originating from the core that miss in the L2 cache.", 14 …"PublicDescription": "Counts memory requests originating from the core that reference a cache line… 24 …"PublicDescription": "Counts the number of demand and prefetch transactions that the L2 XQ rejects… 34 …on which likely indicates back pressure from L2Q. It also counts requests that would have gone dir… 54 …"PublicDescription": "Counts cycles that fetch is stalled due to an outstanding ICache miss. That … 92 "BriefDescription": "Load uops retired that split a cache-line (Precise event capable)", 104 "BriefDescription": "Stores uops retired that split a cache-line (Precise event capable)", 116 "BriefDescription": "Memory uops retired that split a cache-line (Precise event capable)", 146 …"PublicDescription": "Counts the number of memory uops retired that is either a loads or a store o… 158 "PublicDescription": "Counts load uops retired that hit the L1 data cache.", [all …]
/kernel/linux/linux-4.19/tools/perf/pmu-events/arch/x86/goldmont/
D	cache.json	4 …"PublicDescription": "Counts memory requests originating from the core that miss in the L2 cache.", 14 …"PublicDescription": "Counts memory requests originating from the core that reference a cache line… 24 …"PublicDescription": "Counts the number of demand and prefetch transactions that the L2 XQ rejects… 34 …on which likely indicates back pressure from L2Q. It also counts requests that would have gone dir… 54 …"PublicDescription": "Counts cycles that fetch is stalled due to an outstanding ICache miss. That … 91 "BriefDescription": "Load uops retired that split a cache-line (Precise event capable)" 102 "BriefDescription": "Stores uops retired that split a cache-line (Precise event capable)" 113 "BriefDescription": "Memory uops retired that split a cache-line (Precise event capable)" 140 …"PublicDescription": "Counts the number of memory uops retired that is either a loads or a store o… 151 "PublicDescription": "Counts load uops retired that hit the L1 data cache.", [all …]
/kernel/linux/linux-4.19/Documentation/power/
D	freezing-of-tasks.txt	12 There are three per-task flags used for that, PF_NOFREEZE, PF_FROZEN 13 and PF_FREEZER_SKIP (the last one is auxiliary). The tasks that have 23 sets this variable. After this, it executes try_to_freeze_tasks() that sends a 25 All freezable tasks must react to that by calling try_to_freeze(), which 28 it loop until PF_FROZEN is cleared for it. Then, we say that the task is 35 try_to_freeze() function (defined in include/linux/freezer.h), that checks 42 that combine interruptible sleep with checking if the task is to be frozen and 64 order to clear the PF_FROZEN flag for each frozen task. Then, the tasks that 95 IV. Why do we do that? 104 filesystem-related information that must be consistent with the state of the [all …]
/kernel/linux/linux-5.10/Documentation/admin-guide/pm/
D	cpuidle.rst	33 CPU idle time management operates on CPUs as seen by the CPU scheduler (that 35 work in the system). In its view, CPUs are logical units. That is, they need 38 entity which appears to be fetching instructions that belong to one sequence 43 program) at a time, it is a CPU. In that case, if the hardware is asked to 44 enter an idle state, that applies to the processor as a whole. 51 time. The entire cores are CPUs in that case and if the hardware is asked to 52 enter an idle state, that applies to the core that asked for it in the first 54 that the core belongs to (in fact, it may apply to an entire hierarchy of larger 57 remaining core asks the processor to enter an idle state, that may trigger it 59 other cores in that unit. [all …]
/kernel/linux/linux-4.19/LICENSES/preferred/
D	LGPL-2.1	43 price. Our General Public Licenses are designed to make sure that you have 45 service if you wish); that you receive source code or can get it if you 46 want it; that you can change the software and use pieces of it in new free 47 programs; and that you are informed that you can do these things. 49 To protect your rights, we need to make restrictions that forbid 55 a fee, you must give the recipients all the rights that we gave you. You 56 must make sure that they, too, receive or can get the source code. If you 58 the recipients, so that they can relink them with the library after making 66 To protect each distributor, we want to make it very clear that there is no 68 else and passed on, the recipients should know that what they have is not [all …]
D	LGPL-2.0	39 General Public Licenses are designed to make sure that you have the freedom 41 wish), that you receive source code or can get it if you want it, that you 42 can change the software or use pieces of it in new free programs; and that 45 To protect your rights, we need to make restrictions that forbid anyone to 51 a fee, you must give the recipients all the rights that we gave you. You 52 must make sure that they, too, receive or can get the source code. If you 54 the recipients so that they can relink them with the library, after making 62 Also, for each distributor's protection, we want to make certain that 63 everyone understands that there is no warranty for this free library. If 65 recipients to know that what they have is not the original version, so that [all …]
/kernel/linux/linux-5.10/LICENSES/preferred/
D	LGPL-2.1	43 price. Our General Public Licenses are designed to make sure that you have 45 service if you wish); that you receive source code or can get it if you 46 want it; that you can change the software and use pieces of it in new free 47 programs; and that you are informed that you can do these things. 49 To protect your rights, we need to make restrictions that forbid 55 a fee, you must give the recipients all the rights that we gave you. You 56 must make sure that they, too, receive or can get the source code. If you 58 the recipients, so that they can relink them with the library after making 66 To protect each distributor, we want to make it very clear that there is no 68 else and passed on, the recipients should know that what they have is not [all …]
D	LGPL-2.0	39 General Public Licenses are designed to make sure that you have the freedom 41 wish), that you receive source code or can get it if you want it, that you 42 can change the software or use pieces of it in new free programs; and that 45 To protect your rights, we need to make restrictions that forbid anyone to 51 a fee, you must give the recipients all the rights that we gave you. You 52 must make sure that they, too, receive or can get the source code. If you 54 the recipients so that they can relink them with the library, after making 62 Also, for each distributor's protection, we want to make certain that 63 everyone understands that there is no warranty for this free library. If 65 recipients to know that what they have is not the original version, so that [all …]
/kernel/linux/linux-5.10/Documentation/power/
D	freezing-of-tasks.rst	17 There are three per-task flags used for that, PF_NOFREEZE, PF_FROZEN 18 and PF_FREEZER_SKIP (the last one is auxiliary). The tasks that have 28 sets this variable. After this, it executes try_to_freeze_tasks() that sends a 30 All freezable tasks must react to that by calling try_to_freeze(), which 33 it loop until PF_FROZEN is cleared for it. Then, we say that the task is 40 try_to_freeze() function (defined in include/linux/freezer.h), that checks 47 that combine interruptible sleep with checking if the task is to be frozen and 69 order to clear the PF_FROZEN flag for each frozen task. Then, the tasks that 101 IV. Why do we do that? 111 filesystem-related information that must be consistent with the state of the [all …]
/kernel/linux/linux-4.19/tools/perf/pmu-events/arch/x86/knightslanding/
D	memory.json	18 …"BriefDescription": "Counts any Prefetch requests that accounts for data responses from MCDRAM Far… 29 …"BriefDescription": "Counts any Prefetch requests that accounts for data responses from MCDRAM Loc… 40 …"BriefDescription": "Counts any Prefetch requests that accounts for data responses from DRAM Far. … 51 …"BriefDescription": "Counts any Prefetch requests that accounts for data responses from DRAM Local… 62 …"BriefDescription": "Counts any Read request that accounts for data responses from MCDRAM Far or … 73 …"BriefDescription": "Counts any Read request that accounts for data responses from MCDRAM Local.", 84 … "BriefDescription": "Counts any Read request that accounts for data responses from DRAM Far. ", 95 … "BriefDescription": "Counts any Read request that accounts for data responses from DRAM Local.", 106 …"BriefDescription": "Counts Demand code reads and prefetch code read requests that accounts for d… 117 …"BriefDescription": "Counts Demand code reads and prefetch code read requests that accounts for d… [all …]
/kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/knightslanding/
D	memory.json	18 …"BriefDescription": "Counts any Prefetch requests that accounts for data responses from MCDRAM Far… 29 …"BriefDescription": "Counts any Prefetch requests that accounts for data responses from MCDRAM Loc… 40 …"BriefDescription": "Counts any Prefetch requests that accounts for data responses from DRAM Far.", 51 …"BriefDescription": "Counts any Prefetch requests that accounts for data responses from DRAM Local… 62 …"BriefDescription": "Counts any Read request that accounts for data responses from MCDRAM Far or … 73 …"BriefDescription": "Counts any Read request that accounts for data responses from MCDRAM Local.", 84 … "BriefDescription": "Counts any Read request that accounts for data responses from DRAM Far.", 95 … "BriefDescription": "Counts any Read request that accounts for data responses from DRAM Local.", 106 …"BriefDescription": "Counts Demand code reads and prefetch code read requests that accounts for d… 117 …"BriefDescription": "Counts Demand code reads and prefetch code read requests that accounts for d… [all …]
/kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/silvermont/
D	cache.json	3 …"PublicDescription": "This event counts the number of demand and prefetch transactions that the L2… 9 … "BriefDescription": "Counts the number of request from the L2 that were not accepted into the XQ" 12 …that would have gone directly to the XQ, but are rejected due to a full or nearly full condition, … 18 …"BriefDescription": "Counts the number of request that were not accepted into the L2Q because the … 21 …"PublicDescription": "This event counts requests originating from the core that references a cache… 39 …that fetch is stalled due to an outstanding ICache miss. That is, the decoder queue is able to acc… 49 …"PublicDescription": "This event counts the number of retired loads that were prohibited from rece… 67 …"PublicDescription": "This event counts the number of retire stores that experienced cache line bo… 73 "BriefDescription": "Store uops that split cache line boundary" 77 …"PublicDescription": "This event counts the number of retire loads that experienced cache line bou… [all …]
/kernel/linux/linux-4.19/tools/perf/pmu-events/arch/x86/silvermont/
D	cache.json	3 …"PublicDescription": "This event counts the number of demand and prefetch transactions that the L2… 9 … "BriefDescription": "Counts the number of request from the L2 that were not accepted into the XQ" 12 …that would have gone directly to the XQ, but are rejected due to a full or nearly full condition, … 18 …"BriefDescription": "Counts the number of request that were not accepted into the L2Q because the … 21 …"PublicDescription": "This event counts requests originating from the core that references a cache… 39 …that fetch is stalled due to an outstanding ICache miss. That is, the decoder queue is able to acc… 49 …"PublicDescription": "This event counts the number of retired loads that were prohibited from rece… 67 …"PublicDescription": "This event counts the number of retire stores that experienced cache line bo… 73 "BriefDescription": "Store uops that split cache line boundary" 77 …"PublicDescription": "This event counts the number of retire loads that experienced cache line bou… [all …]
/kernel/linux/linux-5.10/Documentation/networking/devlink/
D	devlink-trap.rst	21 kernel so that it will route it as well and generate an ICMP Time Exceeded 39 as it allows users to obtain further visibility into packet drops that would 123 Generic packet traps are used to describe traps that trap well-defined packets 124 or packets that are trapped due to well-defined conditions (e.g., TTL error). 136 - Traps incoming packets that the device decided to drop because of a 140 - Traps incoming packets that the device decided to drop in case of VLAN 145 - Traps incoming packets that the device decided to drop in case they are 146 tagged with a VLAN that is not configured on the ingress bridge port 149 - Traps incoming packets that the device decided to drop in case the STP 153 - Traps packets that the device decided to drop in case they need to be [all …]
/kernel/linux/linux-4.19/Documentation/RCU/
D	stallwarn.txt	5 options that can be used to fine-tune the detector's operation. Finally, 31 o Booting Linux using a console connection that is too slow to 38 o Anything that prevents RCU's grace-period kthreads from running. 48 that low-priority task is not permitted to run on any other CPU, 54 o A CPU-bound real-time task in a CONFIG_PREEMPT_RT kernel that 66 Note that certain high-overhead debugging options, for example 74 slow system. Note that thermal throttling and on-demand governors 78 interrupt on a CPU that is not in dyntick-idle mode. This 88 leading the realization that the CPU had failed. 91 warning. Note that SRCU does -not- have CPU stall warnings. Please note [all …]

12 3 4 5 6 7 8 9 10 >>...471