246
247 Page unmapping event. This probe marks the unmapping of a file system
248 page from the system.
249
250 vnode and offset
251 Identifies the file and offset of the page being
252 unmapped.
253
254
255 Pageins and Pageouts
256 pagein
257 tnf_opaque vnode
258 tnf_offset offset
259 tnf_size size
260
261
262
263 Pagein start event. This event signals the initiation of pagein I/O.
264
265 vnodeandoffset
266 Identifyies the file and offset to be paged in.
267
268
269 size
270 Specifies the number of bytes to be paged in.
271
272
273 pageout
274 tnf_opaque vnode
275 tnf_ulong pages_pageout
276 tnf_ulong pages_freed
277 tnf_ulong pages_reclaimed
278
279
280
281 Pageout completion event. This event signals the completion of pageout
282 I/O.
283
284 vnode
285 Identifies the file of the pageout request.
286
457
458
459 block
460 The logical block number accessed on the device.
461
462
463 buf
464 The kernel address of the buf(9S) structure associated with
465 the transfer.
466
467
468 physio_start
469 tnf_device device
470 tnf_offset offset
471 tnf_size size
472 tnf_bioflags rw
473
474
475
476 Raw I/O start event. This event marks entry into the physio(9F)
477 fufnction which performs unbuffered I/O.
478
479 device
480 Contains the major and minor numbers of the device of the
481 transfer.
482
483
484 offset
485 The logical offset on the device for the transfer.
486
487
488 size
489 The number of bytes to be transferred.
490
491
492 rw
493 The direction of the transfer: read or write (see buf(9S)).
494
495
496 physio_end
497 tnf_device device
498
499
500
501 Raw I/O end event. This event marks exit from the physio(9F)
502 fufnction.
503
504 device
505 The major and minor numbers of the device of the transfer.
506
507
508 USAGE
509 Use the prex utility to control kernel probes. The standard prex
510 commands to list and manipulate probes are available to you, along with
511 commands to set up and manage kernel tracing.
512
513
514 Kernel probes write trace records into a kernel trace buffer. You must
515 copy the buffer into a TNF file for post-processing; use the tnfxtract
516 utility for this.
517
518
519 You use the tnfdump utility to examine a kernel trace file. This is
520 exactly the same as examining a user-level trace file.
521
522
536
537 7. Extract the kernel trace buffer (tnfxtract).
538
539 8. Disable all probes (prex).
540
541 9. Deallocate the kernel trace buffer (prex).
542
543 10. Examine the trace file (tnfdump).
544
545
546 A convenient way to follow these steps is to use two shell windows; run
547 an interactive prex session in one, and run your application and
548 tnfxtract in the other.
549
550 SEE ALSO
551 prex(1), tnfdump(1), tnfxtract(1), libtnfctl(3TNF), TNF_PROBE(3TNF),
552 tracing(3TNF), strategy(9E), biodone(9F), physio(9F), buf(9S)
553
554
555
556 November 8, 1999 TNF_KERNEL_PROBES(4)
|
246
247 Page unmapping event. This probe marks the unmapping of a file system
248 page from the system.
249
250 vnode and offset
251 Identifies the file and offset of the page being
252 unmapped.
253
254
255 Pageins and Pageouts
256 pagein
257 tnf_opaque vnode
258 tnf_offset offset
259 tnf_size size
260
261
262
263 Pagein start event. This event signals the initiation of pagein I/O.
264
265 vnodeandoffset
266 Identifies the file and offset to be paged in.
267
268
269 size
270 Specifies the number of bytes to be paged in.
271
272
273 pageout
274 tnf_opaque vnode
275 tnf_ulong pages_pageout
276 tnf_ulong pages_freed
277 tnf_ulong pages_reclaimed
278
279
280
281 Pageout completion event. This event signals the completion of pageout
282 I/O.
283
284 vnode
285 Identifies the file of the pageout request.
286
457
458
459 block
460 The logical block number accessed on the device.
461
462
463 buf
464 The kernel address of the buf(9S) structure associated with
465 the transfer.
466
467
468 physio_start
469 tnf_device device
470 tnf_offset offset
471 tnf_size size
472 tnf_bioflags rw
473
474
475
476 Raw I/O start event. This event marks entry into the physio(9F)
477 function which performs unbuffered I/O.
478
479 device
480 Contains the major and minor numbers of the device of the
481 transfer.
482
483
484 offset
485 The logical offset on the device for the transfer.
486
487
488 size
489 The number of bytes to be transferred.
490
491
492 rw
493 The direction of the transfer: read or write (see buf(9S)).
494
495
496 physio_end
497 tnf_device device
498
499
500
501 Raw I/O end event. This event marks exit from the physio(9F) function.
502
503 device
504 The major and minor numbers of the device of the transfer.
505
506
507 USAGE
508 Use the prex utility to control kernel probes. The standard prex
509 commands to list and manipulate probes are available to you, along with
510 commands to set up and manage kernel tracing.
511
512
513 Kernel probes write trace records into a kernel trace buffer. You must
514 copy the buffer into a TNF file for post-processing; use the tnfxtract
515 utility for this.
516
517
518 You use the tnfdump utility to examine a kernel trace file. This is
519 exactly the same as examining a user-level trace file.
520
521
535
536 7. Extract the kernel trace buffer (tnfxtract).
537
538 8. Disable all probes (prex).
539
540 9. Deallocate the kernel trace buffer (prex).
541
542 10. Examine the trace file (tnfdump).
543
544
545 A convenient way to follow these steps is to use two shell windows; run
546 an interactive prex session in one, and run your application and
547 tnfxtract in the other.
548
549 SEE ALSO
550 prex(1), tnfdump(1), tnfxtract(1), libtnfctl(3TNF), TNF_PROBE(3TNF),
551 tracing(3TNF), strategy(9E), biodone(9F), physio(9F), buf(9S)
552
553
554
555 May 16, 2020 TNF_KERNEL_PROBES(4)
|