Home
last modified time | relevance | path

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

123

/linux-5.19.10/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)
/linux-5.19.10/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
/linux-5.19.10/net/unix/
DMakefile8 unix-y := af_unix.o garbage.o
/linux-5.19.10/tools/memory-model/litmus-tests/
DMP+onceassign+derefonce.litmus8 * pre-initialization garbage when it traverses an RCU-protected data
/linux-5.19.10/fs/proc/
Dkcore.c259 LIST_HEAD(garbage); in kcore_update_ram()
273 list_splice_tail(&list, &garbage); in kcore_update_ram()
279 list_move(&pos->list, &garbage); in kcore_update_ram()
288 list_for_each_entry_safe(pos, tmp, &garbage, list) { in kcore_update_ram()
/linux-5.19.10/Documentation/litmus-tests/
DREADME30 ensure that an RCU reader will not see pre-initialization garbage.
/linux-5.19.10/arch/arm64/boot/dts/qcom/
Dsc7280-idp.dtsi435 * garbage data when the TX pin of the Bluetooth module is
535 * to prevent BT SoC from receiving garbage during sleep.
545 * garbage data when the TX pin of the Bluetooth module
Dsc7180-idp.dts572 * garbage data when the TX pin of the Bluetooth module is
650 * to prevent BT SoC from receiving garbage during sleep.
659 * garbage data when the TX pin of the Bluetooth module
Dsc7280-qcard.dtsi483 * garbage data when the TX pin of the Bluetooth module is
581 * garbage data when the TX pin of the Bluetooth module
593 * to prevent BT SoC from receiving garbage during sleep.
Dmsm8998-clamshell.dtsi351 * avoid garbage data when the TX pin of the Bluetooth
Dmsm8998-mtp.dtsi406 * avoid garbage data when the TX pin of the Bluetooth
/linux-5.19.10/arch/m68k/fpsp040/
Dx_ovfl.S14 | If the instruction is move_out, then garbage is stored in the
/linux-5.19.10/arch/arc/lib/
Dstrcmp.S74 cmp_s r3,r2 ; ... be independent of trailing garbage
/linux-5.19.10/Documentation/filesystems/
Df2fs.rst105 background_gc=%s Turn on/off cleaning operations, namely garbage
107 idle. If background_gc=on, it will turn on the garbage
108 collection and if background_gc=off, garbage collection
110 on synchronous garbage collection running in background.
111 Default value for this option is on. So garbage
261 run garbage collection to ensure that all available space can
265 avoid additional garbage collection. This can be given as a
329 atgc Enable age-threshold garbage collection, it provides high
723 same as the unit size of garbage collection in FTL. Furthermore, with respect
882 consequently are not needed to be garbage collected. In case the
Daffs.rst186 the bytes 0x00dc..0x00df of block 0 with garbage, thus invalidating
189 Linux will ignore this garbage and recognize the RDB anyway, but
Dnilfs2.rst28 cleaner or garbage collector) are required. Details on the tools are
138 NILFS_IOCTL_CLEAN_SEGMENTS Do garbage collection operation in the
/linux-5.19.10/Documentation/ABI/testing/
Dsysfs-fs-f2fs22 Description: Controls the victim selection policy for garbage collection.
158 Description: Controls migration granularity of garbage collection on large
372 Description: Number of garbage collection operations performed on demand.
378 Description: Number of garbage collection operations triggered in background.
384 Description: Number of blocks moved by garbage collection in foreground.
390 Description: Number of blocks moved by garbage collection in background.
/linux-5.19.10/Documentation/fb/
Dtridentfb.rst62 If in some modes which barely fit the memory you see garbage
/linux-5.19.10/Documentation/process/
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.

123