Home
last modified time | relevance | path

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

123

/linux-2.6.39/arch/alpha/lib/
Dev67-strrchr.S52 lda t5, -1 # E : build garbage mask
55 mskqh t5, a0, t4 # E : Complete garbage mask
57 cmpbge zero, t4, t4 # E : bits set iff byte is garbage
60 andnot t1, t4, t1 # E : clear garbage from null test
61 andnot t3, t4, t3 # E : clear garbage from char test
Dstrrchr.S30 lda t4, -1 # .. e1 : build garbage mask
36 cmpbge zero, t4, t4 # .. e1 : bits set iff byte is garbage
38 andnot t1, t4, t1 # .. e1 : clear garbage from null test
39 andnot t3, t4, t3 # e0 : clear garbage from char test
Dev67-strchr.S39 lda t4, -1 # E : build garbage mask
49 cmpbge zero, t4, t4 # E : bits set iff byte is garbage
57 andnot t0, t4, t0 # E : clear garbage bits
Dstrchr.S26 lda t4, -1 # .. e1 : build garbage mask
32 cmpbge zero, t4, t4 # .. e1 : bits set iff byte is garbage
37 andnot t0, t4, t0 # e0 : clear garbage bits
Dev6-csum_ipv6_magic.S146 zapnot $4,3,$0 # U : clear upper garbage bits
Dstxncpy.S159 mskql t0, a0, t0 # e0 : mask trailing garbage in dst
162 mskqh t1, a0, t1 # e0 : mask leading garbage in src
Dstrncpy_from_user.S145 mskql t0, a0, t0 # e0 : mask trailing garbage in dst
148 mskqh t1, a0, t1 # e0 : mask leading garbage in src
Dev6-strncpy_from_user.S179 mskql t0, a0, t0 # U : mask trailing garbage in dst
183 mskqh t1, a0, t1 # U : mask leading garbage in src
Dev6-stxncpy.S198 mskql t0, a0, t0 # U : mask trailing garbage in dst
202 mskqh t1, a0, t1 # U : mask leading garbage in src (stall)
Dstxcpy.S258 lda t2, -1 # e1 : mask out leading garbage in source
Dev6-stxcpy.S288 lda t2, -1 # E : mask out leading garbage in source
/linux-2.6.39/fs/jffs2/
DREADME.Locking21 the garbage collector will obtain this right at the beginning of
24 garbage collect pass.
53 avoid deadlocks with garbage collection -- the VFS will lock the i_sem
55 allocation may trigger garbage-collection, which may need to move a
57 VFS. If the garbage collection code were to attempt to lock the i_sem
58 of the inode from which it's garbage-collecting a physical node, this
63 mutex, which is obtained by the garbage collection code and also
97 pointer when the garbage collection thread exits. The code to kill the
135 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-2.6.39/drivers/tty/serial/
Dpmac_zilog.h375 #define ZS_CLEARFIFO(port) do { volatile unsigned char garbage; \
376 garbage = read_zsdata(port); \
377 garbage = read_zsdata(port); \
378 garbage = read_zsdata(port); \
/linux-2.6.39/net/unix/
DMakefile7 unix-y := af_unix.o garbage.o
/linux-2.6.39/fs/proc/
Dkcore.c113 LIST_HEAD(garbage); in __kcore_update_ram()
120 list_move(&pos->list, &garbage); in __kcore_update_ram()
124 list_splice(list, &garbage); in __kcore_update_ram()
129 free_kclist_ents(&garbage); in __kcore_update_ram()
/linux-2.6.39/drivers/staging/spectra/
DREADME6 ….c (implement the NAND flash Translation Layer, includs address mapping, garbage collection, wear-…
/linux-2.6.39/arch/m68k/fpsp040/
Dx_ovfl.S14 | If the instruction is move_out, then garbage is stored in the
/linux-2.6.39/fs/logfs/
Dsuper.c609 char *garbage; in logfs_mount() local
610 mtdnr = simple_strtoul(devname+3, &garbage, 0); in logfs_mount()
611 if (*garbage) in logfs_mount()
/linux-2.6.39/arch/powerpc/kvm/
Dpowerpc.c125 int kvm_arch_hardware_enable(void *garbage) in kvm_arch_hardware_enable() argument
130 void kvm_arch_hardware_disable(void *garbage) in kvm_arch_hardware_disable() argument
/linux-2.6.39/Documentation/fb/
Dtridentfb.txt55 If in some modes which barely fit the memory you see garbage
/linux-2.6.39/include/linux/
Dkvm_host.h459 int kvm_arch_hardware_enable(void *garbage);
460 void kvm_arch_hardware_disable(void *garbage);
/linux-2.6.39/arch/s390/kvm/
Dkvm-s390.c78 int kvm_arch_hardware_enable(void *garbage) in kvm_arch_hardware_enable() argument
84 void kvm_arch_hardware_disable(void *garbage) in kvm_arch_hardware_disable() argument
/linux-2.6.39/Documentation/filesystems/
Daffs.txt159 the bytes 0x00dc..0x00df of block 0 with garbage, thus invalidating
162 Linux will ignore this garbage and recognize the RDB anyway, but
/linux-2.6.39/Documentation/RCU/
DRTFP.txt9 [Kung80] recommended use of a garbage collector to defer destruction
11 implementation. This works well in environments that have garbage
12 collectors, but most production garbage collectors incur significant
416 currently referencing. Sort of an inside-out garbage collection

123