Lines Matching refs:objects

103  (5) Cookies are used to represent indices, files and other objects to the
130 FS-Cache maintains a virtual indexing tree in which all indices, files, objects
164      indexed by NFS file handles to get data file objects.  Each data file
165      objects can have an array of pages, but may also have further child
166      objects, such as extended attributes and directory entries.  Extended
167      attribute objects themselves have page-array contents.
172      Each of these contains vnode data file objects, each of which contains an
218 	Objects	alc=N	Number of objects allocated
220 		avl=N	Number of objects that reached the available state
221 		ded=N	Number of objects that reached the dead state
222 	ChkAux	non=N	Number of objects that didn't have a coherency check
223 		ok=N	Number of objects that passed a coherency check
224 		upd=N	Number of objects that needed a coherency data update
225 		obs=N	Number of objects that were declared obsolete
237 		crt=N	Number of objects created by lookup
336 list of all the objects currently allocated and allow them to be viewed
339 	/proc/fs/fscache/objects
343 	[root@andromeda ~]# head /proc/fs/fscache/objects
356 	CHLDN	Number of child objects of this object
390 	C	Show objects that have a cookie
391 	c	Show objects that don't have a cookie
392 	B	Show objects that are busy
393 	b	Show objects that aren't busy
394 	W	Show objects that have pending writes
395 	w	Show objects that don't have pending writes
396 	R	Show objects that have outstanding reads
397 	r	Show objects that don't have outstanding reads
398 	S	Show objects that have work queued
399 	s	Show objects that don't have work queued
405 shows objects that are busy, and lists their object keys, but does not dump
409 By default all objects and all fields will be shown.