| /linux/tools/testing/selftests/drivers/net/lib/py/ |
| H A D | load.py | 41 proc = cmd(cmdline, background=True) 46 def start_client(self, background=False, streams=1, duration=10, reverse=False): argument 51 kwargs = {"background": background, "host": self.env.remote} 52 if not background: 90 self._iperf_client = self.runner.start_client(background=True, streams=16, duration=86400)
|
| /linux/Documentation/sphinx-static/ |
| H A D | custom.css | 42 dl.function, dl.struct, dl.enum { margin-top: 2em; background-color: #ecf0f3; } 59 dl.py { margin-top: 2em; background-color: #ecf0f3; } 77 div.kerneltoc { background-color: #eeeeee; } 78 div.kerneltoc li.current ul { background-color: white; } 132 background: #eeeeee; 159 background: #fafafa; 171 background: #dddddd;
|
| H A D | theme_rtd_colors.css | 35 background-color: darkblue;
|
| H A D | theme_overrides.css | 113 background: inherit;
|
| /linux/Documentation/admin-guide/ |
| H A D | vga-softcursor.rst | 10 make it inverse background of the character it's over or to highlight 28 + 32 if you want to always change the background color 29 + 64 if you dislike having the background the same as the 37 VGA, the high four bits specify background and the low four the
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | dm-clone.rst | 19 background, in parallel with user I/O. 109 the devices and pauses the background hydration when there is I/O in-flight. 162 no_hydration Create a dm-clone instance with background hydration 172 one time, during background hydration. 173 hydration_batch_size <#regions> During background hydration, try to batch 214 Disable the background hydration of the destination device. 217 Enable the background hydration of the destination device. 220 Set background hydration threshold. 223 Set background hydration batch size. 246 3. Enable background hydration of the destination device. [all …]
|
| /linux/drivers/gpu/ipu-v3/ |
| H A D | ipu-dp.c | 54 struct ipu_dp background; member 76 return container_of(dp, struct ipu_flow, background); in to_flow() 197 if (flow->foreground.in_cs == flow->background.in_cs) { in ipu_dp_setup_channel() 213 flow->background.in_cs, in ipu_dp_setup_channel() 327 dp = &priv->flow[flow >> 1].background; in ipu_dp_get() 364 priv->flow[i].background.in_cs = IPUV3_COLORSPACE_UNKNOWN; in ipu_dp_init()
|
| /linux/tools/power/pm-graph/ |
| H A D | bootgraph.py | 636 .c1 {background:rgba(209,0,0,0.4);}\n\ 637 .c2 {background:rgba(255,102,34,0.4);}\n\ 638 .c3 {background:rgba(255,218,33,0.4);}\n\ 639 .c4 {background:rgba(51,221,0,0.4);}\n\ 640 .c5 {background:rgba(17,51,204,0.4);}\n\ 641 .c6 {background:rgba(34,0,102,0.4);}\n\ 642 .c7 {background:rgba(51,0,68,0.4);}\n\ 643 .c8 {background:rgba(204,255,204,0.4);}\n\ 644 .c9 {background:rgba(169,208,245,0.4);}\n\ 645 .c10 {background:rgba(255,255,204,0.4);}\n\ [all …]
|
| /linux/rust/zerocopy/rustdoc/ |
| H A D | style.css | 45 background-color: var(--code-block-background-color);
|
| /linux/tools/perf/Documentation/ |
| H A D | perf-daemon.txt | 7 perf-daemon - Run record sessions on background 26 You can imagine 'perf daemon' of background process with several 72 Do not put the process in background.
|
| /linux/tools/testing/selftests/net/lib/py/ |
| H A D | utils.py | 47 background=False, host=None, timeout=20, ksft_ready=None, argument 100 if not background: 183 super().__init__(comm, background=True,
|
| /linux/drivers/gpu/drm/tegra/ |
| H A D | dc.c | 269 u32 background[3] = { in tegra_plane_setup_blending_legacy() local 297 background[0] |= BLEND_CONTROL_DEPENDENT; in tegra_plane_setup_blending_legacy() 298 background[1] |= BLEND_CONTROL_DEPENDENT; in tegra_plane_setup_blending_legacy() 310 background[2] |= BLEND_CONTROL_DEPENDENT; in tegra_plane_setup_blending_legacy() 314 background[2] |= BLEND_CONTROL_DEPENDENT; in tegra_plane_setup_blending_legacy() 333 background[i] |= BLEND_CONTROL_DEPENDENT; in tegra_plane_setup_blending_legacy() 340 background[2] |= BLEND_CONTROL_DEPENDENT; in tegra_plane_setup_blending_legacy() 351 background[2] |= BLEND_CONTROL_ALPHA; in tegra_plane_setup_blending_legacy() 355 background[2] |= BLEND_CONTROL_ALPHA; in tegra_plane_setup_blending_legacy() 362 tegra_plane_writel(plane, background[0], DC_WIN_BLEND_2WIN_X); in tegra_plane_setup_blending_legacy() [all …]
|
| /linux/fs/jffs2/ |
| H A D | Makefile | 11 jffs2-y += symlink.o build.o erase.o background.o fs.o writev.o
|
| /linux/include/linux/mtd/ |
| H A D | blktrans.h | 54 void (*background)(struct mtd_blktrans_dev *dev); member
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-fs-f2fs | 309 Description: Do background GC aggressively when set. Set to 0 by default. 378 Description: Number of checkpoint operations performed in the background to 390 Description: Number of garbage collection operations triggered in background. 402 Description: Number of blocks moved by garbage collection in background. 692 Description: When space utilization exceeds this, do background DISCARD aggressively. 760 Description: Controls background discard granularity of inner discard thread 791 Description: It controls to enable/disable IO aware feature for background discard. 827 background GC thread. the default number is "60". 834 background GC thread. the default number is "25". 841 background GC thread from initiating GC for sections having valid blocks [all …]
|
| /linux/Documentation/edac/ |
| H A D | scrub.rst | 73 control over patrol (background) scrubbing (e.g., ACPI RAS2, CXL) and/or 80 for example, to disable background patrol scrubbing or adjust the scrub 81 rate for performance-aware operations where background activities need to 123 with performance-aware operations which require the background operations to 158 2. Provision for background (patrol) scrubbing of the entire memory system,
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | app-pri.rst | 15 working in background, which can be preempted by user controlled
|
| H A D | vidioc-g-priority.rst | 60 - Lowest priority, usually applications running in background, for
|
| /linux/include/uapi/linux/ |
| H A D | omapfb.h | 169 __u32 background; member
|
| /linux/Documentation/core-api/ |
| H A D | memory-allocation.rst | 90 Memory allocations may trigger direct or background reclaim and it is 96 doesn't kick the background reclaim. Should be used carefully because it 112 * ``GFP_KERNEL`` - both background and direct reclaim are allowed and the
|
| /linux/Documentation/arch/x86/ |
| H A D | amd-hfi.rst | 26 sending background threads to the dense cores while sending high priority 28 background threads to dense cores can free up power headroom and allow the
|
| /linux/drivers/mtd/ |
| H A D | mtd_blkdevs.c | 133 if (tr->background && !background_done) { in mtd_blktrans_work() 136 tr->background(dev); in mtd_blktrans_work()
|
| /linux/Documentation/filesystems/fuse/ |
| H A D | fuse-io.rst | 37 fast. Dirty pages are written back implicitly (background writeback or page
|
| H A D | fuse.rst | 133 The maximum number of background requests that can be outstanding 134 at a time. When the number of background requests reaches this limit, 139 The threshold of background requests at which the kernel considers 140 the filesystem to be congested. When the number of background requests
|
| /linux/Documentation/scheduler/ |
| H A D | sched-arch.rst | 54 although it may be reasonable to do some background work or enter
|