Searched full:explicit (Results 1 – 25 of 358) sorted by relevance
12345678910>>...15
| /linux-3.3/Documentation/ |
| D | atomic_ops.txt | 37 proper implicit or explicit read memory barrier is needed before reading the
55 or explicit memory barrier is needed before the value set with the operation
65 implicit or explicit memory barrier is used after possible runtime
69 interface must take care of that with a proper implicit or explicit memory
183 atomic_t value. The first two routines pass explicit integers by
188 require any explicit memory barriers. They need only perform the
200 Unlike the above routines, it is required that explicit memory
209 If the atomic instructions used in an implementation provide explicit
219 explicit counter adjustment is given instead of the implicit "1".
232 It requires explicit memory barrier semantics around the operation as
[all …]
|
| D | preempt-locking.txt | 13 requires explicit additional locking for very few additional situations.
19 RULE #1: Per-CPU data structures need explicit protection
29 First, since the data is per-CPU, it may not have explicit SMP locking, but
123 in doubt, rely on locking or explicit preemption disabling.
|
| /linux-3.3/Documentation/RCU/ |
| D | lockdep.txt | 35 Use explicit check expression "c" along with
39 Use explicit check expression "c" along with
43 Use explicit check expression "c" along with
47 Use explicit check expression "c" along with
51 Use explicit check expression "c", but the caller
58 Use explicit check expression "c", and omit all barriers
|
| /linux-3.3/include/net/netfilter/ |
| D | nf_tproxy_core.h | 22 * Explicit TProxy target rule
26 * an explicit iptables rule. In this case the sockets are assumed
36 * regardless if it was bound to 0.0.0.0 or an explicit
37 * address. The reasoning is that if there's an explicit rule, it
46 * connection) that the user is unable to add explicit rules
49 * connections without explicit iptables rule (except of course the
|
| /linux-3.3/Documentation/block/ |
| D | writeback_cache_control.txt | 2 Explicit volatile write back cache control
20 Explicit cache flushes
28 set on an otherwise empty bio structure, which causes only an explicit cache
45 worry if the underlying devices need any explicit cache flushing and how
|
| /linux-3.3/arch/ia64/include/asm/sn/ |
| D | tioca_provider.h | 172 * Explicit flushes not needed if GART is in cached mode in tioca_tlbflush()
177 * PV910244: RevA CA needs explicit flushes. in tioca_tlbflush()
179 * flushing otherwise the explicit flush is ignored. in tioca_tlbflush()
196 * Gart in uncached mode ... need an explicit flush. in tioca_tlbflush()
|
| /linux-3.3/include/trace/events/ |
| D | block.h | 406 TP_PROTO(struct request_queue *q, unsigned int depth, bool explicit),
408 TP_ARGS(q, depth, explicit),
427 * @explicit: whether this was an explicit unplug, or one from schedule()
434 TP_PROTO(struct request_queue *q, unsigned int depth, bool explicit),
436 TP_ARGS(q, depth, explicit)
|
| /linux-3.3/tools/perf/util/ |
| D | cgroup.h | 13 extern int nr_cgroups; /* number of explicit cgroups defined */
|
| /linux-3.3/arch/x86/include/asm/xen/ |
| D | trace_types.h | 5 XEN_MC_FL_NONE, /* explicit flush */
|
| /linux-3.3/net/netlabel/ |
| D | Kconfig | 10 NetLabel provides support for explicit network packet labeling
|
| /linux-3.3/arch/arm/include/asm/ |
| D | futex.h | 56 " ite eq @ explicit IT needed for the 2b label\n" in futex_atomic_cmpxchg_inatomic()
100 " it eq @ explicit IT needed for the 2b label\n" in futex_atomic_cmpxchg_inatomic()
|
| /linux-3.3/include/drm/ |
| D | drm_crtc_helper.h | 75 /* disable crtc when not in use - more explicit than dpms off */
96 /* disable encoder when not in use - more explicit than dpms off */
|
| /linux-3.3/net/unix/ |
| D | garbage.c | 18 * - explicit stack instead of recursion
39 * skb_free() them all instead of doing explicit fput's.
56 * Kill the explicit allocation of stack. Now we keep the tree
|
| /linux-3.3/arch/m68k/include/asm/ |
| D | adb_iop.h | 29 #define ADB_IOP_EXPLICIT 0x80 /* nonzero if explicit command */
|
| /linux-3.3/include/net/netns/ |
| D | generic.h | 12 * stuff on the struct net without explicit struct net modification
|
| /linux-3.3/arch/powerpc/platforms/pseries/ |
| D | msi.c | 97 * disabling MSI with the explicit interface also disables MSI-X in rtas_disable_msi()
101 * may have failed because explicit interface is not in rtas_disable_msi()
405 * Try the new more explicit firmware interface, if that fails fall in rtas_setup_msi_irqs()
|
| /linux-3.3/Documentation/ABI/testing/ |
| D | sysfs-gpio | 8 userspace. GPIOs are only made available to userspace by an explicit
|
| D | sysfs-firmware-gsmi | 6 that provides callback functionality via explicit SMI
|
| /linux-3.3/kernel/ |
| D | Kconfig.preempt | 23 "explicit preemption points" to the kernel code. These new
|
| /linux-3.3/drivers/ide/ |
| D | Kconfig | 354 This driver adds explicit support for Acard AEC62xx (Artop ATP8xx)
378 This driver adds explicit support for AMD-7xx and AMD-8111 chips
388 This driver adds explicit support for ATI IXP chipset.
500 This driver adds explicit support for Intel PIIX and ICH chips.
635 This driver adds explicit support for VIA BusMastering IDE chips.
|
| /linux-3.3/Documentation/filesystems/configfs/ |
| D | configfs.txt | 27 A configfs config_item is created via an explicit userspace operation:
386 more explicit to have a method whereby userspace sees this divergence.
457 Far better would be an explicit action notifying the subsystem that the
458 config_item is ready to go. More importantly, an explicit action allows
|
| /linux-3.3/arch/arm/lib/ |
| D | clear_user.S | 43 it ne @ explicit IT needed for the label
|
| /linux-3.3/arch/arm/mach-prima2/ |
| D | rstc.c | 58 * datasheet doesn't require explicit delay between the set and clear in sirfsoc_reset_device()
|
| /linux-3.3/drivers/md/ |
| D | dm-sysfs.c | 93 * because nobody using md yet, no need to call explicit dm_get/put
|
| /linux-3.3/Documentation/filesystems/ |
| D | porting | 37 Keep in mind that now you need explicit initialization of private data
63 Replace DECLARE_FSTYPE... with explicit initializer and have ->get_sb set as
141 explicit support for exporting, e.g. via NFS. The structure is fully
|
12345678910>>...15