Home
last modified time | relevance | path

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

123

/Linux-v5.4/include/linux/
Dlist_lru.h168 list_lru_walk_cb isolate, void *cb_arg,
185 list_lru_walk_cb isolate, void *cb_arg,
188 list_lru_walk_cb isolate, void *cb_arg,
193 list_lru_walk_cb isolate, void *cb_arg) in list_lru_shrink_walk() argument
195 return list_lru_walk_one(lru, sc->nid, sc->memcg, isolate, cb_arg, in list_lru_shrink_walk()
201 list_lru_walk_cb isolate, void *cb_arg) in list_lru_shrink_walk_irq() argument
203 return list_lru_walk_one_irq(lru, sc->nid, sc->memcg, isolate, cb_arg, in list_lru_shrink_walk_irq()
208 list_lru_walk(struct list_lru *lru, list_lru_walk_cb isolate, in list_lru_walk() argument
215 isolated += list_lru_walk_node(lru, nid, isolate, in list_lru_walk()
/Linux-v5.4/mm/
Dlist_lru.c211 list_lru_walk_cb isolate, void *cb_arg, in __list_lru_walk_one() argument
232 ret = isolate(item, l, &nlru->lock, cb_arg); in __list_lru_walk_one()
269 list_lru_walk_cb isolate, void *cb_arg, in list_lru_walk_one() argument
276 ret = __list_lru_walk_one(nlru, memcg_cache_id(memcg), isolate, cb_arg, in list_lru_walk_one()
285 list_lru_walk_cb isolate, void *cb_arg, in list_lru_walk_one_irq() argument
292 ret = __list_lru_walk_one(nlru, memcg_cache_id(memcg), isolate, cb_arg, in list_lru_walk_one_irq()
299 list_lru_walk_cb isolate, void *cb_arg, in list_lru_walk_node() argument
305 isolated += list_lru_walk_one(lru, nid, NULL, isolate, cb_arg, in list_lru_walk_node()
313 isolate, cb_arg, in list_lru_walk_node()
/Linux-v5.4/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
/Linux-v5.4/drivers/vfio/
DKconfig36 VFIO is built on the ability to isolate devices using the IOMMU.
/Linux-v5.4/arch/mips/dec/
Dint-handler.S138 and t0,t1 # isolate allowed ones
/Linux-v5.4/Documentation/vm/
Dunevictable-lru.rst71 same code to isolate them (for migrate, etc.), the same code to keep track
76 can only migrate pages that it can successfully isolate from the LRU
242 attempting to isolate them, thus abandoning the count of VM_LOCKED VMAs. When
327 If the page was NOT already mlocked, mlock_vma_page() attempts to isolate the
332 mlock_vma_page() is unable to isolate the page from the LRU, vmscan will handle
404 have. If we can successfully isolate the page, we go ahead and
407 to isolate the page, we'll have left a potentially mlocked page on the LRU.
530 in the process of munlocking the page could not isolate the page from the LRU.
610 into VM_LOCKED VMAs that munlock_vma_page() couldn't isolate from the LRU to
/Linux-v5.4/arch/alpha/lib/
Dstrrchr.S56 negq t1, t4 # e0 : isolate first null byte match
Dev67-strrchr.S84 negq t1, t4 # E : isolate first null byte match
Dstxcpy.S216 negq t8, t6 # e0 : isolate low bit set
Dev6-stxcpy.S243 negq t8, t6 # E : isolate low bit set
Dstxncpy.S252 negq t8, t6 # e0 : isolate low bit set
Dev6-stxncpy.S296 negq t8, t6 # E : isolate low bit set
/Linux-v5.4/drivers/fpga/
DKconfig113 isolate one region of the FPGA from the busses while that
122 The PR Decoupler exists in the FPGA fabric to isolate one
/Linux-v5.4/arch/arm/mach-omap2/
Dsram243x.S143 mov r5, r5, lsr #8 @ isolate rfr field and drop burst
280 and r8, r8, #3 @ isolate field
Dsram242x.S143 mov r5, r5, lsr #8 @ isolate rfr field and drop burst
280 and r8, r8, #3 @ isolate field
/Linux-v5.4/Documentation/arm/nwfpe/
Dnwfpe.rst44 attempting to isolate the problem. Please report them, but don't
/Linux-v5.4/arch/um/
DKconfig180 syscalls, it's possible to isolate those applications in
/Linux-v5.4/Documentation/arm/
Dkernel_mode_neon.rst91 * isolate the NEON code in a separate compilation unit and compile it with
/Linux-v5.4/drivers/net/ethernet/sfc/falcon/
Dfalcon.c1370 int link_speed, isolate; in falcon_reconfigure_mac_wrapper() local
1372 isolate = !!READ_ONCE(efx->reset_pending); in falcon_reconfigure_mac_wrapper()
1395 !link_state->up || isolate); in falcon_reconfigure_mac_wrapper()
1409 EF4_SET_OWORD_FIELD(reg, FRF_BZ_RX_INGR_EN, !isolate); in falcon_reconfigure_mac_wrapper()
/Linux-v5.4/Documentation/networking/dsa/
Dsja1105.rst103 be restricted through two methods: either at the L2 forwarding level (isolate
105 (isolate ports within the same bridge). The final forwarding decision taken by
/Linux-v5.4/arch/microblaze/
DKconfig132 syscalls, it's possible to isolate those applications in

123