intel_pstate: fix PCT_TO_HWP macro
[linux-2.6-block.git] / drivers / staging / lustre / sysfs-fs-lustre
1 What:           /sys/fs/lustre/version
2 Date:           May 2015
3 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
4 Description:
5                 Shows current running lustre version.
6
7 What:           /sys/fs/lustre/pinger
8 Date:           May 2015
9 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
10 Description:
11                 Shows if the lustre module has pinger support.
12                 "on" means yes and "off" means no.
13
14 What:           /sys/fs/lustre/health
15 Date:           May 2015
16 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
17 Description:
18                 Shows whenever current system state believed to be "healthy",
19                 "NOT HEALTHY", or "LBUG" whenever lustre has experienced
20                 an internal assertion failure
21
22 What:           /sys/fs/lustre/jobid_name
23 Date:           May 2015
24 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
25 Description:
26                 Currently running job "name" for this node to be transferred
27                 to Lustre servers for purposes of QoS and statistics gathering.
28                 Writing into this file will change the name, reading outputs
29                 currently set value.
30
31 What:           /sys/fs/lustre/jobid_var
32 Date:           May 2015
33 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
34 Description:
35                 Control file for lustre "jobstats" functionality, write new
36                 value from the list below to change the mode:
37                 disable - disable job name reporting to the servers (default)
38                 procname_uid - form the job name as the current running
39                                command name and pid with a dot in between
40                                e.g. dd.1253
41                 nodelocal - use jobid_name value from above.
42
43 What:           /sys/fs/lustre/llite/<fsname>-<uuid>/blocksize
44 Date:           May 2015
45 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
46 Description:
47                 Biggest blocksize on object storage server for this filesystem.
48
49 What:           /sys/fs/lustre/llite/<fsname>-<uuid>/kbytestotal
50 Date:           May 2015
51 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
52 Description:
53                 Shows total number of kilobytes of space on this filesystem
54
55 What:           /sys/fs/lustre/llite/<fsname>-<uuid>/kbytesfree
56 Date:           May 2015
57 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
58 Description:
59                 Shows total number of free kilobytes of space on this filesystem
60
61 What:           /sys/fs/lustre/llite/<fsname>-<uuid>/kbytesavail
62 Date:           May 2015
63 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
64 Description:
65                 Shows total number of free kilobytes of space on this filesystem
66                 actually available for use (taking into account per-client
67                 grants and filesystem reservations).
68
69 What:           /sys/fs/lustre/llite/<fsname>-<uuid>/filestotal
70 Date:           May 2015
71 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
72 Description:
73                 Shows total number of inodes on the filesystem.
74
75 What:           /sys/fs/lustre/llite/<fsname>-<uuid>/filesfree
76 Date:           May 2015
77 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
78 Description:
79                 Shows estimated number of free inodes on the filesystem
80
81 What:           /sys/fs/lustre/llite/<fsname>-<uuid>/client_type
82 Date:           May 2015
83 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
84 Description:
85                 Shows whenever this filesystem considers this client to be
86                 compute cluster-local or remote. Remote clients have
87                 additional uid/gid convrting logic applied.
88
89 What:           /sys/fs/lustre/llite/<fsname>-<uuid>/fstype
90 Date:           May 2015
91 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
92 Description:
93                 Shows filesystem type of the filesystem
94
95 What:           /sys/fs/lustre/llite/<fsname>-<uuid>/uuid
96 Date:           May 2015
97 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
98 Description:
99                 Shows this filesystem superblock uuid
100
101 What:           /sys/fs/lustre/llite/<fsname>-<uuid>/max_read_ahead_mb
102 Date:           May 2015
103 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
104 Description:
105                 Sets maximum number of megabytes in system memory to be
106                 given to read-ahead cache.
107
108 What:           /sys/fs/lustre/llite/<fsname>-<uuid>/max_read_ahead_per_file_mb
109 Date:           May 2015
110 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
111 Description:
112                 Sets maximum number of megabytes to read-ahead for a single file
113
114 What:           /sys/fs/lustre/llite/<fsname>-<uuid>/max_read_ahead_whole_mb
115 Date:           May 2015
116 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
117 Description:
118                 For small reads, how many megabytes to actually request from
119                 the server as initial read-ahead.
120
121 What:           /sys/fs/lustre/llite/<fsname>-<uuid>/checksum_pages
122 Date:           May 2015
123 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
124 Description:
125                 Enables or disables per-page checksum at llite layer, before
126                 the pages are actually given to lower level for network transfer
127
128 What:           /sys/fs/lustre/llite/<fsname>-<uuid>/stats_track_pid
129 Date:           May 2015
130 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
131 Description:
132                 Limit Lustre vfs operations gathering to just a single pid.
133                 0 to track everything.
134
135 What:           /sys/fs/lustre/llite/<fsname>-<uuid>/stats_track_ppid
136 Date:           May 2015
137 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
138 Description:
139                 Limit Lustre vfs operations gathering to just a single ppid.
140                 0 to track everything.
141
142 What:           /sys/fs/lustre/llite/<fsname>-<uuid>/stats_track_gid
143 Date:           May 2015
144 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
145 Description:
146                 Limit Lustre vfs operations gathering to just a single gid.
147                 0 to track everything.
148
149 What:           /sys/fs/lustre/llite/<fsname>-<uuid>/statahead_max
150 Date:           May 2015
151 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
152 Description:
153                 Controls maximum number of statahead requests to send when
154                 sequential readdir+stat pattern is detected.
155
156 What:           /sys/fs/lustre/llite/<fsname>-<uuid>/statahead_agl
157 Date:           May 2015
158 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
159 Description:
160                 Controls if AGL (async glimpse ahead - obtain object information
161                 from OSTs in parallel with MDS during statahead) should be
162                 enabled or disabled.
163                 0 to disable, 1 to enable.
164
165 What:           /sys/fs/lustre/llite/<fsname>-<uuid>/lazystatfs
166 Date:           May 2015
167 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
168 Description:
169                 Controls statfs(2) behaviour in the face of down servers.
170                 If 0, always wait for all servers to come online,
171                 if 1, ignote inactive servers.
172
173 What:           /sys/fs/lustre/llite/<fsname>-<uuid>/max_easize
174 Date:           May 2015
175 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
176 Description:
177                 Shows maximum number of bytes file striping data could be
178                 in current configuration of storage.
179
180 What:           /sys/fs/lustre/llite/<fsname>-<uuid>/default_easize
181 Date:           May 2015
182 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
183 Description:
184                 Shows maximum observed file striping data seen by this
185                 filesystem client instance.
186
187 What:           /sys/fs/lustre/llite/<fsname>-<uuid>/xattr_cache
188 Date:           May 2015
189 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
190 Description:
191                 Controls extended attributes client-side cache.
192                 1 to enable, 0 to disable.
193
194 What:           /sys/fs/lustre/ldlm/cancel_unused_locks_before_replay
195 Date:           May 2015
196 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
197 Description:
198                 Controls if client should replay unused locks during recovery
199                 If a client tends to have a lot of unused locks in LRU,
200                 recovery times might become prolonged.
201                 1 - just locally cancel unused locks (default)
202                 0 - replay unused locks.
203
204 What:           /sys/fs/lustre/ldlm/namespaces/<name>/resource_count
205 Date:           May 2015
206 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
207 Description:
208                 Displays number of lock resources (objects on which individual
209                 locks are taken) currently allocated in this namespace.
210
211 What:           /sys/fs/lustre/ldlm/namespaces/<name>/lock_count
212 Date:           May 2015
213 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
214 Description:
215                 Displays number or locks allocated in this namespace.
216
217 What:           /sys/fs/lustre/ldlm/namespaces/<name>/lru_size
218 Date:           May 2015
219 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
220 Description:
221                 Controls and displays LRU size limit for unused locks for this
222                 namespace.
223                 0 - LRU size is unlimited, controlled by server resources
224                 positive number - number of locks to allow in lock LRU list
225
226 What:           /sys/fs/lustre/ldlm/namespaces/<name>/lock_unused_count
227 Date:           May 2015
228 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
229 Description:
230                 Display number of locks currently sitting in the LRU list
231                 of this namespace
232
233 What:           /sys/fs/lustre/ldlm/namespaces/<name>/lru_max_age
234 Date:           May 2015
235 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
236 Description:
237                 Maximum number of milliseconds a lock could sit in LRU list
238                 before client would voluntarily cancel it as unused.
239
240 What:           /sys/fs/lustre/ldlm/namespaces/<name>/early_lock_cancel
241 Date:           May 2015
242 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
243 Description:
244                 Controls "early lock cancellation" feature on this namespace
245                 if supported by the server.
246                 When enabled, tries to preemtively cancel locks that would be
247                 cancelled by verious operations and bundle the cancellation
248                 requests in the same RPC as the main operation, which results
249                 in significant speedups due to reduced lock-pingpong RPCs.
250                 0 - disabled
251                 1 - enabled (default)
252
253 What:           /sys/fs/lustre/ldlm/namespaces/<name>/pool/granted
254 Date:           May 2015
255 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
256 Description:
257                 Displays number of granted locks in this namespace
258
259 What:           /sys/fs/lustre/ldlm/namespaces/<name>/pool/grant_rate
260 Date:           May 2015
261 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
262 Description:
263                 Number of granted locks in this namespace during last
264                 time interval
265
266 What:           /sys/fs/lustre/ldlm/namespaces/<name>/pool/cancel_rate
267 Date:           May 2015
268 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
269 Description:
270                 Number of lock cancellations in this namespace during
271                 last time interval
272
273 What:           /sys/fs/lustre/ldlm/namespaces/<name>/pool/grant_speed
274 Date:           May 2015
275 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
276 Description:
277                 Calculated speed of lock granting (grant_rate - cancel_rate)
278                 in this namespace
279
280 What:           /sys/fs/lustre/ldlm/namespaces/<name>/pool/grant_plan
281 Date:           May 2015
282 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
283 Description:
284                 Estimated number of locks to be granted in the next time
285                 interval in this namespace
286
287 What:           /sys/fs/lustre/ldlm/namespaces/<name>/pool/limit
288 Date:           May 2015
289 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
290 Description:
291                 Controls number of allowed locks in this pool.
292                 When lru_size is 0, this is the actual limit then.
293
294 What:           /sys/fs/lustre/ldlm/namespaces/<name>/pool/lock_volume_factor
295 Date:           May 2015
296 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
297 Description:
298                 Multiplier for all lock volume calculations above.
299                 Default is 1. Increase to make the client to more agressively
300                 clean it's lock LRU list for this namespace.
301
302 What:           /sys/fs/lustre/ldlm/namespaces/<name>/pool/server_lock_volume
303 Date:           May 2015
304 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
305 Description:
306                 Calculated server lock volume.
307
308 What:           /sys/fs/lustre/ldlm/namespaces/<name>/pool/recalc_period
309 Date:           May 2015
310 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
311 Description:
312                 Controls length of time between recalculation of above
313                 values (in seconds).
314
315 What:           /sys/fs/lustre/ldlm/services/ldlm_cbd/threads_min
316 Date:           May 2015
317 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
318 Description:
319                 Controls minimum number of ldlm callback threads to start.
320
321 What:           /sys/fs/lustre/ldlm/services/ldlm_cbd/threads_max
322 Date:           May 2015
323 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
324 Description:
325                 Controls maximum number of ldlm callback threads to start.
326
327 What:           /sys/fs/lustre/ldlm/services/ldlm_cbd/threads_started
328 Date:           May 2015
329 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
330 Description:
331                 Shows actual number of ldlm callback threads running.
332
333 What:           /sys/fs/lustre/ldlm/services/ldlm_cbd/high_priority_ratio
334 Date:           May 2015
335 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
336 Description:
337                 Controls what percentage of ldlm callback threads is dedicated
338                 to "high priority" incoming requests.
339
340 What:           /sys/fs/lustre/{obdtype}/{connection_name}/blocksize
341 Date:           May 2015
342 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
343 Description:
344                 Blocksize on backend filesystem for service behind this obd
345                 device (or biggest blocksize for compound devices like lov
346                 and lmv)
347
348 What:           /sys/fs/lustre/{obdtype}/{connection_name}/kbytestotal
349 Date:           May 2015
350 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
351 Description:
352                 Total number of kilobytes of space on backend filesystem
353                 for service behind this obd (or total amount for compound
354                 devices like lov lmv)
355
356 What:           /sys/fs/lustre/{obdtype}/{connection_name}/kbytesfree
357 Date:           May 2015
358 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
359 Description:
360                 Number of free kilobytes on backend filesystem for service
361                 behind this obd (or total amount for compound devices
362                 like lov lmv)
363
364 What:           /sys/fs/lustre/{obdtype}/{connection_name}/kbytesavail
365 Date:           May 2015
366 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
367 Description:
368                 Number of kilobytes of free space on backend filesystem
369                 for service behind this obd (or total amount for compound
370                 devices like lov lmv) that is actually available for use
371                 (taking into account per-client and filesystem reservations).
372
373 What:           /sys/fs/lustre/{obdtype}/{connection_name}/filestotal
374 Date:           May 2015
375 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
376 Description:
377                 Number of inodes on backend filesystem for service behind this
378                 obd.
379
380 What:           /sys/fs/lustre/{obdtype}/{connection_name}/filesfree
381 Date:           May 2015
382 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
383 Description:
384                 Number of free inodes on backend filesystem for service
385                 behind this obd.
386
387 What:           /sys/fs/lustre/mdc/{connection_name}/max_pages_per_rpc
388 Date:           May 2015
389 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
390 Description:
391                 Maximum number of readdir pages to fit into a single readdir
392                 RPC.
393
394 What:           /sys/fs/lustre/{mdc,osc}/{connection_name}/max_rpcs_in_flight
395 Date:           May 2015
396 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
397 Description:
398                 Maximum number of parallel RPCs on the wire to allow on
399                 this connection. Increasing this number would help on higher
400                 latency links, but has a chance of overloading a server
401                 if you have too many clients like this.
402                 Default: 8
403
404 What:           /sys/fs/lustre/osc/{connection_name}/max_pages_per_rpc
405 Date:           May 2015
406 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
407 Description:
408                 Maximum number of pages to fit into a single RPC.
409                 Typically bigger RPCs allow for better performance.
410                 Default: however many pages to form 1M of data (256 pages
411                 for 4K page sized platforms)
412
413 What:           /sys/fs/lustre/osc/{connection_name}/active
414 Date:           May 2015
415 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
416 Description:
417                 Controls accessibility of this connection. If set to 0,
418                 fail all accesses immediately.
419
420 What:           /sys/fs/lustre/osc/{connection_name}/checksums
421 Date:           May 2015
422 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
423 Description:
424                 Controls whenever to checksum bulk RPC data over the wire
425                 to this target.
426                 1: enable (default) ; 0: disable
427
428 What:           /sys/fs/lustre/osc/{connection_name}/contention_seconds
429 Date:           May 2015
430 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
431 Description:
432                 Controls for how long to consider a file contended once
433                 indicated as such by the server.
434                 When a file is considered contended, all operations switch to
435                 synchronous lockless mode to avoid cache and lock pingpong.
436
437 What:           /sys/fs/lustre/osc/{connection_name}/cur_dirty_bytes
438 Date:           May 2015
439 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
440 Description:
441                 Displays how many dirty bytes is presently in the cache for this
442                 target.
443
444 What:           /sys/fs/lustre/osc/{connection_name}/cur_grant_bytes
445 Date:           May 2015
446 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
447 Description:
448                 Shows how many bytes we have as a "dirty cache" grant from the
449                 server. Writing a value smaller than shown allows to release
450                 some grant back to the server.
451                 Dirty cache grant is a way Lustre ensures that cached successful
452                 writes on client do not end up discarded by the server due to
453                 lack of space later on.
454
455 What:           /sys/fs/lustre/osc/{connection_name}/cur_lost_grant_bytes
456 Date:           May 2015
457 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
458 Description:
459                 Shows how many granted bytes were released to the server due
460                 to lack of write activity on this client.
461
462 What:           /sys/fs/lustre/osc/{connection_name}/grant_shrink_interval
463 Date:           May 2015
464 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
465 Description:
466                 Number of seconds with no write activity for this target
467                 to start releasing dirty grant back to the server.
468
469 What:           /sys/fs/lustre/osc/{connection_name}/destroys_in_flight
470 Date:           May 2015
471 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
472 Description:
473                 Number of DESTROY RPCs currently in flight to this target.
474
475 What:           /sys/fs/lustre/osc/{connection_name}/lockless_truncate
476 Date:           May 2015
477 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
478 Description:
479                 Controls whether lockless truncate RPCs are allowed to this
480                 target.
481                 Lockless truncate causes server to perform the locking which
482                 is beneficial if the truncate is not followed by a write
483                 immediately.
484                 1: enable ; 0: disable (default)
485
486 What:           /sys/fs/lustre/osc/{connection_name}/max_dirty_mb
487 Date:           May 2015
488 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
489 Description:
490                 Controls how much dirty data this client can accumulate
491                 for this target. This is orthogonal to dirty grant and is
492                 a hard limit even if the server would allow a bigger dirty
493                 cache.
494                 While allowing higher dirty cache is beneficial for write
495                 performance, flushing write cache takes longer and as such
496                 the node might be more prone to OOMs.
497                 Having this value set too low might result in not being able
498                 to sent too many parallel WRITE RPCs.
499                 Default: 32
500
501 What:           /sys/fs/lustre/osc/{connection_name}/resend_count
502 Date:           May 2015
503 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
504 Description:
505                 Controls how many times to try and resend RPCs to this target
506                 that failed with "recoverable" status, such as EAGAIN,
507                 ENOMEM.
508
509 What:           /sys/fs/lustre/lov/{connection_name}/numobd
510 Date:           May 2015
511 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
512 Description:
513                 Number of OSC targets managed by this LOV instance.
514
515 What:           /sys/fs/lustre/lov/{connection_name}/activeobd
516 Date:           May 2015
517 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
518 Description:
519                 Number of OSC targets managed by this LOV instance that are
520                 actually active.
521
522 What:           /sys/fs/lustre/lmv/{connection_name}/numobd
523 Date:           May 2015
524 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
525 Description:
526                 Number of MDC targets managed by this LMV instance.
527
528 What:           /sys/fs/lustre/lmv/{connection_name}/activeobd
529 Date:           May 2015
530 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
531 Description:
532                 Number of MDC targets managed by this LMV instance that are
533                 actually active.
534
535 What:           /sys/fs/lustre/lmv/{connection_name}/placement
536 Date:           May 2015
537 Contact:        "Oleg Drokin" <oleg.drokin@intel.com>
538 Description:
539                 Determines policy of inode placement in case of multiple
540                 metadata servers:
541                 CHAR - based on a hash of the file name used at creation time
542                        (Default)
543                 NID - based on a hash of creating client network id.