Searched full:were (Results 1 – 25 of 4483) sorted by relevance
12345678910>>...180
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | hist-v4l2.rst | 29 aliases ``O_NONCAP`` and ``O_NOIO`` were defined. Applications can set
40 struct ``video_standard`` and the color subcarrier fields were
59 module. The ``YUV422`` and ``YUV411`` planar image formats were added.
62 output devices were added.
110 Version 0.20 introduced a number of changes which were *not backward
115 1. Some typos in ``V4L2_FMT_FLAG`` symbols were fixed. struct v4l2_clip
137 4. All the different get- and set-format commands were swept into one
152 ``VIDIOC_S_PARM`` ioctls were merged with ``VIDIOC_G_OUTPARM`` and
159 6. Control enumeration was simplified, and two new control flags were
188 cause errors if it were being used for timestamping a multimedia
[all …]
|
| /kernel/linux/linux-4.19/Documentation/media/uapi/v4l/ |
| D | hist-v4l2.rst | 29 aliases ``O_NONCAP`` and ``O_NOIO`` were defined. Applications can set
40 struct ``video_standard`` and the color subcarrier fields were
59 module. The ``YUV422`` and ``YUV411`` planar image formats were added.
62 output devices were added.
114 Version 0.20 introduced a number of changes which were *not backward
119 1. Some typos in ``V4L2_FMT_FLAG`` symbols were fixed. struct
144 4. All the different get- and set-format commands were swept into one
160 ``VIDIOC_S_PARM`` ioctls were merged with ``VIDIOC_G_OUTPARM`` and
168 6. Control enumeration was simplified, and two new control flags were
197 cause errors if it were being used for timestamping a multimedia
[all …]
|
| /kernel/linux/linux-4.19/Documentation/networking/ |
| D | altera_tse.txt | 8 driver were built for a Cyclone(R) V SOC FPGA board, a Cyclone(R) V FPGA board,
20 Quartus toolchain. Quartus 13.1 and 14.0 were used to build the design that
178 statistic is a count of the number of packets received that were not addressed
182 statistic is a count of the number of packets received that were addressed to
186 statistic is a count of the number of packets received that were addressed to
195 statistic counts the number of packets transmitted that were not addressed to
199 statistic counts the number of packets transmitted that were addressed to a
203 statistic counts the number of packets transmitted that were addressed to a
227 This statistic counts the total number of packets received that were 64 octets
231 2819. This statistic counts the total number of packets received that were
[all …]
|
| /kernel/linux/linux-5.10/Documentation/networking/device_drivers/ethernet/altera/ |
| D | altera_tse.rst | 14 driver were built for a Cyclone(R) V SOC FPGA board, a Cyclone(R) V FPGA board,
26 Quartus toolchain. Quartus 13.1 and 14.0 were used to build the design that
201 statistic is a count of the number of packets received that were not addressed
205 statistic is a count of the number of packets received that were addressed to
209 statistic is a count of the number of packets received that were addressed to
218 statistic counts the number of packets transmitted that were not addressed to
222 statistic counts the number of packets transmitted that were addressed to a
226 statistic counts the number of packets transmitted that were addressed to a
250 This statistic counts the total number of packets received that were 64 octets
254 2819. This statistic counts the total number of packets received that were
[all …]
|
| /kernel/linux/linux-5.10/Documentation/scheduler/ |
| D | sched-nice-design.rst | 8 Nice levels were always pretty weak under Linux and people continuously
14 units were driven by the HZ tick, so the smallest timeslice was 1/HZ.
17 much stronger than they were before in 2.4 (and people were happy about
48 this was long ago when hardware was weaker and caches were smaller, and
49 people were running number crunching apps at nice +19.)
83 nice levels were not 'punchy enough', so lots of people had to resort to
104 levels were changed to be "multiplicative" (or exponential) - that way
|
| /kernel/linux/linux-4.19/Documentation/scheduler/ |
| D | sched-nice-design.txt | 4 Nice levels were always pretty weak under Linux and people continuously
10 units were driven by the HZ tick, so the smallest timeslice was 1/HZ.
13 much stronger than they were before in 2.4 (and people were happy about
44 this was long ago when hardware was weaker and caches were smaller, and
45 people were running number crunching apps at nice +19.)
79 nice levels were not 'punchy enough', so lots of people had to resort to
100 levels were changed to be "multiplicative" (or exponential) - that way
|
| /kernel/linux/linux-4.19/block/partitions/ |
| D | Kconfig | 9 were partitioned under an operating system running on a different
30 were partitioned using the Cumana interface on Acorn machines.
43 were partitioned using the ICS interface on Acorn machines.
88 were partitioned on an Alpha machine.
95 were partitioned under AmigaOS.
102 were partitioned under the Atari OS.
117 were partitioned on a Macintosh.
181 were partitioned using Windows 2000's/XP's or Vista's Logical Disk
254 were partitioned using EFI GPT.
|
| /kernel/linux/linux-5.10/block/partitions/ |
| D | Kconfig | 9 were partitioned under an operating system running on a different
30 were partitioned using the Cumana interface on Acorn machines.
43 were partitioned using the ICS interface on Acorn machines.
88 were partitioned on an Alpha machine.
95 were partitioned under AmigaOS.
102 were partitioned under the Atari OS.
117 were partitioned on a Macintosh.
181 were partitioned using Windows 2000's/XP's or Vista's Logical Disk
254 were partitioned using EFI GPT.
|
| /kernel/linux/linux-5.10/drivers/net/ethernet/neterion/vxge/ |
| D | vxge-traffic.h | 661 * @rx_rpa_discard: Count of received frames that were discarded because the
1207 * by the adapter that were discarded because the VPATH is out of service
1209 * adapter that were discared because the VPATH is out of service
1211 * the posted header credits for upstream PCI writes were depleted
1213 * the posted header credits for upstream PCI writes were depleted
1215 * the posted header credits for upstream PCI writes were depleted
1217 * the posted header credits for upstream PCI writes were depleted
1219 * the posted header credits for upstream PCI writes were depleted
1221 * the posted header credits for upstream PCI writes were depleted
1223 * the posted header credits for upstream PCI writes were depleted
[all …]
|
| /kernel/linux/linux-4.19/drivers/net/ethernet/neterion/vxge/ |
| D | vxge-traffic.h | 661 * @rx_rpa_discard: Count of received frames that were discarded because the
1207 * by the adapter that were discarded because the VPATH is out of service
1209 * adapter that were discared because the VPATH is out of service
1211 * the posted header credits for upstream PCI writes were depleted
1213 * the posted header credits for upstream PCI writes were depleted
1215 * the posted header credits for upstream PCI writes were depleted
1217 * the posted header credits for upstream PCI writes were depleted
1219 * the posted header credits for upstream PCI writes were depleted
1221 * the posted header credits for upstream PCI writes were depleted
1223 * the posted header credits for upstream PCI writes were depleted
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/tremontx/ |
| D | virtual-memory.json | 4 …ng SW prefetches) whose address translations missed in all TLB levels and were mapped to 4K pages.…
16 …ng SW prefetches) whose address translations missed in all TLB levels and were mapped to 2M or 4M …
28 …ue to demand data stores whose address translations missed in the TLB and were mapped to 4K pages.…
40 …ue to demand data stores whose address translations missed in the TLB and were mapped to 2M or 4M …
64 …e to instruction fetches whose address translations missed in the TLB and were mapped to 4K pages.…
76 …e to instruction fetches whose address translations missed in the TLB and were mapped to 2M or 4M …
|
| /kernel/linux/linux-5.10/Documentation/powerpc/ |
| D | vcpudispatch_stats.rst | 68 statistics were enabled. 4126 of those dispatches were on the same
69 physical cpu as the last time. 2683 were on a different core, but within
70 the same chip, while 30 dispatches were on a different chip compared to
74 6821 dispatches on the vcpu's home node, while 18 dispatches were
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/goldmontplus/ |
| D | virtual-memory.json | 4 …ng SW prefetches) whose address translations missed in all TLB levels and were mapped to 4K pages.…
16 …ng SW prefetches) whose address translations missed in all TLB levels and were mapped to 2M or 4M …
28 …ng SW prefetches) whose address translations missed in all TLB levels and were mapped to 1GB pages…
52 …ue to demand data stores whose address translations missed in the TLB and were mapped to 4K pages.…
64 …ue to demand data stores whose address translations missed in the TLB and were mapped to 2M or 4M …
76 …ue to demand data stores whose address translations missed in the TLB and were mapped to 1GB pages…
124 …e to instruction fetches whose address translations missed in the TLB and were mapped to 4K pages.…
136 …e to instruction fetches whose address translations missed in the TLB and were mapped to 2M or 4M …
148 …e to instruction fetches whose address translations missed in the TLB and were mapped to 1GB pages…
|
| /kernel/linux/linux-4.19/tools/perf/pmu-events/arch/x86/goldmontplus/ |
| D | virtual-memory.json | 4 …ng SW prefetches) whose address translations missed in all TLB levels and were mapped to 4K pages.…
16 …ng SW prefetches) whose address translations missed in all TLB levels and were mapped to 2M or 4M …
28 …ng SW prefetches) whose address translations missed in all TLB levels and were mapped to 1GB pages…
52 …ue to demand data stores whose address translations missed in the TLB and were mapped to 4K pages.…
64 …ue to demand data stores whose address translations missed in the TLB and were mapped to 2M or 4M …
76 …ue to demand data stores whose address translations missed in the TLB and were mapped to 1GB pages…
124 …e to instruction fetches whose address translations missed in the TLB and were mapped to 4K pages.…
136 …e to instruction fetches whose address translations missed in the TLB and were mapped to 2M or 4M …
148 …e to instruction fetches whose address translations missed in the TLB and were mapped to 1GB pages…
|
| /kernel/linux/linux-5.10/Documentation/networking/devlink/ |
| D | devlink-trap.rst | 91 * ``drop``: Trapped packets were dropped by the underlying device. Packets
94 * ``exception``: Trapped packets were not forwarded as intended by the
100 * ``control``: Trapped packets were trapped by the device because these are
160 is the port from which they were received
216 - Traps packets that should have been routed by the device, but were bigger
347 interface from which they were received. Such packets are routed by the
509 - Contains packet traps for packets that were dropped by the device during
512 - Contains packet traps for packets that were dropped by the device during
518 - Contains packet traps for packets that were dropped by the device due to
521 - Contains packet traps for packets that were dropped by the device during
[all …]
|
| /kernel/linux/linux-5.10/arch/x86/include/asm/ |
| D | olpc.h | 55 * order) were created: A1, B1, B2, B3, B4, C1. The A1 through B2 models
56 * were based on Geode GX CPUs, and models after that were based upon
57 * Geode LX CPUs. There were also some hand-assembled models floating
|
| /kernel/linux/linux-4.19/arch/x86/include/asm/ |
| D | olpc.h | 57 * order) were created: A1, B1, B2, B3, B4, C1. The A1 through B2 models
58 * were based on Geode GX CPUs, and models after that were based upon
59 * Geode LX CPUs. There were also some hand-assembled models floating
|
| /kernel/linux/linux-4.19/tools/perf/pmu-events/arch/x86/ivytown/ |
| D | uncore-power.json | 10 …units). One can also use inversion (filter_inv=1) to track cycles when we were less than the confi…
20 …units). One can also use inversion (filter_inv=1) to track cycles when we were less than the confi…
30 …units). One can also use inversion (filter_inv=1) to track cycles when we were less than the confi…
40 …units). One can also use inversion (filter_inv=1) to track cycles when we were less than the confi…
50 …units). One can also use inversion (filter_inv=1) to track cycles when we were less than the confi…
61 …units). One can also use inversion (filter_inv=1) to track cycles when we were less than the confi…
72 …units). One can also use inversion (filter_inv=1) to track cycles when we were less than the confi…
83 …units). One can also use inversion (filter_inv=1) to track cycles when we were less than the confi…
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/jaketown/ |
| D | uncore-power.json | 10 …units). One can also use inversion (filter_inv=1) to track cycles when we were less than the confi…
20 …units). One can also use inversion (filter_inv=1) to track cycles when we were less than the confi…
30 …units). One can also use inversion (filter_inv=1) to track cycles when we were less than the confi…
40 …units). One can also use inversion (filter_inv=1) to track cycles when we were less than the confi…
50 …units). One can also use inversion (filter_inv=1) to track cycles when we were less than the confi…
61 …units). One can also use inversion (filter_inv=1) to track cycles when we were less than the confi…
72 …units). One can also use inversion (filter_inv=1) to track cycles when we were less than the confi…
83 …units). One can also use inversion (filter_inv=1) to track cycles when we were less than the confi…
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/ivytown/ |
| D | uncore-power.json | 10 …units). One can also use inversion (filter_inv=1) to track cycles when we were less than the confi…
20 …units). One can also use inversion (filter_inv=1) to track cycles when we were less than the confi…
30 …units). One can also use inversion (filter_inv=1) to track cycles when we were less than the confi…
40 …units). One can also use inversion (filter_inv=1) to track cycles when we were less than the confi…
50 …units). One can also use inversion (filter_inv=1) to track cycles when we were less than the confi…
61 …units). One can also use inversion (filter_inv=1) to track cycles when we were less than the confi…
72 …units). One can also use inversion (filter_inv=1) to track cycles when we were less than the confi…
83 …units). One can also use inversion (filter_inv=1) to track cycles when we were less than the confi…
|
| /kernel/linux/linux-4.19/tools/perf/pmu-events/arch/x86/jaketown/ |
| D | uncore-power.json | 10 …units). One can also use inversion (filter_inv=1) to track cycles when we were less than the confi…
20 …units). One can also use inversion (filter_inv=1) to track cycles when we were less than the confi…
30 …units). One can also use inversion (filter_inv=1) to track cycles when we were less than the confi…
40 …units). One can also use inversion (filter_inv=1) to track cycles when we were less than the confi…
50 …units). One can also use inversion (filter_inv=1) to track cycles when we were less than the confi…
61 …units). One can also use inversion (filter_inv=1) to track cycles when we were less than the confi…
72 …units). One can also use inversion (filter_inv=1) to track cycles when we were less than the confi…
83 …units). One can also use inversion (filter_inv=1) to track cycles when we were less than the confi…
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | stable-api-nonsense.rst | 20 will not break. I have old programs that were built on a pre 0.9something
119 subsystem. These reworks were done to address a number of different
126 - A change was made in the way data packets were allocated from the
137 In both of these instances, all developers agreed that these were
138 important changes that needed to be made, and they were made, with
150 happens, all drivers that use the interfaces were also fixed at the
153 were not allowed to change, fixing this kind of security problem and
|
| /kernel/linux/linux-4.19/Documentation/process/ |
| D | stable-api-nonsense.rst | 20 will not break. I have old programs that were built on a pre 0.9something
119 subsystem. These reworks were done to address a number of different
126 - A change was made in the way data packets were allocated from the
137 In both of these instances, all developers agreed that these were
138 important changes that needed to be made, and they were made, with
150 happens, all drivers that use the interfaces were also fixed at the
153 were not allowed to change, fixing this kind of security problem and
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/goldmont/ |
| D | other.json | 24 …"PublicDescription": "Counts the number of issue slots per core cycle that were not consumed by th…
34 …"PublicDescription": "Counts the number of issue slots per core cycle that were not consumed becau…
44 …were not consumed by the backend because allocation is stalled waiting for a mispredicted jump to …
|
| /kernel/linux/linux-4.19/tools/perf/pmu-events/arch/x86/goldmont/ |
| D | other.json | 24 …"PublicDescription": "Counts the number of issue slots per core cycle that were not consumed by th…
34 …"PublicDescription": "Counts the number of issue slots per core cycle that were not consumed becau…
44 …were not consumed by the backend because allocation is stalled waiting for a mispredicted jump to …
|
12345678910>>...180