Home
last modified time | relevance | path

Searched refs:isolate (Results 1 – 45 of 45) sorted by relevance

/linux-4.4.14/include/linux/
Dlist_lru.h160 list_lru_walk_cb isolate, void *cb_arg,
163 list_lru_walk_cb isolate, void *cb_arg,
168 list_lru_walk_cb isolate, void *cb_arg) in list_lru_shrink_walk() argument
170 return list_lru_walk_one(lru, sc->nid, sc->memcg, isolate, cb_arg, in list_lru_shrink_walk()
175 list_lru_walk(struct list_lru *lru, list_lru_walk_cb isolate, in list_lru_walk() argument
182 isolated += list_lru_walk_node(lru, nid, isolate, in list_lru_walk()
/linux-4.4.14/mm/
Dlist_lru.c200 list_lru_walk_cb isolate, void *cb_arg, in __list_lru_walk_one() argument
223 ret = isolate(item, l, &nlru->lock, cb_arg); in __list_lru_walk_one()
260 list_lru_walk_cb isolate, void *cb_arg, in list_lru_walk_one() argument
264 isolate, cb_arg, nr_to_walk); in list_lru_walk_one()
269 list_lru_walk_cb isolate, void *cb_arg, in list_lru_walk_node() argument
275 isolated += __list_lru_walk_one(lru, nid, -1, isolate, cb_arg, in list_lru_walk_node()
280 isolate, cb_arg, nr_to_walk); in list_lru_walk_node()
/linux-4.4.14/arch/m68k/fpsp040/
Dx_store.S42 bfextu %d0{#6:#3},%d0 |isolate dest. reg from cmdreg3b
237 andw #0x7,%d0 |isolate register number
Dbugfix.S280 | It is necessary to isolate the result of the instruction in the
406 | It is necessary to isolate the result of the instruction in the
Dres_func.S117 andib #0x3b,%d0 |isolate bits to select inst
725 andib #0x60,%d0 |isolate tag bits
1418 andiw #0x0c00,%d0 |isolate last 2 bits of size field
1956 bfextu %d0{#16:#3},%d0 |isolate source bits
1984 bfextu %d0{#25:#3},%d0 |isolate register for dynamic k-factor
Dx_operr.S258 andil #7,%d0 |isolate register number
Dx_snan.S256 bfextu %d0{#0:#3},%d0 |isolate dtag in lsbs
Ddecbin.S432 bfextu %d3{#26:#2},%d2 |isolate rounding mode bits
Dbindec.S180 andiw #0xe000,%d0 |isolate stag bits
/linux-4.4.14/Documentation/vm/
Dunevictable-lru.txt95 same code to isolate them (for migrate, etc.), the same code to keep track
100 can only migrate pages that it can successfully isolate from the LRU
260 attempting to isolate them, thus abandoning the count of VM_LOCKED VMAs. When
345 If the page was NOT already mlocked, mlock_vma_page() attempts to isolate the
350 mlock_vma_page() is unable to isolate the page from the LRU, vmscan will handle
421 have. If we can successfully isolate the page, we go ahead and
424 to isolate the page, we'll have left a potentially mlocked page on the LRU.
526 in the process of munlocking the page could not isolate the page from the LRU.
604 into VM_LOCKED VMAs that munlock_vma_page() couldn't isolate from the LRU to
/linux-4.4.14/arch/alpha/lib/
Dstrrchr.S55 negq t1, t4 # e0 : isolate first null byte match
Dev67-strrchr.S83 negq t1, t4 # E : isolate first null byte match
Dstxcpy.S215 negq t8, t6 # e0 : isolate low bit set
Dev6-stxcpy.S242 negq t8, t6 # E : isolate low bit set
Dstxncpy.S251 negq t8, t6 # e0 : isolate low bit set
Dev6-stxncpy.S295 negq t8, t6 # E : isolate low bit set
/linux-4.4.14/arch/mips/dec/
Dint-handler.S137 and t0,t1 # isolate allowed ones
/linux-4.4.14/arch/arm/mach-omap2/
Dsram242x.S157 mov r5, r5, lsr #8 @ isolate rfr field and drop burst
294 and r8, r8, #3 @ isolate field
Dsram243x.S157 mov r5, r5, lsr #8 @ isolate rfr field and drop burst
294 and r8, r8, #3 @ isolate field
/linux-4.4.14/Documentation/arm/nwfpe/
DREADME41 attempting to isolate the problem. Please report them, but don't
/linux-4.4.14/arch/mips/include/asm/octeon/
Dcvmx-mdio.h52 uint16_t isolate:1; member
/linux-4.4.14/Documentation/arm/
Dkernel_mode_neon.txt89 * isolate the NEON code in a separate compilation unit and compile it with
/linux-4.4.14/drivers/net/ethernet/sfc/
Dfalcon.c1368 int link_speed, isolate; in falcon_reconfigure_mac_wrapper() local
1370 isolate = !!ACCESS_ONCE(efx->reset_pending); in falcon_reconfigure_mac_wrapper()
1393 !link_state->up || isolate); in falcon_reconfigure_mac_wrapper()
1407 EFX_SET_OWORD_FIELD(reg, FRF_BZ_RX_INGR_EN, !isolate); in falcon_reconfigure_mac_wrapper()
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-devices-edac119 This becomes vital for panic events to isolate the
/linux-4.4.14/arch/microblaze/
DKconfig121 syscalls, it's possible to isolate those applications in
/linux-4.4.14/arch/parisc/
DKconfig336 syscalls, it's possible to isolate those applications in
/linux-4.4.14/Documentation/
DBUG-HUNTING94 isolate the change to a directory.
Dedac.txt305 This becomes vital for panic events to isolate the
338 This becomes vital for panic events to isolate the
Dunshare.txt66 per-security context instance of a user's home directory, isolate user
Dkernel-parameters.txt1656 to isolate from the general SMP balancing and scheduling
1662 This option is the preferred way to isolate CPUs. The
/linux-4.4.14/drivers/iommu/
DKconfig101 can isolate the DMA memory of different devices and protect the
/linux-4.4.14/arch/tile/
DKconfig233 syscalls, it's possible to isolate those applications in
/linux-4.4.14/Documentation/input/
Dalps.txt14 table, with the risk of regression testing existing devices, or isolate
/linux-4.4.14/arch/sparc/
DKconfig245 syscalls, it's possible to isolate those applications in
/linux-4.4.14/Documentation/powerpc/
Deeh-pci-error-recovery.txt69 condition, it will "isolate" the affected PCI card. Isolation
Dpci_iov_resource_on_powernv.txt189 to a single PE, so it could only isolate one VF.
/linux-4.4.14/arch/sh/
DKconfig660 syscalls, it's possible to isolate those applications in
/linux-4.4.14/arch/s390/
DKconfig702 syscalls, it's possible to isolate those applications in
/linux-4.4.14/Documentation/PCI/
Dpci-error-recovery.txt155 particular, if the platform doesn't isolate slots), and recovery
/linux-4.4.14/arch/arm64/
DKconfig553 syscalls, it's possible to isolate those applications in
/linux-4.4.14/arch/powerpc/
DKconfig693 syscalls, it's possible to isolate those applications in
/linux-4.4.14/Documentation/scheduler/
Dsched-deadline.txt40 that makes it possible to isolate the behavior of tasks between each other.
/linux-4.4.14/arch/arm/
DKconfig1791 syscalls, it's possible to isolate those applications in
/linux-4.4.14/arch/mips/
DKconfig2691 syscalls, it's possible to isolate those applications in
/linux-4.4.14/arch/x86/
DKconfig1732 syscalls, it's possible to isolate those applications in