| /linux-4.4.14/tools/perf/bench/ |
| D | sched-pipe.c | 42 static bool threaded; variable
46 OPT_BOOLEAN('T', "threaded", &threaded, "Specify threads/process based task setup"),
117 if (threaded) { in bench_sched_pipe()
154 loops, threaded ? "threads" : "processes"); in bench_sched_pipe()
|
| /linux-4.4.14/scripts/coccinelle/misc/ |
| D | irqf_oneshot.cocci | 1 /// Since commit 1c6c69525b40 ("genirq: Reject bogus threaded irq requests")
2 /// threaded IRQs without a primary handler need to be requested with
|
| /linux-4.4.14/Documentation/usb/ |
| D | dwc3.txt | 27 - threaded handler of the device
38 - threaded handler of the EP-interrupt
|
| /linux-4.4.14/arch/metag/ |
| D | Kconfig.soc | 29 a 2-threaded HTP.
|
| /linux-4.4.14/fs/squashfs/ |
| D | Kconfig | 64 If in doubt, select "Single threaded compression"
67 bool "Single threaded compression"
69 Traditionally Squashfs has used single-threaded decompression.
|
| /linux-4.4.14/Documentation/gpio/ |
| D | driver.txt | 108 RT_FULL: Note, chained IRQ handlers will not be forced threaded on -RT.
111 if required (and if it can't be converted to the nested threaded GPIO irqchip)
113 it will be threaded IRQ handler on -RT and hard IRQ handler on non-RT
136 RT_FULL: Such kind of handlers will be forced threaded on -RT, as result IRQ
153 The hallmark of threaded GPIO irqchips is that they set the .can_sleep
|
| D | consumer.txt | 175 don't need to sleep, and can safely be done from inside hard (non-threaded) IRQ
212 Accessing such GPIOs requires a context which may sleep, for example a threaded
|
| D | gpio-legacy.txt | 218 a threaded IRQ handler, and those accessors must be used instead of
|
| /linux-4.4.14/Documentation/devicetree/bindings/dma/ |
| D | img-mdc-dma.txt | 1 * IMG Multi-threaded DMA Controller (MDC)
|
| /linux-4.4.14/Documentation/DocBook/ |
| D | genericirq.xml.db | 34 API-request-threaded-irq
|
| D | kernel-api.xml.db | 376 API-request-threaded-irq
|
| /linux-4.4.14/Documentation/mic/ |
| D | mic_overview.txt | 37 single threaded performance for the host compared to MIC, the ability of
|
| /linux-4.4.14/Documentation/vm/ |
| D | split_page_table_lock | 6 multi-threaded applications due high contention on the lock. To improve
|
| D | numa_memory_policy.txt | 50 In a multi-threaded task, task policies apply only to the thread
|
| /linux-4.4.14/Documentation/misc-devices/mei/ |
| D | mei-client-bus.txt | 119 threaded IRQ handler.
|
| /linux-4.4.14/fs/xfs/ |
| D | Kconfig | 9 on the SGI IRIX platform. It is completely multi-threaded, can
|
| /linux-4.4.14/Documentation/filesystems/caching/ |
| D | object.txt | 140 sleeping on I/O. This means that single-threaded and 1-per-CPU-threaded
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | f2fs.txt | 544 LFS has two schemes for free space management: threaded log and copy-and-compac-
548 overhead under high utilization. Contrarily, the threaded log scheme suffers
551 policy is dynamically changed to the threaded log scheme according to the file
|
| D | xfs.txt | 6 on the SGI IRIX platform. It is completely multi-threaded, can
|
| D | ext4.txt | 302 multi-threaded, synchronous workloads on very
|
| /linux-4.4.14/Documentation/ |
| D | kernel-per-CPU-kthreads.txt | 50 Purpose: Handle threaded interrupts.
65 Purpose: Execute softirq handlers when threaded or when under heavy load.
|
| D | workqueue.txt | 37 In the original wq implementation, a multi threaded (MT) wq had one
38 worker thread per CPU and a single threaded (ST) wq had one worker
|
| D | memory-barriers.txt | 1350 optimizations that, while perfectly safe in single-threaded code, can
1379 for single-threaded code, is almost certainly not what the developer
1400 single-threaded code, but can be fatal in concurrent code:
1418 single-threaded code, so you need to tell the compiler about cases
1432 This transformation is a win for single-threaded code because it
1495 win for single-threaded code:
1556 In single-threaded code, this is not only safe, but also saves
1585 This optimization can therefore be a win in single-threaded code.
2203 be a problem as a single-threaded linear piece of code will still appear to
|
| D | unshare.txt | 57 even non-threaded applications if they have a need to disassociate
|
| D | dma-buf-sharing.txt | 439 multi-threaded app[3]. The issue is made worse when it is library code
|
| D | CodingStyle | 585 Data structures that have visibility outside the single-threaded
|
| /linux-4.4.14/drivers/media/usb/pwc/ |
| D | philips.txt | 72 slack when your program is behind. But you need a multi-threaded or
|
| /linux-4.4.14/drivers/staging/rdma/hfi1/ |
| D | hfi.h | 316 int (*do_interrupt)(struct hfi1_ctxtdata *rcd, int threaded);
|
| /linux-4.4.14/Documentation/serial/ |
| D | driver | 58 The core driver uses the info->tmpbuf_sem lock to prevent multi-threaded
|
| /linux-4.4.14/drivers/dma/ |
| D | Kconfig | 214 Enable support for the IMG multi-threaded DMA controller (MDC).
|
| /linux-4.4.14/Documentation/arm/ |
| D | cluster-pm-race-avoidance.txt | 97 referred to as a "CPU". CPUs are assumed to be single-threaded:
|
| /linux-4.4.14/Documentation/PCI/ |
| D | pci-error-recovery.txt | 168 >>> Doing better requires complex multi-threaded logic in the error
|
| /linux-4.4.14/mm/ |
| D | Kconfig | 203 # Heavily threaded applications may benefit from splitting the mm-wide
|
| /linux-4.4.14/init/ |
| D | Kconfig | 1575 by some high performance threaded applications. Disabling
|
| /linux-4.4.14/Documentation/RCU/ |
| D | RTFP.txt | 2529 single-threaded loads (on an SMP kernel), because it gets rid of some
|
| /linux-4.4.14/arch/x86/ |
| D | Kconfig | 940 spurious interrupts. This is recommended when threaded
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | api.txt | 225 single-threaded guest vcpus, it should make all vcpu ids be a multiple
|