Blame view

kernel/linux-imx6_3.14.28/Documentation/ABI/testing/sysfs-kernel-slab 17.1 KB
6b13f685e   김민수   BSP 최초 추가
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
  What:		/sys/kernel/slab
  Date:		May 2007
  KernelVersion:	2.6.22
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The /sys/kernel/slab directory contains a snapshot of the
  		internal state of the SLUB allocator for each cache.  Certain
  		files may be modified to change the behavior of the cache (and
  		any cache it aliases, if any).
  Users:		kernel memory tuning tools
  
  What:		/sys/kernel/slab/cache/aliases
  Date:		May 2007
  KernelVersion:	2.6.22
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The aliases file is read-only and specifies how many caches
  		have merged into this cache.
  
  What:		/sys/kernel/slab/cache/align
  Date:		May 2007
  KernelVersion:	2.6.22
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The align file is read-only and specifies the cache's object
  		alignment in bytes.
  
  What:		/sys/kernel/slab/cache/alloc_calls
  Date:		May 2007
  KernelVersion:	2.6.22
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The alloc_calls file is read-only and lists the kernel code
  		locations from which allocations for this cache were performed.
  		The alloc_calls file only contains information if debugging is
  		enabled for that cache (see Documentation/vm/slub.txt).
  
  What:		/sys/kernel/slab/cache/alloc_fastpath
  Date:		February 2008
  KernelVersion:	2.6.25
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The alloc_fastpath file shows how many objects have been
  		allocated using the fast path.  It can be written to clear the
  		current count.
  		Available when CONFIG_SLUB_STATS is enabled.
  
  What:		/sys/kernel/slab/cache/alloc_from_partial
  Date:		February 2008
  KernelVersion:	2.6.25
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The alloc_from_partial file shows how many times a cpu slab has
  		been full and it has been refilled by using a slab from the list
  		of partially used slabs.  It can be written to clear the current
  		count.
  		Available when CONFIG_SLUB_STATS is enabled.
  
  What:		/sys/kernel/slab/cache/alloc_refill
  Date:		February 2008
  KernelVersion:	2.6.25
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The alloc_refill file shows how many times the per-cpu freelist
  		was empty but there were objects available as the result of
  		remote cpu frees.  It can be written to clear the current count.
  		Available when CONFIG_SLUB_STATS is enabled.
  
  What:		/sys/kernel/slab/cache/alloc_slab
  Date:		February 2008
  KernelVersion:	2.6.25
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The alloc_slab file is shows how many times a new slab had to
  		be allocated from the page allocator.  It can be written to
  		clear the current count.
  		Available when CONFIG_SLUB_STATS is enabled.
  
  What:		/sys/kernel/slab/cache/alloc_slowpath
  Date:		February 2008
  KernelVersion:	2.6.25
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The alloc_slowpath file shows how many objects have been
  		allocated using the slow path because of a refill or
  		allocation from a partial or new slab.  It can be written to
  		clear the current count.
  		Available when CONFIG_SLUB_STATS is enabled.
  
  What:		/sys/kernel/slab/cache/cache_dma
  Date:		May 2007
  KernelVersion:	2.6.22
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The cache_dma file is read-only and specifies whether objects
  		are from ZONE_DMA.
  		Available when CONFIG_ZONE_DMA is enabled.
  
  What:		/sys/kernel/slab/cache/cpu_slabs
  Date:		May 2007
  KernelVersion:	2.6.22
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The cpu_slabs file is read-only and displays how many cpu slabs
  		are active and their NUMA locality.
  
  What:		/sys/kernel/slab/cache/cpuslab_flush
  Date:		April 2009
  KernelVersion:	2.6.31
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The file cpuslab_flush shows how many times a cache's cpu slabs
  		have been flushed as the result of destroying or shrinking a
  		cache, a cpu going offline, or as the result of forcing an
  		allocation from a certain node.  It can be written to clear the
  		current count.
  		Available when CONFIG_SLUB_STATS is enabled.
  
  What:		/sys/kernel/slab/cache/ctor
  Date:		May 2007
  KernelVersion:	2.6.22
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The ctor file is read-only and specifies the cache's object
  		constructor function, which is invoked for each object when a
  		new slab is allocated.
  
  What:		/sys/kernel/slab/cache/deactivate_empty
  Date:		February 2008
  KernelVersion:	2.6.25
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The deactivate_empty file shows how many times an empty cpu slab
  		was deactivated.  It can be written to clear the current count.
  		Available when CONFIG_SLUB_STATS is enabled.
  
  What:		/sys/kernel/slab/cache/deactivate_full
  Date:		February 2008
  KernelVersion:	2.6.25
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The deactivate_full file shows how many times a full cpu slab
  		was deactivated.  It can be written to clear the current count.
  		Available when CONFIG_SLUB_STATS is enabled.
  
  What:		/sys/kernel/slab/cache/deactivate_remote_frees
  Date:		February 2008
  KernelVersion:	2.6.25
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The deactivate_remote_frees file shows how many times a cpu slab
  		has been deactivated and contained free objects that were freed
  		remotely.  It can be written to clear the current count.
  		Available when CONFIG_SLUB_STATS is enabled.
  
  What:		/sys/kernel/slab/cache/deactivate_to_head
  Date:		February 2008
  KernelVersion:	2.6.25
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The deactivate_to_head file shows how many times a partial cpu
  		slab was deactivated and added to the head of its node's partial
  		list.  It can be written to clear the current count.
  		Available when CONFIG_SLUB_STATS is enabled.
  
  What:		/sys/kernel/slab/cache/deactivate_to_tail
  Date:		February 2008
  KernelVersion:	2.6.25
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The deactivate_to_tail file shows how many times a partial cpu
  		slab was deactivated and added to the tail of its node's partial
  		list.  It can be written to clear the current count.
  		Available when CONFIG_SLUB_STATS is enabled.
  
  What:		/sys/kernel/slab/cache/destroy_by_rcu
  Date:		May 2007
  KernelVersion:	2.6.22
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The destroy_by_rcu file is read-only and specifies whether
  		slabs (not objects) are freed by rcu.
  
  What:		/sys/kernel/slab/cache/free_add_partial
  Date:		February 2008
  KernelVersion:	2.6.25
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The free_add_partial file shows how many times an object has
  		been freed in a full slab so that it had to added to its node's
  		partial list.  It can be written to clear the current count.
  		Available when CONFIG_SLUB_STATS is enabled.
  
  What:		/sys/kernel/slab/cache/free_calls
  Date:		May 2007
  KernelVersion:	2.6.22
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The free_calls file is read-only and lists the locations of
  		object frees if slab debugging is enabled (see
  		Documentation/vm/slub.txt).
  
  What:		/sys/kernel/slab/cache/free_fastpath
  Date:		February 2008
  KernelVersion:	2.6.25
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The free_fastpath file shows how many objects have been freed
  		using the fast path because it was an object from the cpu slab.
  		It can be written to clear the current count.
  		Available when CONFIG_SLUB_STATS is enabled.
  
  What:		/sys/kernel/slab/cache/free_frozen
  Date:		February 2008
  KernelVersion:	2.6.25
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The free_frozen file shows how many objects have been freed to
  		a frozen slab (i.e. a remote cpu slab).  It can be written to
  		clear the current count.
  		Available when CONFIG_SLUB_STATS is enabled.
  
  What:		/sys/kernel/slab/cache/free_remove_partial
  Date:		February 2008
  KernelVersion:	2.6.25
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The free_remove_partial file shows how many times an object has
  		been freed to a now-empty slab so that it had to be removed from
  		its node's partial list.  It can be written to clear the current
  		count.
  		Available when CONFIG_SLUB_STATS is enabled.
  
  What:		/sys/kernel/slab/cache/free_slab
  Date:		February 2008
  KernelVersion:	2.6.25
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The free_slab file shows how many times an empty slab has been
  		freed back to the page allocator.  It can be written to clear
  		the current count.
  		Available when CONFIG_SLUB_STATS is enabled.
  
  What:		/sys/kernel/slab/cache/free_slowpath
  Date:		February 2008
  KernelVersion:	2.6.25
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The free_slowpath file shows how many objects have been freed
  		using the slow path (i.e. to a full or partial slab).  It can
  		be written to clear the current count.
  		Available when CONFIG_SLUB_STATS is enabled.
  
  What:		/sys/kernel/slab/cache/hwcache_align
  Date:		May 2007
  KernelVersion:	2.6.22
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The hwcache_align file is read-only and specifies whether
  		objects are aligned on cachelines.
  
  What:		/sys/kernel/slab/cache/min_partial
  Date:		February 2009
  KernelVersion:	2.6.30
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		David Rientjes <rientjes@google.com>
  Description:
  		The min_partial file specifies how many empty slabs shall
  		remain on a node's partial list to avoid the overhead of
  		allocating new slabs.  Such slabs may be reclaimed by utilizing
  		the shrink file.
  
  What:		/sys/kernel/slab/cache/object_size
  Date:		May 2007
  KernelVersion:	2.6.22
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The object_size file is read-only and specifies the cache's
  		object size.
  
  What:		/sys/kernel/slab/cache/objects
  Date:		May 2007
  KernelVersion:	2.6.22
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The objects file is read-only and displays how many objects are
  		active and from which nodes they are from.
  
  What:		/sys/kernel/slab/cache/objects_partial
  Date:		April 2008
  KernelVersion:	2.6.26
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The objects_partial file is read-only and displays how many
  		objects are on partial slabs and from which nodes they are
  		from.
  
  What:		/sys/kernel/slab/cache/objs_per_slab
  Date:		May 2007
  KernelVersion:	2.6.22
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The file objs_per_slab is read-only and specifies how many
  		objects may be allocated from a single slab of the order
  		specified in /sys/kernel/slab/cache/order.
  
  What:		/sys/kernel/slab/cache/order
  Date:		May 2007
  KernelVersion:	2.6.22
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The order file specifies the page order at which new slabs are
  		allocated.  It is writable and can be changed to increase the
  		number of objects per slab.  If a slab cannot be allocated
  		because of fragmentation, SLUB will retry with the minimum order
  		possible depending on its characteristics.
  		When debug_guardpage_minorder=N (N > 0) parameter is specified
  		(see Documentation/kernel-parameters.txt), the minimum possible
  		order is used and this sysfs entry can not be used to change
  		the order at run time.
  
  What:		/sys/kernel/slab/cache/order_fallback
  Date:		April 2008
  KernelVersion:	2.6.26
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The order_fallback file shows how many times an allocation of a
  		new slab has not been possible at the cache's order and instead
  		fallen back to its minimum possible order.  It can be written to
  		clear the current count.
  		Available when CONFIG_SLUB_STATS is enabled.
  
  What:		/sys/kernel/slab/cache/partial
  Date:		May 2007
  KernelVersion:	2.6.22
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The partial file is read-only and displays how long many
  		partial slabs there are and how long each node's list is.
  
  What:		/sys/kernel/slab/cache/poison
  Date:		May 2007
  KernelVersion:	2.6.22
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The poison file specifies whether objects should be poisoned
  		when a new slab is allocated.
  
  What:		/sys/kernel/slab/cache/reclaim_account
  Date:		May 2007
  KernelVersion:	2.6.22
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The reclaim_account file specifies whether the cache's objects
  		are reclaimable (and grouped by their mobility).
  
  What:		/sys/kernel/slab/cache/red_zone
  Date:		May 2007
  KernelVersion:	2.6.22
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The red_zone file specifies whether the cache's objects are red
  		zoned.
  
  What:		/sys/kernel/slab/cache/remote_node_defrag_ratio
  Date:		January 2008
  KernelVersion:	2.6.25
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The file remote_node_defrag_ratio specifies the percentage of
  		times SLUB will attempt to refill the cpu slab with a partial
  		slab from a remote node as opposed to allocating a new slab on
  		the local node.  This reduces the amount of wasted memory over
  		the entire system but can be expensive.
  		Available when CONFIG_NUMA is enabled.
  
  What:		/sys/kernel/slab/cache/sanity_checks
  Date:		May 2007
  KernelVersion:	2.6.22
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The sanity_checks file specifies whether expensive checks
  		should be performed on free and, at minimum, enables double free
  		checks.  Caches that enable sanity_checks cannot be merged with
  		caches that do not.
  
  What:		/sys/kernel/slab/cache/shrink
  Date:		May 2007
  KernelVersion:	2.6.22
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The shrink file is written when memory should be reclaimed from
  		a cache.  Empty partial slabs are freed and the partial list is
  		sorted so the slabs with the fewest available objects are used
  		first.
  
  What:		/sys/kernel/slab/cache/slab_size
  Date:		May 2007
  KernelVersion:	2.6.22
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The slab_size file is read-only and specifies the object size
  		with metadata (debugging information and alignment) in bytes.
  
  What:		/sys/kernel/slab/cache/slabs
  Date:		May 2007
  KernelVersion:	2.6.22
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The slabs file is read-only and displays how long many slabs
  		there are (both cpu and partial) and from which nodes they are
  		from.
  
  What:		/sys/kernel/slab/cache/store_user
  Date:		May 2007
  KernelVersion:	2.6.22
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The store_user file specifies whether the location of
  		allocation or free should be tracked for a cache.
  
  What:		/sys/kernel/slab/cache/total_objects
  Date:		April 2008
  KernelVersion:	2.6.26
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The total_objects file is read-only and displays how many total
  		objects a cache has and from which nodes they are from.
  
  What:		/sys/kernel/slab/cache/trace
  Date:		May 2007
  KernelVersion:	2.6.22
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		The trace file specifies whether object allocations and frees
  		should be traced.
  
  What:		/sys/kernel/slab/cache/validate
  Date:		May 2007
  KernelVersion:	2.6.22
  Contact:	Pekka Enberg <penberg@cs.helsinki.fi>,
  		Christoph Lameter <cl@linux-foundation.org>
  Description:
  		Writing to the validate file causes SLUB to traverse all of its
  		cache's objects and check the validity of metadata.