From 04047077d5ee9c270f328392b021d8de4d2d4657 Mon Sep 17 00:00:00 2001 From: guanglei Date: Wed, 18 Oct 2006 07:11:03 +0000 Subject: [PATCH] sync with each individual stapprobe man page --- documentation.html | 13 + man5/stapprobes.5.html | 725 ++------------ man5/stapprobes.iosched.5.html | 148 +++ man5/stapprobes.netdev.5.html | 114 +++ man5/stapprobes.nfs.5.html | 1615 ++++++++++++++++++++++++++++++ man5/stapprobes.nfsd.5.html | 683 +++++++++++++ man5/stapprobes.pagefault.5.html | 69 ++ man5/stapprobes.process.5.html | 152 +++ man5/stapprobes.rpc.5.html | 786 +++++++++++++++ man5/stapprobes.scsi.5.html | 208 ++++ man5/stapprobes.signal.5.html | 663 ++++++++++++ man5/stapprobes.tcp.5.html | 148 +++ man5/stapprobes.udp.5.html | 148 +++ 13 files changed, 4817 insertions(+), 655 deletions(-) create mode 100644 man5/stapprobes.iosched.5.html create mode 100644 man5/stapprobes.netdev.5.html create mode 100644 man5/stapprobes.nfs.5.html create mode 100644 man5/stapprobes.nfsd.5.html create mode 100644 man5/stapprobes.pagefault.5.html create mode 100644 man5/stapprobes.process.5.html create mode 100644 man5/stapprobes.rpc.5.html create mode 100644 man5/stapprobes.scsi.5.html create mode 100644 man5/stapprobes.signal.5.html create mode 100644 man5/stapprobes.tcp.5.html create mode 100644 man5/stapprobes.udp.5.html diff --git a/documentation.html b/documentation.html index 3d988c22..445d57cd 100644 --- a/documentation.html +++ b/documentation.html @@ -61,6 +61,19 @@

Older Stuff

diff --git a/man5/stapprobes.5.html b/man5/stapprobes.5.html index 39355e5d..e489045d 100644 --- a/man5/stapprobes.5.html +++ b/man5/stapprobes.5.html @@ -126,7 +126,7 @@ context. It is possible for such probes to be run concurrently on a multi-processor computer.

-Alternatively, intervals may be specified in units of milliseconds. +Alternatively, intervals may be specified in units of time. There are two probe point variants similar to the jiffies timer:
@@ -141,10 +141,18 @@ timer.ms(N).randomize(M) -Here, N and M are specified in milliseconds. The probe intervals will be -rounded up to the nearest jiffies interval for the actual timer. If the -"randomize" component is given, then the random value will be added to the -interval before the conversion to jiffies. +Here, N and M are specified in milliseconds, but the full options for units +are seconds (s/sec), milliseconds (ms/msec), microseconds (us/usec), +nanoseconds (ns/nsec), and hertz (hz). Randomization is not supported for +hertz timers. +

+The actual resolution of the timers depends on the target kernel. For +kernels prior to 2.6.17, timers are limited to jiffies resolution, so +intervals are rounded up to the nearest jiffies interval. After 2.6.17, +the implementation uses hrtimers for tighter precision, though the actual +resolution will be arch-dependent. In either case, if the "randomize" +component is given, then the random value will be added to the interval +before any rounding occurs.

Profiling timers are also available to provide probes that execute on all @@ -311,662 +319,51 @@ where NN is the number of parameters supplied by the macro. Number and string parameters are passed in a type-safe manner.

IO SCHEDULER

- -

-This family of probe points is used to probe the IO scheduler activities. -It contains the following probe points: -

- -

ioscheduler.elv_next_request - -

-Fires when a request is retrieved from request queue -

-Arguments: - -

-elevator_name - -
The name of the elevator -

-disk_major - -
The major number of the disk -

-disk_minor - -
The minor number of the disk -

- -

ioscheduler.elv_add_request - -

-Fires when a request is added to the request queue -

-Arguments: - -

-elevator_name - -
The name of the elevator -

-disk_major - -
The major number of the disk -

-disk_minor - -
The minor number of the disk -

- -

ioscheduler.elv_completed_request - -

-Fires when a request is completed -

-Arguments: - -

-elevator_name - -
The name of the elevator -

-disk_major - -
The major number of the disk -

-disk_minor - -
The minor number of the disk -

- -

SCSI

- -

-This family of probe points is used to probe the SCSI activities. -It contains the following probe points: -

- -

scsi.ioentry - -

-Fires when SCSI mid layer prepares a SCSI request -

-Arguments: - -

-disk_major - -
The major number of the disk -

-disk_minor - -
The minor number of the disk -

-device_state - -
The current state of the device. The possible values could be: -

-
        SDEV_CREATED = 1,    /* device created but not added to sysfs -
                              * Only internal commands allowed (for inq) */ -
        SDEV_RUNNING = 2,    /* device properly configured -
                              * All commands allowed */ -
        SDEV_CANCEL = 3,     /* beginning to delete device -
                              * Only error handler commands allowed */ -
        SDEV_DEL = 4,        /* device deleted -
                              * no commands allowed */ -
        SDEV_QUIESCE = 5,    /* Device quiescent.  No block commands -
                              * will be accepted, only specials (which -
                              * originate in the mid-layer) */ -
        SDEV_OFFLINE = 6,    /* Device offlined (by error handling or -
                              * user request */ -
        SDEV_BLOCK = 7,      /* Device blocked by scsi lld.  No scsi -
                              * commands from user or midlayer should be issued -
                              * to the scsi lld. */ -

- -

scsi.iodispatching - -

-Fires when the SCSI mid layer dispatches a SCSI command to the low level driver -

-Arguments: - -

-host_no - -
The host number -

-channel - -
The channel number -

-lun - -
The lun number -

-dev_id - -
The scsi device id -

-device_state - -
The current state of the device. -

-data_direction - -
The data_direction specifies whether this command is from/to the device. -
The possible values could be: -

-
        DMA_BIDIRECTIONAL = 0, -
        DMA_TO_DEVICE = 1, -
        DMA_FROM_DEVICE = 2, -
        DMA_NONE = 3, -

-request_buffer - -
The request buffer address -

-req_bufflen - -
The request buffer length -

- -

scsi.iodone - -

-Fires when a SCSI command is done by low level driver and enqueued into the done queue. -

-Arguments: - -

-host_no - -
The host number -

-channel +

PERFORMANCE MONITORING HARDWARE

-
The channel number

-lun - -
The lun number -

-dev_id - -
The scsi device id -

-device_state - -
The current state of the device -

-data_direction - -
The data_direction specifies whether this command is from/to the device. -

- -

scsi.iocompleted - -

-Fires when SCSI mid layer runs the completion processing for -block device I/O requests -

-Arguments: - +The perfmon family of probe points is used to access the performance +monitoring hardware available in modern processors. This family of +probes points needs the perfmon2 support in the kernel to access the +performance monitoring hardware.

-host_no -
The host number -

-channel +Performance monitor hardware points begin with a +perfmon. -
The channel number -

-lun +The next part of the names the event being counted +counter(event). -
The lun number -

-dev_id +The event names are processor implementation specific with the +execption of the generic +cycles and instructions -
The scsi device id -

-device_state +events, which are available on all processors. This sets up a counter +on the processor to count the number of events occuring on the +processor. For more details on the performance monitoring events +available on a specific processor use the command perfmon2 command: -
The current state of the device -

-data_direction - -
The data_direction specifies whether this command is from/to the device. -

-goodbytes - -
The bytes completed. -

- -

NETWORK DEVICE

- -

-This family of probe points is used to probe the activities of network -device. -It contains the following probe points: -

- -

netdev.receive - -

-Fires when data arrives on network device -

-Arguments: - -

-dev_name - -
The name of the device. e.g: eth0, ath1 -

-length - -
The length of the receiving buffer -

-protocol - -
  The possible values of protocol could be: -
     0800    IP -
     8100    802.1Q VLAN -
     0001    802.3 -
     0002    AX.25 -
     0004    802.2 -
     8035    RARP -
     0005    SNAP -
     0805    X.25 -
     0806    ARP -
     8137    IPX -
     0009    Localtalk -
     86DD    IPv6 -

-truesize - -
The size of the received data -

- -

netdev.transmit - -

-Fires when the network device wants to transmit a buffer -

-Arguments: - -

-dev_name - -
The name of the device. e.g: eth0, ath1 -

-length - -
The length of the transmit buffer -

-protocol - -
The protocol of this packet. -

-truesize - -
The size of the the data to be transmitted. -

- -

PAGE FAULT

- -

-This family of probe points is used to probe page fault events. -It contains the following probe points: -

- -

vm.pagefault - -

-Fires when there is a pagefault -

-Arguments: - -

-address - -
The address caused this page fault. -

-write_access - -
1 means this is a write access and 0 means this is a read access -

- -

PROCESS

- -

-This family of probe points is used to probe the process activities. -It contains the following probe points: -

- -

process.create - -

-Fires whenever a new process is successfully created, either as a -result of one of the fork syscall variants, or a new kernel thread. -

-Arguments: - -

-task - -
a handle to the newly created process -

-new_pid - -
pid of the newly created process -

- -

process.start - -

-Fires immediately before a new process begins execution. -

-Arguments: - -

-N/A - -

- -

process.exec - -

-Fires whenever a process attempts to exec to a new program -

-Arguments: - -

-filename - -
the path to the new executable -

- -

process.exec_complete - -

-Fires at the completion of an exec call -

-Arguments: - -

-errno - -
the error number resulting from the exec -

-success - -
a boolean indicating whether the exec was successful -

- -

process.exit - -

-Fires when a process terminates. This will always be followed by a -process.release, though the latter may be delayed if the process -waits in a zombie state. -

-Arguments: - -

-code - -
the exit code of the process -

- -

process.release - -

-Fires when a process is released from the kernel. This always -follows a process.exit, though it may be delayed somewhat if the -process waits in a zombie state. -

-Arguments: - -

-task - -
a task handle to the process being released -

-pid - -
pid of the process being released -

- -

TCP

- -

-This family of probe points is used to probe TCP layer activities. -It contains the following probe points: -

- -

tcp.sendmsg - -

-Fires whenever sending a tcp message -

-Arguments: - -

-sock - -
network socket -

-size - -
number of bytes to send -

- -

tcp.sendmsg.return - -

-Fires whenever sending message is done -

-Arguments: - -

-size - -
number of bytes sent -

- -

tcp.recvmsg - -

-Fires whenever a message is received -

-Arguments: - -

-sock - -
network socket -

-size - -
number of bytes to be received -

- -

tcp.recvmsg.return - -

-Fires whenever message receiving is done -

-Arguments: - -

-size - -
number of bytes received -

- -

tcp.disconnect - -

-Fires whenever tcp is disconnected -

-Arguments: - -

-sock - -
network socket -

-flags - -
TCP flags (e.g. FIN, etc) -

- -

tcp.disconnect.return +
-

-Fires when returning from tcp.disconnect -

-Arguments: +

+pfmon -l -

-ret +

-
error code (0: no error) -

- -

UDP

-This family of probe points is used to probe UDP layer activities. -It contains the following probe points: -

udp.sendmsg - -

-Fires whenever sending a udp message -

-Arguments: - -

-sock - -
network socket -

-size - -
number of bytes to send -

- -

udp.sendmsg.return - -

-Fires whenever sending message is done -

-Arguments: - -

-size - -
number of bytes sent -

- -

udp.recvmsg - -

-Fires whenever a message is received -

-Arguments: - -

-sock - -
network socket -

-size - -
number of bytes to be received -

- -

udp.recvmsg.return - -

-Fires whenever message receiving is done -

-Arguments: - -

-size - -
number of bytes received -

- -

udp.disconnect - -

-Fires whenever udp is disconnected -

-Arguments: - -

-sock - -
network socket -

-flags - -
flags (e.g. FIN, etc) -

- -

udp.disconnect.return - -

-Fires when returning from udp.disconnect -

-Arguments: - -

-ret - -
error code (0: no error) +

$counter

+is a handle used in the body of the probe for operations +involving the counter associated with the probe. +

read_counter

+is a function that is passed the handle for the perfmon probe and returns +the current count for the event.

- +

EXAMPLES

@@ -992,15 +389,39 @@ name in any of the USB drivers.

kernel.statement(0xc0044852)

refers to the first byte of the statement whose compiled instructions include the given address in the kernel. +

kernel.statement("*@kernel/sched.c:2917")

+refers to the statement of line 2917 within the "kernel/sched.c".

kernel.syscall.*.return

refers to the group of probe aliases with any name in the third position

- +

STAPPROBES.IOSCHED

+Section: File Formats (5)
Updated: @DATE@
Index +Return to Main Contents

+ + +

NAME

+ +stapprobes.iosched - systemtap IO scheduler probe points +

+ + + +

+ +

DESCRIPTION

+ +

+This family of probe points is used to probe the IO scheduler +activities. It contains the following probe points: +

+ +

ioscheduler.elv_next_request + +

+Fires when retrieves a request from request queue +

+Arguments: + +

+elevator_name + +
The elevator name +

+ +

ioscheduler.elv_next_request.return + +

+Fires when return from retrieving a request +

+Arguments: + +

+req + +
Address of the request +

+req_flags + +
request flags +

+disk_major + +
disk major number of the request +

+disk_minor + +
disk minor number of the request +

+ +

ioscheduler.elv_add_request + +

+Fires when add a request into request queue +

+Arguments: + +

+elevator_name + +
The elevator name +

+req + +
Address of the request +

+req_flags + +
request flags +

+disk_major + +
disk major number of the request +

+disk_minor + +
disk minor number of the request +

+ +

ioscheduler.elv_completed_request + +

+Fires when a request is completed +

+Arguments: + +

+elevator_name + +
The elevator name +

+req + +
Address of the request +

+req_flags + +
request flags +

+disk_major + +
disk major number of the request +

+disk_minor + +
disk minor number of the request +

+ +

Index

NAME: +
DESCRIPTION: +
SEE ALSO: +

+This document was created by +man2html, +using the manual pages.
+Time: 07:06:13 GMT, October 18, 2006 + + diff --git a/man5/stapprobes.netdev.5.html b/man5/stapprobes.netdev.5.html new file mode 100644 index 00000000..6de132dd --- /dev/null +++ b/man5/stapprobes.netdev.5.html @@ -0,0 +1,114 @@ +Content-type: text/html + +Manpage of STAPPROBES.NETDEV + +

STAPPROBES.NETDEV

+Section: File Formats (5)
Updated: @DATE@
Index +Return to Main Contents

+ + +

NAME

+ +stapprobes.netdev - systemtap network device probe points +

+ + + +

+ +

DESCRIPTION

+ +

+This family of probe points is used to probe the activities of network +device. +It contains the following probe points: +

+ +

netdev.receive + +

+Fires when data arrives on network device +

+Arguments: + +

+dev_name + +
The name of the device. e.g: eth0, ath1 +

+length + +
The length of the receiving buffer +

+protocol + +
  The possible values of protocol could be: +
     0800    IP +
     8100    802.1Q VLAN +
     0001    802.3 +
     0002    AX.25 +
     0004    802.2 +
     8035    RARP +
     0005    SNAP +
     0805    X.25 +
     0806    ARP +
     8137    IPX +
     0009    Localtalk +
     86DD    IPv6 +

+truesize + +
The size of the received data +

+ +

netdev.transmit + +

+Fires when the network device wants to transmit a buffer +

+Arguments: + +

+dev_name + +
The name of the device. e.g: eth0, ath1 +

+length + +
The length of the transmit buffer +

+protocol + +
The protocol of this packet. +

+truesize + +
The size of the the data to be transmitted. +

+ +

Index

NAME: +
DESCRIPTION: +
SEE ALSO: +

+This document was created by +man2html, +using the manual pages.
+Time: 06:28:19 GMT, October 18, 2006 + + diff --git a/man5/stapprobes.nfs.5.html b/man5/stapprobes.nfs.5.html new file mode 100644 index 00000000..e2b0cf43 --- /dev/null +++ b/man5/stapprobes.nfs.5.html @@ -0,0 +1,1615 @@ +Content-type: text/html + +Manpage of STAPPROBES.NFS + +

STAPPROBES.NFS

+Section: File Formats (5)
Updated: @DATE@
Index +Return to Main Contents

+ + +

NAME

+ +stapprobes.nfs - systemtap NFS client side probe points +

+ + + +

+ +

DESCRIPTION

+ +

+This family of probe points is used to probe NFS activities on +client side. +It contains the following probe points: +

+ +

nfs.fop.llseek + +

+Fires whenever doing a llseek operation on nfs client side +

+Arguments: + +

+dev + +
device identifier +

+ino + +
inode number +

+s_id + +
the pointer to s_id +

+devname + +
the combination of server ip and the name of block device +
on server +

+maxbyte + +
Maximum size of the files +

+offset + +
the offset of file to be repositioned +

+origin + +
  the original position. The possible value could be: +
          SEEK_SET +
                The offset is set to offset bytes. +
          SEEK_CUR +
                The offset is set to its current location +
                plus offset bytes. +
          SEEK_END +
                The offset is set to the size of the file +
                plus offset bytes. +

+ +

nfs.fop.llseek.return + +

+Fires whenever nfs llseek operation is done +

+Arguments: + +

+retstr + +
resulting offset location +

+ +

nfs.fop.read + +

+Fires whenever doing a read operation on nfs client side +

+Arguments: + +

+dev + +
device identifier +

+ino + +
inode number +

+s_id + +
the pointer to s_id +

+devname + +
the combination of server ip and the name of block device +
on server +

+len,size + +
number of bytes to be read +

+pos + +
current file offset
+

+buf + +
the buf address +

+ +

nfs.fop.read.return + +

+Fires whenever nfs read operation is done +

+Arguments: + +

+size + +
number of bytes read +

+ +

nfs.fop.write + +

+Fires whenever doing a write operation on nfs client side +

+Arguments: + +

+dev + +
device identifier +

+ino + +
inode number +

+s_id + +
the pointer to s_id +

+devname + +
the combination of server ip and the name of block device +
on server +

+len,size + +
number of bytes to written +

+pos + +
current file offset
+

+buf + +
the buf address +

+ +

nfs.fop.write.return + +

+Fires whenever nfs write operation is done +

+Arguments: + +

+size + +
number of bytes written +

+ +

nfs.fop.aio_read + +

+Fires whenever doing an aio_read operation on nfs client side +

+Arguments: + +

+dev + +
device identifier +

+ino + +
inode number +

+s_id + +
the pointer to s_id +

+devname + +
the combination of server ip and the name of block device +
on server +

+count,size + +
number of bytes to be read +

+pos + +
current file offset
+

+buf + +
the buf address +

+parent_name + +
parent dir name +

+file_name + +
file name +

+cache_valid + +
cache related bit mask flag +

+cache_time + +
when we started read-caching this inode +

+attrtimeo + +
how long the cached information is assumed to be valid. +

+
The cached attrs for this inode needed to be revalidated if +
jiffies - read_cache_jiffies > attrtime +

+ +

nfs.fop.aio_read.return + +

+Fires whenever nfs aio_read operation is done +

+Arguments: + +

+size + +
number of bytes read +

+ +

nfs.fop.aio_write + +

+Fires whenever doing an aio_write operation on nfs client side +

+Arguments: + +

+dev + +
device identifier +

+ino + +
inode number +

+s_id + +
the pointer to s_id +

+devname + +
the combination of server ip and the name of block device +
on server +

+count,size + +
number of bytes to written +

+pos + +
current file offset
+

+buf + +
the buf address +

+parent_name + +
parent dir name +

+file_name + +
file name +

+ +

nfs.fop.aio_write.return + +

+Fires whenever nfs aio_write operation is done +

+Arguments: + +

+size + +
number of bytes written +

+ +

nfs.fop.mmap + +

+Fires whenever doing an mmap operation on nfs client side +

+Arguments: + +

+dev + +
device identifier +

+ino + +
inode number +

+s_id + +
the pointer to s_id +

+devname + +
the combination of server ip and the name of block device +
on server +

+vm_start + +
start address within vm_mm +

+vm_end + +
the first byte after end address within vm_mm +

+vm_flag + +
vm flags +

+parent_name + +
parent dir name +

+file_name + +
file name +

+cache_valid + +
cache related bit mask flag +

+cache_time + +
when we started read-caching this inode +

+attrtimeo + +
how long the cached information is assumed to be valid. +

+
The cached attrs for this inode needed to be revalidated if +
jiffies - read_cache_jiffies > attrtime +

+ +

nfs.fop.open + +

+Fires whenever doing an open operation on nfs client side +

+Arguments: + +

+dev + +
device identifier +

+ino + +
inode number +

+s_id + +
the pointer to s_id +

+devname + +
the combination of server ip and the name of block device +
on server +

+file_name + +
file name +

+flag + +
file flag +

+i_size + +
file length in bytes +

+ +

nfs.fop.flush + +

+Fires whenever doing an flush operation on nfs client side +

+Arguments: + +

+dev + +
device identifier +

+ino + +
inode number +

+s_id + +
the pointer to s_id +

+devname + +
the combination of server ip and the name of block device +
on server +

+mode + +
file mode +

+ndirty + +
number of dirty page to be flushed +

+ +

nfs.fop.release + +

+Fires whenever doing a release page operation on nfs client side +

+Arguments: + +

+dev + +
device identifier +

+ino + +
inode number +

+s_id + +
the pointer to s_id +

+devname + +
the combination of server ip and the name of block device +
on server +

+mode + +
file mode +

+ +

nfs.fop.fsync + +

+Fires whenever doing a fsync operation on nfs client side +

+Arguments: + +

+dev + +
device identifier +

+ino + +
inode number +

+s_id + +
the pointer to s_id +

+devname + +
the combination of server ip and the name of block device +
on server +

+ndirty + +
number of dirty page to be flushed +

+ +

nfs.fop.lock + +

+Fires whenever doing a file lock operation on nfs client side +

+Arguments: + +

+dev + +
device identifier +

+ino + +
inode number +

+s_id + +
the pointer to s_id +

+devname + +
the combination of server ip and the name of block device +
on server +

+i_mode + +
file type and access rights +

+cmd + +
cmd arguments +

+fl_type + +
lock type +

+fl_flag + +
lock flags +

+fl_start + +
starting offset of locked region +

+fl_end + +
ending offset of locked region +
+ +

nfs.fop.sendfile + +

+Fires whenever doing a send file operation on nfs client side +

+Arguments: + +

+dev + +
device identifier +

+ino + +
inode number +

+s_id + +
the pointer to s_id +

+devname + +
the combination of server ip and the name of block device +
on server +

+count,size + +
number of bytes to sent +

+ppos + +
current file offset
+

+cache_valid + +
cache related bit mask flag +

+cache_time + +
when we started read-caching this inode +

+attrtimeo + +
how long the cached information is assumed to be valid. +

+
The cached attrs for this inode needed to be revalidated if +
jiffies - read_cache_jiffies > attrtime +

+ +

nfs.fop.sendfile.return + +

+Fires whenever nfs sendfile operation is done +

+Arguments: + +

+size + +
number of bytes sent +

+ +

nfs.fop.check_flags + +

+Fires whenever doing a check flag operation on nfs client side +

+Arguments: + +

+flags + +
file flag +

+ +

nfs.aop.readpage + +

+Fires when a previous async read operation failed +

+Arguments: + +

+__page + +
the address of page +

+dev + +
device identifier +

+ino + +
inode number +

+i_flag + +
file flags +

+i_size + +
file length in bytes +

+sb_flag + +
super block flags +

+file + +
file argument +

+page_index + +
offset within mapping +

+rsize + +
read size (in bytes) +

+ +

nfs.aop.readpages + +

+Fies when in readahead way,read several pages once +

+Arguments: + +

+dev + +
device identifier +

+ino + +
inode number +

+nr_pages ,size + +
number of pages attempted to read in this execution +

+file + +
filp argument +

+rpages + +
read size (in pages) +

+rsize + +
read size (in bytes) +

+ +

nfs.aop.readpages.return + +

+Fies whenever a nfs read pages operation is done +

+Arguments: + +

+size + +
number of pages read +

+ +

nfs.aop.set_page_dirty + +

+Fies whenever set page dirty on nfs client side +

+Arguments: + +

+__page + +
the address of page +

+page_flag + +
page flags +

+ +

nfs.aop.writepage + +

+Fies whenever writing an mapped page to the server from nfs client side +

+Arguments: + +

+__page + +
the address of page +

+dev + +
device identifier +

+ino + +
inode number +

+for_reclaim + +
a flag of writeback_control, indicates if it's invoked from the page allocator +

+for_kupdate + +
a flag of writeback_control, indicates if it's a kupdate writeback +
The priority of wb is decided by above two flags +

+i_flag + +
file flags +

+i_size + +
file length in bytes +

+i_state + +
inode state flags +

+sb_flag + +
super block flags +

+page_index + +
offset within mapping +

+wsize + +
write size +

+ +

nfs.aop.writepages + +

+Fies whenever writing several dirty pages to the server from nfs client sides +

+Arguments: + +

+dev + +
device identifier +

+ino + +
inode number +

+for_reclaim + +
a flag of writeback_control, indicates if it's invoked from the page allocator +

+for_kupdate + +
a flag of writeback_control, indicates if it's a kupdate writeback +
The priority of wb is decided by above two flags +

+wpages + +
write size (in pages) +

+wsize + +
write size +

+nr_to_write ,size + +
number of pages attempted to be written in this execution +

+ +

nfs.aop.prepare_write + +

+Fies whenever prepare a page for writting on nfs client sides +

+Arguments: + +

+__page + +
the address of page +

+dev + +
device identifier +

+ino + +
inode number +

+offset + +
start address of this write operation +

+to + +
end address of this write operation +

+page_index + +
offset within mapping +

+size + +
read bytes +

+ +

nfs.aop.commit_write + +

+Fies often after prepare write operation +

+Arguments: + +

+__page + +
the address of page +

+dev + +
device identifier +

+ino + +
inode number +

+offset + +
start address of this write operation +

+to + +
end address of this write operation +

+i_flag + +
file flags +

+i_size + +
file length in bytes +

+sb_flag + +
super block flag +

+page_index + +
offset within mapping +

+size + +
read bytes +

+ +

nfs.aop.release_page + +

+Arguments: + +

+__page + +
the address of page +

+dev + +
device identifier +

+ino + +
inode number +

+page_index + +
offset within mapping +

+ +

nfs.proc.lookup + +

+Arguments: + +

+server_ip + +
ip address of server +

+prot + +
transfer protocol +

+version + +
nfs version +

+filename + +
the name of file which client opens/searchs on server +

+name_len + +
the length of file name +

+bitmask0, bitmask1 + +
V4 bitmask representing the set of attributes +
supported on this filesystem (only in probe nfs.proc4.lookup) +

+ +

nfs.proc.read + +

+Fires when client synchronously reads file from server +

+Arguments: + +

+server_ip + +
ip address of server +

+prot + +
transfer protocol +

+version + +
nfs version +

+flags + +
used to set task->tk_flags in rpc_init_task function +

+size,count + +
number of bytes to be read in this execution +

+offset + +
the file offset +

+ +

nfs.proc.read.return + +

+Fires when synchronously reading file from server is done +

+Arguments: + +

+size + +
number of bytes read +

+ +

nfs.proc.write + +

+Fires when client synchronously writes file to server +

+Arguments: + +

+server_ip + +
ip address of server +

+prot + +
transfer protocol +

+version + +
nfs version +

+flags + +
used to set task->tk_flags in rpc_init_task function +

+size,count + +
number of bytes to be written in this execution +

+offset + +
the file offset +

+bitmask0, bitmask1 + +
V4 bitmask representing the set of attributes +
supported on this filesystem (only in probe nfs.proc4.lookup) +

+ +

nfs.proc.write.return + +

+Fires when synchronously writting file from server is done +

+Arguments: + +

+size + +
number of bytes written +

+ +

nfs.proc.commit + +

+Fires when client writes the buffered data to disk,the buffered +data is asynchronously written by client before(not exist in NFSV2) +

+Arguments: + +

+server_ip + +
ip address of server +

+prot + +
transfer protocol +

+version + +
nfs version +

+size,count + +
number of bytes to be written in this execution +

+offset + +
the file offset +

+bitmask0, bitmask1 + +
V4 bitmask representing the set of attributes +
supported on this filesystem (only in probe nfs.proc4.lookup) +

+ +

nfs.proc.commit.return + +

+Fires when committing operation is done +

+Arguments: + +

+size + +
number of bytes written +

+ +

nfs.proc.read_setup + +

+Fires when client asynchronously reads file from server, +this function is used to setup a read rpc task,not do +a real read operation. +

+Arguments: + +

+server_ip + +
ip address of server +

+prot + +
transfer protocol +

+version + +
nfs version +

+size,count + +
number of bytes to be read in this execution +

+offset + +
the file offset +

+ +

nfs.proc.read_done + +

+Fires when a read reply is received or some read error occur +(timeout or socket shutdown) +

+Arguments: + +

+server_ip + +
ip address of server +

+prot + +
transfer protocol +

+version + +
nfs version +

+status + +
result of last async read operation +

+count + +
number of bytes read +

+timestamp + +
time stamp ,which is used for lease renewal (only +
in nfs.proc4.read_done) +

+ +

nfs.proc.write_setup + +

+Fires when client asynchronously write data to server, +this function is used to setup a write rpc task,not do +a write read operation. +

+Arguments: + +

+server_ip + +
ip address of server +

+prot + +
transfer protocol +

+version + +
nfs version +

+size,count + +
number of bytes to be written in this execution +

+offset + +
the file offset +

+how + +
  used to set args.stable,The possible value could be: +
          NFS_UNSTABLE, +
          NFS_DATA_SYNC, +
          NFS_FILE_SYNC +
          (only in nfs.proc3.write_setup and nfs.proc4.write_setup) +

+bitmask0, bitmask1 + +
V4 bitmask representing the set of attributes supported +
on this filesystem (only in probe nfs.proc4.write_setup) +

+ +

nfs.proc.write_done + +

+Fires when a write reply is received or some write error occur +(timeout or socket shutdown) +

+Arguments: + +

+server_ip + +
ip address of server +

+prot + +
transfer protocol +

+version + +
nfs version +

+status + +
result of last async write operation +

+valid + +
fattr->valid ,indicates which fields are valid +

+count + +
number of bytes written +

+timestamp + +
time stamp ,which is used for lease renewal (only +
in nfs.proc4.read_done) +

+ +

nfs.proc.commit_setup + +

+Fires when client asynchronously do a commit operation, +this function is used to setup a commit rpc task,not do +a commit read operation. +

+Arguments: + +

+server_ip + +
ip address of server +

+prot + +
transfer protocol +

+version + +
nfs version +

+size,count + +
number of bytes to be written in this execution +

+offset + +
the file offset +

+bitmask0, bitmask1 + +
V4 bitmask representing the set of attributes supported +
on this filesystem (only in probe nfs.proc4.commit_setup) +

+ +

nfs.proc.commit_done + +

+Fires when a commit reply is received or some commit error occur +(timeout or socket shutdown) +

+Arguments: + +

+server_ip + +
ip address of server +

+prot + +
transfer protocol +

+version + +
nfs version +

+status + +
result of last async write operation +

+valid + +
fattr->valid ,indicates which fields are valid +

+count + +
number of bytes written +

+timestamp + +
time stamp ,which is used for lease renewal (only +
in nfs.proc4.read_done) +

+ +

nfs.proc.open + +

+Fires whenever doing a open operation on nfs client side, +the nfs_open function is used to allocate file read/write +context information +

+Arguments: + +

+server_ip + +
ip address of server +

+prot + +
transfer protocol +

+version + +
nfs version +

+filename + +
file name +

+flag + +
file flag +

+mode + +
file mode +

+ +

nfs.proc.release + +

+Fires whenever doing a release operation on nfs client side, +

+Arguments: + +

+server_ip + +
ip address of server +

+prot + +
transfer protocol +

+version + +
nfs version +

+filename + +
file name +

+flag + +
file flag +

+mode + +
file mode +

+ +

nfs.proc4.handle_exception + +

+Fires whenever doing the error handling, only exist in NFSV4 +

+errorcode + +
error code +

+ +

nfs.proc.create + +

+Fires whenever nfs client creates a file on server +

+Arguments: + +

+server_ip + +
ip address of server +

+prot + +
transfer protocol +

+version + +
nfs version +

+fh + +
file handler of parent dir +

+filename + +
file name +

+filelen + +
length of file name +

+flag + +
indicates create mode(only for NFSV3 and NFSV4) +

+ +

nfs.proc.remove + +

+Fires whenever nfs client removes a file from server +

+Arguments: + +

+server_ip + +
ip address of server +

+prot + +
transfer protocol +

+version + +
nfs version +

+fh + +
file handler of parent dir +

+filename + +
file name +

+filelen + +
length of file name +

+ +

nfs.proc.rename + +

+Fires whenever nfs client renames a file on server +

+Arguments: + +

+server_ip + +
ip address of server +

+prot + +
transfer protocol +

+version + +
nfs version +

+old_fh + +
file handler of old parent dir +

+old_name + +
old file name +

+old_filelen + +
length of old file name +

+new_fh + +
file handler of new parent dir +

+new_name + +
new file name +

+new_filelen + +
length of new file name +

+ +

Index

NAME: +
DESCRIPTION: +
SEE ALSO: +

+This document was created by +man2html, +using the manual pages.
+Time: 06:28:19 GMT, October 18, 2006 + + diff --git a/man5/stapprobes.nfsd.5.html b/man5/stapprobes.nfsd.5.html new file mode 100644 index 00000000..d76d3738 --- /dev/null +++ b/man5/stapprobes.nfsd.5.html @@ -0,0 +1,683 @@ +Content-type: text/html + +Manpage of STAPPROBES.NFSD + +

STAPPROBES.NFSD

+Section: File Formats (5)
Updated: @DATE@
Index +Return to Main Contents

+ + +

NAME

+ +stapprobes.nfsd - systemtap NFS server side probe points +

+ + + +

+ +

DESCRIPTION

+ +

+This family of probe points is used to probe NFS activities on +server side. Because there is only one function, i.e., nfsd4_proc_compound +in proc level for NFSv4, all the following nfsd.proc probe points except +nfsd.proc.compound are only for NFSv2 and NFSv3. +

+It contains the following probe points: +

+ +

nfsd.proc.lookup + +

+Fires whenever client opens/searchs file on server +

+Arguments: + +

+client_ip + +
the ip address of client +

+proto + +
transfer protocol +

+version + +
nfs version +

+fh + +
the pointer to file handler of parent dir +

+filename + +
file name +

+filelen + +
the length of file name +

+ +

nfsd.proc.read + +

+Fires whenever client reads file on server +

+Arguments: + +

+client_ip + +
the ip address of client +

+proto + +
transfer protocol +

+version + +
nfs version +

+fh + +
the pointer to file handler of file +

+count,size + +
number of bytes to be read +

+offset + +
the offset of file +

+vec + +
struct kvec ,includes buf address in kernel address +
and the length of each buffer +

+vlen + +
number of blocks to be read +

+ +

nfsd.proc.write + +

+Fires whenever client writes data to file on server +

+Arguments: + +

+client_ip + +
the ip address of client +

+proto + +
transfer protocol +

+version + +
nfs version +

+fh + +
the pointer to file handler of file +

+count,size + +
number of bytes to written +

+offset + +
the offset of file +

+vec + +
struct kvec ,includes buf address in kernel address +
and the length of each buffer +

+vlen + +
number of blocks to written +

+stable + +
argp->stable(only for nfs.proc3.write) +

+ +

nfsd.proc.commit + +

+Fires whenever client does a commit operation +

+Arguments: + +

+client_ip + +
the ip address of client +

+proto + +
transfer protocol +

+version + +
nfs version +

+fh + +
the pointer to file handler of file +

+count,size + +
number of bytes to written +

+offset + +
the offset of file +

+ +

nfsd.proc.create + +

+Fires whenever client creates a file on server +

+Arguments: + +

+client_ip + +
the ip address of client +

+proto + +
transfer protocol +

+version + +
nfs version +

+fh + +
the pointer to file handler of parent dir +

+filename + +
file name +

+filelen + +
the length of file name +

+ +

nfsd.proc.remove + +

+Fires whenever client removes a file on server +

+Arguments: + +

+client_ip + +
the ip address of client +

+proto + +
transfer protocol +

+version + +
nfs version +

+fh + +
the pointer to file handler of file +

+filename + +
file name +

+filelen + +
the length of file name +

+ +

nfsd.proc.rename + +

+Fires whenever client renames a file on server +

+Arguments: + +

+client_ip + +
the ip address of client +

+proto + +
transfer protocol +

+version + +
nfs version +

+fh + +
the pointer to file handler of old path +

+tfh + +
the pointer to file handler of new path +

+filename + +
old file name +

+tname + +
new file name +

+filelen + +
the length of old file name +

+tlen + +
the length of new file name +

+ +

nfsd.proc.compound + +

+Fires whenever server receives a NFSV4 operation from client +

+Arguments: + +

+client_ip + +
the ip address of client +

+proto + +
transfer protocol +

+version + +
nfs version +

+num + +
number of file operation +

+op + +
head of operation list +

+ +

nfsd.open + +

+Fires whenever server opens file +

+Arguments: + +

+fh + +
file handle (the first part is the length of the file handle) +

+access + +
type of open (read/write/commit/readdir...) +

+type + +
type of file(regular file or dir) +

+ +

nfsd.read + +

+Fires whenever server reads file +

+Arguments: + +

+fh + +
file handle (the first part is the length of the file handle) +

+file + +
argument :file, indicates if the file has been opened. +

+count,size + +
number of bytes to be read +

+offset + +
the offset of file +

+vec + +
struct kvec ,includes buf address in kernel address +
and the length of each buffer +

+vlen + +
number of blocks to be read +

+ +

nfsd.write + +

+Fires whenever server writes file +

+Arguments: + +

+fh + +
file handle (the first part is the length of the file handle) +

+file + +
argument :file, indicates if the file has been opened. +

+count,size + +
number of bytes to be read +

+offset + +
the offset of file +

+vec + +
struct kvec ,includes buf address in kernel address +
and the length of each buffer +

+vlen + +
number of blocks to be written +

+ +

nfsd.commit + +

+Fires when server commits all pending writes to stable storage +

+Arguments: + +

+fh + +
file handle (the first part is the length of the file handle) +

+count,size + +
number of bytes to be read +

+offset + +
the offset of file +

+ +

nfsd.lookup + +

+Fires whenever client opens/searchs file on server +

+Arguments: + +

+fh + +
file handle (the first part is the length of the file handle) +

+filename + +
file name +

+filelen + +
the length of file name +

+ +

nfsd.create + +

+
Fires when client creates a file(regular,dir,device,fifo) on +
server side, sometimes nfsd will call nfsd_create_v3 instead +
of this function +

+Arguments: + +

+fh + +
file handle (the first part is the length of the file handle) +

+filename + +
file name +

+filelen + +
the length of file name +

+type + +
file type(regular,dir,device,fifo ...) +

+iap_valid + +
Attribute flags +

+iap_mode + +
file access mod +

+ +

nfsd.createv3 + +

+Fires when client creates a regular file or set file attributes +on server side,only called by nfsd3_proc_create and nfsd4_open +(op_claim_type is NFS4_OPEN_CLAIM_NULL) +

+Arguments: + +

+fh + +
file handle (the first part is the length of the file handle) +

+filename + +
file name +

+filelen + +
the length of file name +

+iap_valid + +
Attribute flags +

+iap_mode + +
file access mode +

+createmode + +
create mode .The possible values could be: +
NFS3_CREATE_EXCLUSIVE,NFS3_CREATE_UNCHECKED,NFS3_CREATE_GUARDED +

+truncp + +
trunp arguments, indicates if the file shouldbe truncate +

+verfier + +
file attributes (atime,mtime,mode).It's used to reset file +
attributes for CREATE_EXCLUSIVE +

+ +

nfsd.unlink + +

+Fires when client removes a file or a dir on server side, +

+Arguments: + +

+fh + +
file handle (the first part is the length of the file handle) +

+filename + +
file name +

+filelen + +
the length of file name +

+type + +
file type(file or dir) +

+ +

nfsd.rename + +

+Fires when clients rename a file on server side +

+Arguments: + +

+fh + +
file handler of old path +

+tfh + +
file handler of new path +

+filename + +
old file name +

+tname + +
new file name +

+flen + +
length of old file name +

+tlen + +
length of new file name +

+ +

nfsd.close + +

+Fires whenever server closes file +

+Arguments: + +

+filename + +
file name +

+ +

nfsd.dispatch + +

+Fires whenever server receives NFS operation from client +

+Arguments: + +

+client_ip + +
the ip address of client +

+proto + +
transfer protocol +

+version + +
nfs version +

+xid + +
transmission id +

+prog + +
program number +

+proc + +
procedure number +

+ +

Index

NAME: +
DESCRIPTION: +
SEE ALSO: +

+This document was created by +man2html, +using the manual pages.
+Time: 06:28:19 GMT, October 18, 2006 + + diff --git a/man5/stapprobes.pagefault.5.html b/man5/stapprobes.pagefault.5.html new file mode 100644 index 00000000..9c8a8971 --- /dev/null +++ b/man5/stapprobes.pagefault.5.html @@ -0,0 +1,69 @@ +Content-type: text/html + +Manpage of STAPPROBES.PAGEFAULT + +

STAPPROBES.PAGEFAULT

+Section: File Formats (5)
Updated: @DATE@
Index +Return to Main Contents

+ + +

NAME

+ +stapprobes.pagefault - systemtap pagefault probe points +

+ + + +

+ +

DESCRIPTION

+ +

+This family of probe points is used to probe page fault events. +It contains the following probe points: +

+ +

vm.pagefault + +

+Fires when there is a pagefault +

+Arguments: + +

+address + +
The address caused this page fault. +

+write_access + +
1 means this is a write access and 0 means this is a read access +

+ +

Index

NAME: +
DESCRIPTION: +
SEE ALSO: +

+This document was created by +man2html, +using the manual pages.
+Time: 06:28:19 GMT, October 18, 2006 + + diff --git a/man5/stapprobes.process.5.html b/man5/stapprobes.process.5.html new file mode 100644 index 00000000..85fcec05 --- /dev/null +++ b/man5/stapprobes.process.5.html @@ -0,0 +1,152 @@ +Content-type: text/html + +Manpage of STAPPROBES.PROCESS + +

STAPPROBES.PROCESS

+Section: File Formats (5)
Updated: @DATE@
Index +Return to Main Contents

+ + +

NAME

+ +stapprobes.process - systemtap process probe points +

+ + + +

+ +

DESCRIPTION

+ +

+This family of probe points is used to probe the process activities. +It contains the following probe points: +

+ +

process.create + +

+Fires whenever a new process is successfully created, either as a +result of one of the fork syscall variants, or a new kernel thread. +

+Arguments: + +

+task + +
a handle to the newly created process +

+new_pid + +
pid of the newly created process +

+ +

process.start + +

+Fires immediately before a new process begins execution. +

+Arguments: + +

+N/A + +

+ +

process.exec + +

+Fires whenever a process attempts to exec to a new program +

+Arguments: + +

+filename + +
the path to the new executable +

+ +

process.exec_complete + +

+Fires at the completion of an exec call +

+Arguments: + +

+errno + +
the error number resulting from the exec +

+success + +
a boolean indicating whether the exec was successful +

+ +

process.exit + +

+Fires when a process terminates. This will always be followed by a +process.release, though the latter may be delayed if the process +waits in a zombie state. +

+Arguments: + +

+code + +
the exit code of the process +

+ +

process.release + +

+Fires when a process is released from the kernel. This always +follows a process.exit, though it may be delayed somewhat if the +process waits in a zombie state. +

+Arguments: + +

+task + +
a task handle to the process being released +

+pid + +
pid of the process being released +

+ +

Index

NAME: +
DESCRIPTION: +
SEE ALSO: +

+This document was created by +man2html, +using the manual pages.
+Time: 06:28:19 GMT, October 18, 2006 + + diff --git a/man5/stapprobes.rpc.5.html b/man5/stapprobes.rpc.5.html new file mode 100644 index 00000000..9cb963f4 --- /dev/null +++ b/man5/stapprobes.rpc.5.html @@ -0,0 +1,786 @@ +Content-type: text/html + +Manpage of STAPPROBES.RPC + +

STAPPROBES.RPC

+Section: File Formats (5)
Updated: @DATE@
Index +Return to Main Contents

+ + +

NAME

+ +stapprobes.rpc - systemtap SunRPC probe points +

+ + + +

+ +

DESCRIPTION

+ +

+This family of probe points is used to probe the SUNRPC activities, +including the client, the server and the sunrpc scheduler. +

+It contains the following probe points: +

+ +

sunrpc.clnt.create_client + +

+Fires when an RPC client is to be created +

+Arguments: + +

+servername + +
The name of the server machine +

+progname + +
The name of the RPC program +

+prog + +
The number of the RPC program +

+vers + +
The version number of the RPC program +

+prot + +
The number of the IP protocol +

+authflavor + +
The authentication flavor +

+ +

sunrpc.clnt.clone_client + +

+Fires when an RPC client structure is to be cloned +

+Arguments: + +

+servername + +
The name of the server machine +

+progname + +
The name of the RPC program +

+prog + +
The number of the RPC program +

+vers + +
The version number of the RPC program +

+prot + +
The number of the IP protocol +

+authflavor + +
The authentication flavor +

+ +

sunrpc.clnt.shutdown_client + +

+Fires when an RPC client is to be shut down +

+Arguments + +

+servername + +
The name of the server machine +

+progname + +
The name of the RPC program +

+prog + +
The number of the RPC program +

+vers + +
The version number of the RPC program +

+prot + +
The number of the IP protocol +

+authflavor + +
The authentication flavor +

+clones + +
The number of clones +

+tasks + +
The number of references +

+netreconn + +
The count of reconnections +

+rpccnt + +
The count of RPC calls +

+om_ops + +
The count of operations +

+om_ntrans + +
The count of RPC transmissions +

+om_bytes_sent + +
The count of bytes out +

+om_bytes_recv + +
The count of bytes in +

+om_queue + +
The jiffies queued for transmission +

+om_rtt + +
The RPC RTT jiffies +

+om_execution + +
The RPC execution jiffies +

+ +

sunrpc.clnt.bind_new_program + +

+Fires when a new RPC program is to be bound an existing client +

+Arguments + +

+servername + +
The name of the server machine +

+old_progname + +
The name of old RPC program +

+old_prog + +
The number of old RPC program +

+old_vers + +
The version of old RPC program +

+progname + +
The name of new RPC program +

+prog + +
The number of new RPC program +

+vers + +
The version of new RPC program +

+ +

sunrpc.clnt.call_sync + +

+Fires when an RPC procedure is to be called synchronously +

+Arguments + +

+servername + +
The name of the server machine +

+progname + +
The name of the RPC program +

+prog + +
The number of the RPC program +

+vers + +
The version number of the RPC program +

+prot + +
The number of the IP protocol +

+port + +
The port number +

+xid + +
Current transmission id +

+dead + +
Whether this client is abandoned +

+procname + +
The procedure name in this RPC call +

+proc + +
The procedure number in this RPC call +

+flags + +
The flags of this RPC call +

+ +

sunrpc.clnt.call_async + +

+Fires when an RPC procedure is to be called asynchronously +

+Arguments + +

+servername + +
The name of the server machine +

+progname + +
The name of the RPC program +

+prog + +
The number of the RPC program +

+vers + +
The version number of the RPC program +

+prot + +
The number of the IP protocol +

+port + +
The port number +

+xid + +
Current transmission id +

+dead + +
Whether this client is abandoned +

+procname + +
The procedure name in this RPC call +

+proc + +
The procedure number in this RPC call +

+flags + +
The flags of this RPC call +

+ +

sunrpc.clnt.restart_call + +

+Fires when an (async) RPC client is to be restarted +

+Arguments + +

+servername + +
The name of the server machine +

+prog + +
The number of the RPC program +

+xid + +
The transmission id +

+tk_pid + +
The debugging aid of this task +

+tk_flags + +
The task flags +

+tk_priority + +
The task priority +

+tk_runstate + +
The task run status +

+ +

sunrpc.svc.register + +

+Fires when an RPC service is to be registered with the local portmapper. +If proto and port == 0, it means to unregister a service. +

+Arguments + +

+sv_name + +
The name of the service +

+progname + +
The name of the RPC program +

+prog + +
The number of the RPC program +

+prot + +
The number of the IP protocol +

+port + +
The port number +

+ +

sunrpc.svc.create + +

+Fires when an RPC service is to be created +

+Arguments + +

+progname + +
The name of the RPC program +

+prog + +
The number of the RPC program +

+pg_nvers + +
The total of the supported versions +

+bufsize + +
The buffer size +

+ +

sunrpc.svc.destroy + +

+Fires when an RPC client is to be destroyed +

+Arguments + +

+sv_name + +
The service name +

+sv_progname + +
The name of the program +

+sv_prog + +
The number of the program +

+sv_nrthreads + +
The number of concurrent threads +

+netcnt + +
The count of received RPC requests +

+nettcpconn + +
The count of accepted TCP connections +

+rpccnt + +
The count of valid RPC requests +

+rpcbadfmt + +
The count of requests dropped for bad formats +

+rpcbadauth + +
The count of requests drooped for authentication failure +

+ +

sunrpc.svc.process + +

+Fires when an RPC client is to be processed +

+Arguments + +

+sv_name + +
The service name +

+sv_prog + +
The number of the program +

+sv_nrthreads + +
The number of concurrent threads +

+peer_ip + +
The peer address where the request is from +

+rq_xid + +
The transmission id in the request +

+rq_prog + +
The program number in the request +

+rq_vers + +
The program version in the request +

+rq_proc + +
The procedure number in the request +

+rq_prot + +
The IP protocol of the reqeust +

+ +

sunrpc.svc.authorise + +

+Fires when an RPC client is to be authorised +

+Arguments + +

+sv_name + +
The service name +

+peer_ip + +
The peer address where the request is from +

+rq_xid + +
The transmission id in the request +

+rq_prog + +
The program number in the request +

+rq_vers + +
The program version in the request +

+rq_proc + +
The procedure number in the request +

+rq_prot + +
The IP protocol of the reqeust +

+ +

sunrpc.svc.recv + +

+Fires when the server is to receive the next request on any socket +

+Arguments + +

+sv_name + +
The service name +

+sv_prog + +
The number of the program +

+sv_nrthreads + +
The number of concurrent threads +

+timeout + +
The timeout of waiting for data +

+ +

sunrpc.svc.send + +

+Fires when want to return reply to client +

+Arguments + +

+sv_name + +
The service name +

+peer_ip + +
The peer address where the request is from +

+rq_xid + +
The transmission id in the request +

+rq_prog + +
The program number in the request +

+rq_vers + +
The program version in the request +

+rq_proc + +
The procedure number in the request +

+rq_prot + +
The IP protocol of the reqeust +

+ +

sunrpc.svc.drop + +

+Fires when a request is to be dropped +

+Arguments + +

+sv_name + +
The service name +

+peer_ip + +
The peer address where the request is from +

+rq_xid + +
The transmission id in the request +

+rq_prog + +
The program number in the request +

+rq_vers + +
The program version in the request +

+rq_proc + +
The procedure number in the request +

+rq_prot + +
The IP protocol of the reqeust +

+ +

sunrpc.sched.new_task + +

+Fires when a new task is to be created for the specified client +

+Arguments + +xid + +
The transmission id in the RPC call +

+prog + +
The program number in the RPC call +

+vers + +
The program version in the RPC call +

+prot + +
The IP protocol in the RPC call +

+tk_flags + +
The flags of the task +

+ +

sunrpc.sched.release_task + +

+Fires when all resources associated with a task are to be released +

+Arguments + +

+xid + +
The transmission id in the RPC call +

+prog + +
The program number in the RPC call +

+vers + +
The program version in the RPC call +

+prot + +
The IP protocol in the RPC call +

+tk_flags + +
The flags of the task +

+ +

sunrpc.sched.execute + +

+Fires when the RPC `scheduler'(or rather, the finite state machine) +is to be executed +

+Arguments + +

+xid + +
The transmission id in the RPC call +

+prog + +
The program number in the RPC call +

+vers + +
The program version in the RPC call +

+prot + +
The IP protocol in the RPC call +

+tk_pid + +
The debugging id of the task +

+tk_flags + +
The flags of the task +

+ +

sunrpc.sched.delay + +

+Fires when a task is to be delayed +

+Arguments + +

+xid + +
The transmission id in the RPC call +

+prog + +
The program number in the RPC call +

+vers + +
The program version in the RPC call +

+prot + +
The IP protocol in the RPC call +

+tk_pid + +
The debugging id of the task +

+tk_flags + +
The flags of the task +

+delay + +
The time delayed +

+ +

Index

NAME: +
DESCRIPTION: +
SEE ALSO: +

+This document was created by +man2html, +using the manual pages.
+Time: 06:28:19 GMT, October 18, 2006 + + diff --git a/man5/stapprobes.scsi.5.html b/man5/stapprobes.scsi.5.html new file mode 100644 index 00000000..c6abad4e --- /dev/null +++ b/man5/stapprobes.scsi.5.html @@ -0,0 +1,208 @@ +Content-type: text/html + +Manpage of STAPPROBES.SCSI + +

STAPPROBES.SCSI

+Section: File Formats (5)
Updated: @DATE@
Index +Return to Main Contents

+ + +

NAME

+ +stapprobes.scsi - systemtap scsi probe points +

+ + + +

+ +

DESCRIPTION

+ +

+This family of probe points is used to probe the SCSI activities. +It contains the following probe points: +

+ +

scsi.ioentry + +

+Fires when SCSI mid layer prepares a SCSI request +

+Arguments: + +

+disk_major + +
The major number of the disk +

+disk_minor + +
The minor number of the disk +

+device_state + +
The current state of the device. The possible values could be: +

+
        SDEV_CREATED = 1,    /* device created but not added to sysfs +
                              * Only internal commands allowed (for inq) */ +
        SDEV_RUNNING = 2,    /* device properly configured +
                              * All commands allowed */ +
        SDEV_CANCEL = 3,     /* beginning to delete device +
                              * Only error handler commands allowed */ +
        SDEV_DEL = 4,        /* device deleted +
                              * no commands allowed */ +
        SDEV_QUIESCE = 5,    /* Device quiescent.  No block commands +
                              * will be accepted, only specials (which +
                              * originate in the mid-layer) */ +
        SDEV_OFFLINE = 6,    /* Device offlined (by error handling or +
                              * user request */ +
        SDEV_BLOCK = 7,      /* Device blocked by scsi lld.  No scsi +
                              * commands from user or midlayer should be issued +
                              * to the scsi lld. */ +

+ +

scsi.iodispatching + +

+Fires when the SCSI mid layer dispatches a SCSI command to the low level driver +

+Arguments: + +

+host_no + +
The host number +

+channel + +
The channel number +

+lun + +
The lun number +

+dev_id + +
The scsi device id +

+device_state + +
The current state of the device. +

+data_direction + +
The data_direction specifies whether this command is from/to the device. +
The possible values could be: +

+
        DMA_BIDIRECTIONAL = 0, +
        DMA_TO_DEVICE = 1, +
        DMA_FROM_DEVICE = 2, +
        DMA_NONE = 3, +

+request_buffer + +
The request buffer address +

+req_bufflen + +
The request buffer length +

+ +

scsi.iodone + +

+Fires when a SCSI command is done by low level driver and enqueued into the done queue. +

+Arguments: + +

+host_no + +
The host number +

+channel + +
The channel number +

+lun + +
The lun number +

+dev_id + +
The scsi device id +

+device_state + +
The current state of the device +

+data_direction + +
The data_direction specifies whether this command is from/to the device. +

+ +

scsi.iocompleted + +

+Fires when SCSI mid layer runs the completion processing for +block device I/O requests +

+Arguments: + +

+host_no + +
The host number +

+channel + +
The channel number +

+lun + +
The lun number +

+dev_id + +
The scsi device id +

+device_state + +
The current state of the device +

+data_direction + +
The data_direction specifies whether this command is from/to the device. +

+goodbytes + +
The bytes completed. +

+ +

Index

NAME: +
DESCRIPTION: +
SEE ALSO: +

+This document was created by +man2html, +using the manual pages.
+Time: 06:28:19 GMT, October 18, 2006 + + diff --git a/man5/stapprobes.signal.5.html b/man5/stapprobes.signal.5.html new file mode 100644 index 00000000..d5e58c10 --- /dev/null +++ b/man5/stapprobes.signal.5.html @@ -0,0 +1,663 @@ +Content-type: text/html + +Manpage of STAPPROBES.SIGNAL + +

STAPPROBES.SIGNAL

+Section: File Formats (5)
Updated: @DATE@
Index +Return to Main Contents

+ + +

NAME

+ +stapprobes.signal - systemtap signal probe points +

+ + + +

+ +

DESCRIPTION

+ +

+This family of probe points is used to probe signal activities. +It contains the following probe points: +

+ +

signal.send + +

+Fires when a signal is sent to a process +

+Arguments: + +

+sig + +
signal number +

+sig_name + +
a string representation of the signal +

+sig_pid + +
pid of the signal recipient process +

+pid_name + +
name of the signal recipient process +

+si_code + +
indicates the signal type +

+task + +
a task handle to the signal recipient +

+sinfo + +
the address of siginfo struct +

+shared + +
indicates whether this signal is shared by the thread group +

+send2queue + +
indicates whether this signal is sent to an existing sigqueue +

+name + +
name of the function used to send out this signal +

+ +

signal.send.return + +

+Fires when return from sending a signal +

+Arguments: + +

+retstr + +
the return value +

+
Return values for "__group_send_sig_info" and "specific_send_sig_info" +

+- return 0 if the signal is sucessfully sent to a process, +which means the following: +

+<1> the signal is ignored by receiving process +

+<2> this is a non-RT signal and we already have one queued +

+<3> the signal is successfully added into the sigqueue of receiving process +

+- return -EAGAIN if the sigqueue is overflow the signal was RT and sent +by user using something other than kill() +

+ +

+
Return values for "send_group_sigqueue" +

: +- return 0 if the signal is either sucessfully added into the +sigqueue of receiving process or a SI_TIMER entry is already +queued so just increment the overrun count +
+- return 1 if this signal is ignored by receiving process +

+ +

+
Return values for "send_sigqueue" +

+- return 0 if the signal is either sucessfully added into the +sigqueue of receiving process or a SI_TIMER entry is already +queued so just increment the overrun count +

+- return 1 if this signal is ignored by receiving process +

+- return -1 if the task is marked exiting, so posix_timer_event +can redirect it to the group leader +

+ +

+shared + +
indicates whether this signal is shared by the thread group +

+send2queue + +
indicates whether this signal is sent to an existing sigqueue +

+name + +
name of the function used to send out this signal +

+ + + +

signal.checkperm + +

+Fires when check permissions for sending the signal +

+Arguments: + +

+sig + +
the number of the signal +

+sig_name + +
a string representation of the signal +

+sig_pid + +
pid of the signal recipient process +

+pid_name + +
name of the signal recipient process +

+si_code + +
indicates the signal type +

+task + +
a task handle to the signal recipient +

+sinfo + +
the address of siginfo struct +

+name + +
name of the probe point, is set to "signal.checkperm" +

+ +

signal.checkperm.return + +

+Fires when return from permissions check for sending a signal +

+Arguments: + +

+retstr + +
the return value +

+name + +
name of the probe point, is set to "signal.checkperm" +

+ +

signal.wakeup + +

+Fires when wake up the process for new active signals +

+Arguments: + +

+sig_pid + +
pid of the process to be woke up +

+pid_name + +
name of the process to be woke up +

+resume + +
indicate whether to wake up a task in STOPPED or TRACED state +

+state_mask + +
a string representation indicate the mask of task states +that can be woken. Possible values are +(TASK_INTERRUPTIBLE|TASK_STOPPED|TASK_TRACED) and +TASK_INTERRUPTIBLE. +

+ +

signal.check_ignored + +

+Fires when check whether the signal is ignored or not +

+Arguments: + +

+sig_pid + +
pid of the signal recipient process +

+pid_name + +
name of the signal recipient process +

+sig + +
the signal to be checked +

+sig_name + +
name of the signal +

+ +

signal.check_ignored.return + +

+Fires when return from signal.check_ignored +

+Arguments: + +

+retstr + +
return value. 0 indicate the current signal isn't ignored. +

+ +

signal.force_segv + +

+Forces SIGSEGV when there are some issues while handling +signals for the process +

+Arguments: + +

+sig_pid + +
pid of the signal recipient process +

+pid_name + +
name of the signal recipient process +

+sig + +
the signal being handled +

+sig_name + +
name of this signal +

+ +

signal.force_segv.return + +

+Fires when return from signal.force_segv +

+Arguments: + +

+retstr + +
return value. Always return 0 +

+ +

signal.syskill + +

+Fires when sys_kill is called to send a signal to a process. +

+Arguments: + +

+pid + +
pid of the recipient process +

+sig + +
the signal to be sent +

+ +

signal.syskill.return + +

+Fires when returning from sys_kill +

+ +

signal.tgkill + +

+Fires when sys_tgkill is called to send a signal to one specific thread +

+Arguments: + +

+pid + +
pid of the recipient thread +

+tgid + +
thread group id which the target thread should have +

+sig + +
the signal to be sent +

+ +

signal.tgkill.return + +

+Fires when returning from sys_tgkill +

+ +

signal.tkill + +

+Fires when sys_tkill is called to send a signal to a single process. +

+Arguments: + +

+pid + +
pid of the recipient process +

+sig + +
the signal to be sent +

+ +

signal.tkill.return + +

+Fires when returning from sys_tkill +

+ +

signal.send_sig_queue + +

+Fires when queue a signal to a process +

+Arguments: + +

+sig + +
the signal to be queued +

+sig_name + +
name of this signal +

+sig_pid + +
pid of the process to which the signal is queued +

+pid_name + +
name of the process to which the signal is queued +

+sigqueue_addr + +
address of the signal queue +

+ +

signal.send_sig_queue.return + +

+Fires when return from signal.send_sig_queue +

+Arguments: + +

+retstr + +
return value +

+ +

signal.pending + +

+Fires when examine the set of signals that are +pending for delivery to the calling thread +

+Arguments: + +

+sigset_add + +
address of user space sigset_t +

+sigset_size + +
sigset size +

+ +

signal.pending.return + +

+Fires when return from signal.pending +

+Arguments: + +

+retstr + +
return value +

+ +

signal.handle + +

+Fires when invoking the signal handler +

+Arguments: + +

+sig + +
signal number +

+sig_name + +
signal name +

+sinfo + +
address of siginfo struct +

+sig_code + +
the si_code of siginfo +

+ka_addr + +
Address of the k_sigaction struct associated with the signal +

+oldset_addr + +
Address of a bit mask array of blocked signals +

+sig_mode + +
indicates whether the signal is a User Mode or Kernel mode Signal +

+ +

signal.handle.return + +

+Fires when return from signal.handle +

+Arguments: + +

+retstr + +
return value of handle_signal() +

+ +

signal.do_action + +

+Fires by calling thread to examine and change a signal action +
+Arguments: + +

+sig + +
signal number +

+sigact_addr + +
address of the new sigaction struct associated with the signal +

+oldsigact_addr + +
address of a previous sigaction struct associated with the signal +

+sa_handler + +
the new handler of the signal +

+sa_mask + +
the new mask of the signal +

+ +

signal.do_action.return + +

+Fires when return from signal.do_action +

+Arguments: + +

+retstr + +
return value of do_sigaction() +

+ +

signal.procmask + +

+Fires by calling thread to examine and change blocked signals +

+Arguments: + +

+how + +
  indicates how to change the blocked signals. +
  Possible values are: +
    SIG_BLOCK=0 for blocking signals +
    SIG_UNBLOCK=1 for unblocking signals +
    SIG_SETMASK=2 for setting the signal mask +

+sigset_addr + +
address of sigset_t to be set +

+oldsigset_addr + +
address of the old sigset_t +

+sigset + +
the actual sigset to be set +

+ +

signal.procmask.return + +

+Fires when return from signal.procmask +

+Arguments: + +

+retstr + +
return value of sigprocmask() +

+ +

signal.flush + +

+Fires when flush all pending signals for a task +

+Arguments: + +

+task + +
the task handler of the process +

+sig_pid + +
pid of the task +

+pid_name + +
name of the task +

+ +

Index

NAME: +
DESCRIPTION: +
SEE ALSO: +

+This document was created by +man2html, +using the manual pages.
+Time: 06:28:19 GMT, October 18, 2006 + + diff --git a/man5/stapprobes.tcp.5.html b/man5/stapprobes.tcp.5.html new file mode 100644 index 00000000..cbdfea74 --- /dev/null +++ b/man5/stapprobes.tcp.5.html @@ -0,0 +1,148 @@ +Content-type: text/html + +Manpage of STAPPROBES.TCP + +

STAPPROBES.TCP

+Section: File Formats (5)
Updated: @DATE@
Index +Return to Main Contents

+ + +

NAME

+ +stapprobes.tcp - systemtap tcp probe points +

+ + + +

+ +

DESCRIPTION

+ +

+This family of probe points is used to probe TCP layer activities. +It contains the following probe points: +

+ +

tcp.sendmsg + +

+Fires whenever sending a tcp message +

+Arguments: + +

+sock + +
network socket +

+size + +
number of bytes to send +

+ +

tcp.sendmsg.return + +

+Fires whenever sending message is done +

+Arguments: + +

+size + +
number of bytes sent +

+ +

tcp.recvmsg + +

+Fires whenever a message is received +

+Arguments: + +

+sock + +
network socket +

+size + +
number of bytes to be received +

+ +

tcp.recvmsg.return + +

+Fires whenever message receiving is done +

+Arguments: + +

+size + +
number of bytes received +

+ +

tcp.disconnect + +

+Fires whenever tcp is disconnected +

+Arguments: + +

+sock + +
network socket +

+flags + +
TCP flags (e.g. FIN, etc) +

+ +

tcp.disconnect.return + +

+Fires when returning from tcp.disconnect +

+Arguments: + +

+ret + +
error code (0: no error) +

+ +

Index

NAME: +
DESCRIPTION: +
SEE ALSO: +

+This document was created by +man2html, +using the manual pages.
+Time: 06:28:19 GMT, October 18, 2006 + + diff --git a/man5/stapprobes.udp.5.html b/man5/stapprobes.udp.5.html new file mode 100644 index 00000000..3d59b492 --- /dev/null +++ b/man5/stapprobes.udp.5.html @@ -0,0 +1,148 @@ +Content-type: text/html + +Manpage of STAPPROBES.UDP + +

STAPPROBES.UDP

+Section: File Formats (5)
Updated: @DATE@
Index +Return to Main Contents

+ + +

NAME

+ +stapprobes.udp - systemtap udp probe points +

+ + + +

+ +

DESCRIPTION

+ +

+This family of probe points is used to probe UDP layer activities. +It contains the following probe points: +

+ +

udp.sendmsg + +

+Fires whenever sending a udp message +

+Arguments: + +

+sock + +
network socket +

+size + +
number of bytes to send +

+ +

udp.sendmsg.return + +

+Fires whenever sending message is done +

+Arguments: + +

+size + +
number of bytes sent +

+ +

udp.recvmsg + +

+Fires whenever a message is received +

+Arguments: + +

+sock + +
network socket +

+size + +
number of bytes to be received +

+ +

udp.recvmsg.return + +

+Fires whenever message receiving is done +

+Arguments: + +

+size + +
number of bytes received +

+ +

udp.disconnect + +

+Fires whenever udp is disconnected +

+Arguments: + +

+sock + +
network socket +

+flags + +
flags (e.g. FIN, etc) +

+ +

udp.disconnect.return + +

+Fires when returning from udp.disconnect +

+Arguments: + +

+ret + +
error code (0: no error) +

+ +

Index

NAME: +
DESCRIPTION: +
SEE ALSO: +

+This document was created by +man2html, +using the manual pages.
+Time: 06:28:19 GMT, October 18, 2006 + + -- 2.43.5

Older Stuff

IO SCHEDULER

SCSI

PERFORMANCE MONITORING HARDWARE

NETWORK DEVICE

PAGE FAULT

PROCESS

TCP

UDP

EXAMPLES

SEE ALSO

STAPPROBES.IOSCHED

NAME

DESCRIPTION

SEE ALSO

Index

STAPPROBES.NETDEV

NAME

DESCRIPTION

SEE ALSO

Index

STAPPROBES.NFS

NAME

DESCRIPTION

SEE ALSO

Index

STAPPROBES.NFSD

NAME

DESCRIPTION

SEE ALSO

Index

STAPPROBES.PAGEFAULT

NAME

DESCRIPTION

SEE ALSO

Index

STAPPROBES.PROCESS

NAME

DESCRIPTION

SEE ALSO

Index

STAPPROBES.RPC

NAME

DESCRIPTION

SEE ALSO

Index

STAPPROBES.SCSI

NAME

DESCRIPTION

SEE ALSO

Index

STAPPROBES.SIGNAL

NAME

DESCRIPTION

SEE ALSO

Index

STAPPROBES.TCP

NAME

DESCRIPTION

SEE ALSO

Index

STAPPROBES.UDP

NAME

DESCRIPTION

SEE ALSO

Index