Home
last modified time | relevance | path

Searched refs:garbage (Results 1 – 25 of 55) sorted by relevance

123

/Linux-v5.4/arch/alpha/lib/
Dev67-strrchr.S53 lda t5, -1 # E : build garbage mask
56 mskqh t5, a0, t4 # E : Complete garbage mask
58 cmpbge zero, t4, t4 # E : bits set iff byte is garbage
61 andnot t1, t4, t1 # E : clear garbage from null test
62 andnot t3, t4, t3 # E : clear garbage from char test
Dstrrchr.S31 lda t4, -1 # .. e1 : build garbage mask
37 cmpbge zero, t4, t4 # .. e1 : bits set iff byte is garbage
39 andnot t1, t4, t1 # .. e1 : clear garbage from null test
40 andnot t3, t4, t3 # e0 : clear garbage from char test
Dev67-strchr.S40 lda t4, -1 # E : build garbage mask
50 cmpbge zero, t4, t4 # E : bits set iff byte is garbage
58 andnot t0, t4, t0 # E : clear garbage bits
Dstrchr.S27 lda t4, -1 # .. e1 : build garbage mask
33 cmpbge zero, t4, t4 # .. e1 : bits set iff byte is garbage
38 andnot t0, t4, t0 # e0 : clear garbage bits
Dev6-csum_ipv6_magic.S148 zapnot $4,3,$0 # U : clear upper garbage bits
Dstxncpy.S160 mskql t0, a0, t0 # e0 : mask trailing garbage in dst
163 mskqh t1, a0, t1 # e0 : mask leading garbage in src
Dev6-stxncpy.S199 mskql t0, a0, t0 # U : mask trailing garbage in dst
203 mskqh t1, a0, t1 # U : mask leading garbage in src (stall)
Dstxcpy.S259 lda t2, -1 # e1 : mask out leading garbage in source
/Linux-v5.4/fs/jffs2/
DREADME.Locking17 the garbage collector will obtain this right at the beginning of
20 garbage collect pass.
49 avoid deadlocks with garbage collection -- the VFS will lock the i_sem
51 allocation may trigger garbage-collection, which may need to move a
53 VFS. If the garbage collection code were to attempt to lock the i_sem
54 of the inode from which it's garbage-collecting a physical node, this
59 mutex, which is obtained by the garbage collection code and also
94 pointer when the garbage collection thread exits. The code to kill the
132 the jffs2_raw_node_ref structures in question while the garbage
DTODO24 By writing _new_ nodes to one block, and garbage-collected REF_PRISTINE
/Linux-v5.4/drivers/tty/serial/
Dpmac_zilog.h365 #define ZS_CLEARFIFO(port) do { volatile unsigned char garbage; \
366 garbage = read_zsdata(port); \
367 garbage = read_zsdata(port); \
368 garbage = read_zsdata(port); \
/Linux-v5.4/net/unix/
DMakefile8 unix-y := af_unix.o garbage.o
/Linux-v5.4/fs/proc/
Dkcore.c261 LIST_HEAD(garbage); in kcore_update_ram()
275 list_splice_tail(&list, &garbage); in kcore_update_ram()
281 list_move(&pos->list, &garbage); in kcore_update_ram()
290 list_for_each_entry_safe(pos, tmp, &garbage, list) { in kcore_update_ram()
/Linux-v5.4/tools/memory-model/litmus-tests/
DMP+onceassign+derefonce.litmus8 * pre-initialization garbage when it traverses an RCU-protected data
/Linux-v5.4/Documentation/driver-api/
Dlightnvm-pblk.rst13 - Implement garbage collection.
/Linux-v5.4/Documentation/filesystems/
Df2fs.txt101 background_gc=%s Turn on/off cleaning operations, namely garbage
103 idle. If background_gc=on, it will turn on the garbage
104 collection and if background_gc=off, garbage collection
106 on synchronous garbage collection running in background.
107 Default value for this option is on. So garbage
228 run garbage collection to ensure that all available space can
232 avoid additional garbage collection. This can be given as a
269 time for the garbage collection thread. Time is
273 time for the garbage collection thread. Time is
277 time for the garbage collection thread. Time is
[all …]
Daffs.txt163 the bytes 0x00dc..0x00df of block 0 with garbage, thus invalidating
166 Linux will ignore this garbage and recognize the RDB anyway, but
Dnilfs2.txt25 cleaner or garbage collector) are required. Details on the tools are
131 NILFS_IOCTL_CLEAN_SEGMENTS Do garbage collection operation in the
/Linux-v5.4/arch/m68k/fpsp040/
Dx_ovfl.S14 | If the instruction is move_out, then garbage is stored in the
/Linux-v5.4/arch/arc/lib/
Dstrcmp.S74 cmp_s r3,r2 ; ... be independent of trailing garbage
/Linux-v5.4/Documentation/fb/
Dtridentfb.rst62 If in some modes which barely fit the memory you see garbage
/Linux-v5.4/Documentation/ABI/testing/
Dsysfs-fs-f2fs26 Controls the victim selection policy for garbage collection.
106 Controls migration granularity of garbage collection on large
/Linux-v5.4/Documentation/ioctl/
Dbotching-up-ioctls.rst75 an ioctl struct with random stack garbage in the yet unused parts. Which
77 but garbage. This is also the reason why you must explicitly pad all
79 might insert could contain garbage.
/Linux-v5.4/Documentation/networking/
Dxfrm_device.txt131 from a garbage collection routine after all reference counts to the state
/Linux-v5.4/Documentation/admin-guide/
Dbcache.rst540 Amount of dirty data is in the cache (updated when garbage collection runs).
575 duration: garbage collection, btree read, btree node sorts and btree splits.
598 Writing to this file forces garbage collection to run.
628 the SSD's garbage collection easier by effectively giving it more reserved

123