--- /srv/reproducible-results/rbuild-debian/r-b-build.otFWAbm2/b1/systemtap_5.3-1_amd64.changes +++ /srv/reproducible-results/rbuild-debian/r-b-build.otFWAbm2/b2/systemtap_5.3-1_amd64.changes ├── Files │ @@ -1,11 +1,11 @@ │ │ 7d2a1441315e90ca8c0f0c247168b1bd 8776 devel optional systemtap-client_5.3-1_amd64.deb │ 4fbd8990aa2d5e3a5237747a04782762 642248 devel optional systemtap-common_5.3-1_amd64.deb │ 36e830be0d4ef856281059841ca8dacb 23025200 debug optional systemtap-dbgsym_5.3-1_amd64.deb │ - 1080d6be3cd82daba3cd752a2f767993 2591076 doc optional systemtap-doc_5.3-1_amd64.deb │ + 01b468482a50cfd4ddbd0165e1054b4e 2591048 doc optional systemtap-doc_5.3-1_amd64.deb │ 36fb7bfb34707e8da9c676359b486a04 1285704 debug optional systemtap-runtime-dbgsym_5.3-1_amd64.deb │ ce819da367cf3b8cf513ffd1b2f45e3d 150228 devel optional systemtap-runtime_5.3-1_amd64.deb │ 3e16e44ebf5f5bdd1b01ec665bc9e44b 19260 devel optional systemtap-sdt-dev_5.3-1_amd64.deb │ 1b386a4ee837f0b98d652aafb73f2eca 2137368 debug optional systemtap-server-dbgsym_5.3-1_amd64.deb │ 53980cc0228b864adffd7ca802e61a2e 165396 devel optional systemtap-server_5.3-1_amd64.deb │ f1138942ff5876d8832bba194bfb4f84 1580520 devel optional systemtap_5.3-1_amd64.deb ├── systemtap-doc_5.3-1_amd64.deb │ ├── file list │ │ @@ -1,3 +1,3 @@ │ │ -rw-r--r-- 0 0 0 4 2025-09-09 10:48:01.000000 debian-binary │ │ --rw-r--r-- 0 0 0 54368 2025-09-09 10:48:01.000000 control.tar.xz │ │ --rw-r--r-- 0 0 0 2536516 2025-09-09 10:48:01.000000 data.tar.xz │ │ +-rw-r--r-- 0 0 0 54372 2025-09-09 10:48:01.000000 control.tar.xz │ │ +-rw-r--r-- 0 0 0 2536484 2025-09-09 10:48:01.000000 data.tar.xz │ ├── control.tar.xz │ │ ├── control.tar │ │ │ ├── ./md5sums │ │ │ │ ├── ./md5sums │ │ │ │ │┄ Files differ │ ├── data.tar.xz │ │ ├── data.tar │ │ │ ├── file list │ │ │ │ @@ -217,15 +217,15 @@ │ │ │ │ -rw-r--r-- 0 root (0) root (0) 2252 2025-09-09 10:48:01.000000 ./usr/share/doc/systemtap-doc/tapsets/API-asmlinkage.html │ │ │ │ -rw-r--r-- 0 root (0) root (0) 2942 2025-09-09 10:48:01.000000 ./usr/share/doc/systemtap-doc/tapsets/API-assert.html │ │ │ │ -rw-r--r-- 0 root (0) root (0) 2660 2025-09-09 10:48:01.000000 ./usr/share/doc/systemtap-doc/tapsets/API-atomic-long-read.html │ │ │ │ -rw-r--r-- 0 root (0) root (0) 2534 2025-09-09 10:48:01.000000 ./usr/share/doc/systemtap-doc/tapsets/API-atomic-read.html │ │ │ │ -rw-r--r-- 0 root (0) root (0) 2363 2025-09-09 10:48:01.000000 ./usr/share/doc/systemtap-doc/tapsets/API-backtrace.html │ │ │ │ -rw-r--r-- 0 root (0) root (0) 2892 2025-09-09 10:48:01.000000 ./usr/share/doc/systemtap-doc/tapsets/API-bytes-to-string.html │ │ │ │ -rw-r--r-- 0 root (0) root (0) 2160 2025-09-09 10:48:01.000000 ./usr/share/doc/systemtap-doc/tapsets/API-caller-addr.html │ │ │ │ --rw-r--r-- 0 root (0) root (0) 2478 2025-09-09 10:48:01.000000 ./usr/share/doc/systemtap-doc/tapsets/API-caller.html │ │ │ │ +-rw-r--r-- 0 root (0) root (0) 2412 2025-09-09 10:48:01.000000 ./usr/share/doc/systemtap-doc/tapsets/API-caller.html │ │ │ │ -rw-r--r-- 0 root (0) root (0) 2593 2025-09-09 10:48:01.000000 ./usr/share/doc/systemtap-doc/tapsets/API-callers.html │ │ │ │ -rw-r--r-- 0 root (0) root (0) 2570 2025-09-09 10:48:01.000000 ./usr/share/doc/systemtap-doc/tapsets/API-cmdline-arg.html │ │ │ │ -rw-r--r-- 0 root (0) root (0) 3110 2025-09-09 10:48:01.000000 ./usr/share/doc/systemtap-doc/tapsets/API-cmdline-args.html │ │ │ │ -rw-r--r-- 0 root (0) root (0) 2283 2025-09-09 10:48:01.000000 ./usr/share/doc/systemtap-doc/tapsets/API-cmdline-str.html │ │ │ │ -rw-r--r-- 0 root (0) root (0) 2497 2025-09-09 10:48:01.000000 ./usr/share/doc/systemtap-doc/tapsets/API-commit.html │ │ │ │ -rw-r--r-- 0 root (0) root (0) 2529 2025-09-09 10:48:01.000000 ./usr/share/doc/systemtap-doc/tapsets/API-cpu-clock-ms.html │ │ │ │ -rw-r--r-- 0 root (0) root (0) 2569 2025-09-09 10:48:01.000000 ./usr/share/doc/systemtap-doc/tapsets/API-cpu-clock-ns.html │ │ │ │ @@ -336,15 +336,15 @@ │ │ │ │ -rw-r--r-- 0 root (0) root (0) 2628 2025-09-09 10:48:01.000000 ./usr/share/doc/systemtap-doc/tapsets/API-isinstr.html │ │ │ │ -rw-r--r-- 0 root (0) root (0) 2376 2025-09-09 10:48:01.000000 ./usr/share/doc/systemtap-doc/tapsets/API-jiffies.html │ │ │ │ -rw-r--r-- 0 root (0) root (0) 3184 2025-09-09 10:48:01.000000 ./usr/share/doc/systemtap-doc/tapsets/API-json-add-array-numeric-metric.html │ │ │ │ -rw-r--r-- 0 root (0) root (0) 3050 2025-09-09 10:48:01.000000 ./usr/share/doc/systemtap-doc/tapsets/API-json-add-array-string-metric.html │ │ │ │ -rw-r--r-- 0 root (0) root (0) 2792 2025-09-09 10:48:01.000000 ./usr/share/doc/systemtap-doc/tapsets/API-json-add-array.html │ │ │ │ -rw-r--r-- 0 root (0) root (0) 2933 2025-09-09 10:48:01.000000 ./usr/share/doc/systemtap-doc/tapsets/API-json-add-numeric-metric.html │ │ │ │ -rw-r--r-- 0 root (0) root (0) 2704 2025-09-09 10:48:01.000000 ./usr/share/doc/systemtap-doc/tapsets/API-json-add-string-metric.html │ │ │ │ --rw-r--r-- 0 root (0) root (0) 2864 2025-09-09 10:48:01.000000 ./usr/share/doc/systemtap-doc/tapsets/API-json-data.html │ │ │ │ +-rw-r--r-- 0 root (0) root (0) 2930 2025-09-09 10:48:01.000000 ./usr/share/doc/systemtap-doc/tapsets/API-json-data.html │ │ │ │ -rw-r--r-- 0 root (0) root (0) 3317 2025-09-09 10:48:01.000000 ./usr/share/doc/systemtap-doc/tapsets/API-json-output-array-numeric-value.html │ │ │ │ -rw-r--r-- 0 root (0) root (0) 3329 2025-09-09 10:48:01.000000 ./usr/share/doc/systemtap-doc/tapsets/API-json-output-array-string-value.html │ │ │ │ -rw-r--r-- 0 root (0) root (0) 2448 2025-09-09 10:48:01.000000 ./usr/share/doc/systemtap-doc/tapsets/API-json-output-data-end.html │ │ │ │ -rw-r--r-- 0 root (0) root (0) 2426 2025-09-09 10:48:01.000000 ./usr/share/doc/systemtap-doc/tapsets/API-json-output-data-start.html │ │ │ │ -rw-r--r-- 0 root (0) root (0) 2873 2025-09-09 10:48:01.000000 ./usr/share/doc/systemtap-doc/tapsets/API-json-output-numeric-value.html │ │ │ │ -rw-r--r-- 0 root (0) root (0) 2802 2025-09-09 10:48:01.000000 ./usr/share/doc/systemtap-doc/tapsets/API-json-output-string-value.html │ │ │ │ -rw-r--r-- 0 root (0) root (0) 2738 2025-09-09 10:48:01.000000 ./usr/share/doc/systemtap-doc/tapsets/API-json-set-prefix.html │ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-caller.html │ │ │ │ @@ -3,9 +3,9 @@ │ │ │ │

Synopsis

│ │ │ │      caller:string()
│ │ │ │

Arguments

│ │ │ │ None │ │ │ │

Description

│ │ │ │ This function returns the address and name of the │ │ │ │ calling function. This is equivalent to calling: │ │ │ │ - sprintf(“s 0xx”, symname(caller_addr), caller_addr) │ │ │ │ + sprintf("s 0xx", symname(caller_addr), caller_addr) │ │ │ │

Prev Up Next
function::backtrace Home function::caller_addr
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-ioblock-end.html │ │ │ │ @@ -1,41 +1,41 @@ │ │ │ │ probe::ioblock.end
probe::ioblock.end
Prev Chapter 9. IO Scheduler and block IO Tapset Next

Name

probe::ioblock.end — │ │ │ │ Fires whenever a block I/O transfer is complete. │ │ │ │ -

Synopsis

ioblock.end

Values

bytes_done

│ │ │ │ - number of bytes transferred │ │ │ │ +

Synopsis

ioblock.end

Values

name

│ │ │ │ + name of the probe point │ │ │ │ +

opf

│ │ │ │ + operations and flags │ │ │ │ +

idx

│ │ │ │ + offset into the bio vector array │ │ │ │ +

size

│ │ │ │ + total size in bytes │ │ │ │ +

error

│ │ │ │ + 0 on success │ │ │ │ +

vcnt

│ │ │ │ + bio vector count which represents number of array element (page, offset, length) which makes up this I/O request │ │ │ │ +

ino

│ │ │ │ + i-node number of the mapped file │ │ │ │ +

phys_segments

│ │ │ │ + number of segments in this bio after physical address coalescing is performed. │ │ │ │

flags

│ │ │ │ see below │ │ │ │ BIO_UPTODATE 0 ok after I/O completion │ │ │ │ BIO_RW_BLOCK 1 RW_AHEAD set, and read/write would block │ │ │ │ BIO_EOF 2 out-out-bounds error │ │ │ │ BIO_SEG_VALID 3 nr_hw_seg valid │ │ │ │ BIO_CLONED 4 doesn't own data │ │ │ │ BIO_BOUNCED 5 bio is a bounce bio │ │ │ │ BIO_USER_MAPPED 6 contains user pages │ │ │ │ BIO_EOPNOTSUPP 7 not supported │ │ │ │ -

idx

│ │ │ │ - offset into the bio vector array │ │ │ │ -

size

│ │ │ │ - total size in bytes │ │ │ │ -

error

│ │ │ │ - 0 on success │ │ │ │

rw

│ │ │ │ binary trace for read/write request │ │ │ │ -

sector

│ │ │ │ - beginning sector for the entire bio │ │ │ │ -

opf

│ │ │ │ - operations and flags │ │ │ │ +

bytes_done

│ │ │ │ + number of bytes transferred │ │ │ │

devname

│ │ │ │ block device name │ │ │ │ -

ino

│ │ │ │ - i-node number of the mapped file │ │ │ │ -

vcnt

│ │ │ │ - bio vector count which represents number of array element (page, offset, length) which makes up this I/O request │ │ │ │ -

phys_segments

│ │ │ │ - number of segments in this bio after physical address coalescing is performed. │ │ │ │ -

name

│ │ │ │ - name of the probe point │ │ │ │ +

sector

│ │ │ │ + beginning sector for the entire bio │ │ │ │

hw_segments

│ │ │ │ number of segments after physical and DMA remapping hardware coalescing is performed │ │ │ │

Context

│ │ │ │ The process signals the transfer is done. │ │ │ │

Prev Up Next
Chapter 9. IO Scheduler and block IO Tapset Home probe::ioblock.request
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-ioblock-request.html │ │ │ │ @@ -1,43 +1,43 @@ │ │ │ │ probe::ioblock.request
probe::ioblock.request
Prev Chapter 9. IO Scheduler and block IO Tapset Next

Name

probe::ioblock.request — │ │ │ │ Fires whenever making a generic block I/O request. │ │ │ │ -

Synopsis

ioblock.request

Values

idx

│ │ │ │ - offset into the bio vector array │ │ │ │ -

size

│ │ │ │ - total size in bytes │ │ │ │ +

Synopsis

ioblock.request

Values

hw_segments

│ │ │ │ + number of segments after physical and DMA remapping hardware coalescing is performed │ │ │ │

rw

│ │ │ │ binary trace for read/write request │ │ │ │ -

bdev_contains

│ │ │ │ - points to the device object which contains the partition (when bio structure represents a partition) │ │ │ │ +

devname

│ │ │ │ + block device name │ │ │ │ +

sector

│ │ │ │ + beginning sector for the entire bio │ │ │ │

flags

│ │ │ │ see below │ │ │ │ BIO_UPTODATE 0 ok after I/O completion │ │ │ │ BIO_RW_BLOCK 1 RW_AHEAD set, and read/write would block │ │ │ │ BIO_EOF 2 out-out-bounds error │ │ │ │ BIO_SEG_VALID 3 nr_hw_seg valid │ │ │ │ BIO_CLONED 4 doesn't own data │ │ │ │ BIO_BOUNCED 5 bio is a bounce bio │ │ │ │ BIO_USER_MAPPED 6 contains user pages │ │ │ │ BIO_EOPNOTSUPP 7 not supported │ │ │ │ -

bdev

│ │ │ │ - target block device │ │ │ │ -

sector

│ │ │ │ - beginning sector for the entire bio │ │ │ │ -

opf

│ │ │ │ - operations and flags │ │ │ │ +

bdev_contains

│ │ │ │ + points to the device object which contains the partition (when bio structure represents a partition) │ │ │ │ +

phys_segments

│ │ │ │ + number of segments in this bio after physical address coalescing is performed │ │ │ │

p_start_sect

│ │ │ │ points to the start sector of the partition structure of the device │ │ │ │ -

devname

│ │ │ │ - block device name │ │ │ │ -

vcnt

│ │ │ │ - bio vector count which represents number of array element (page, offset, length) which make up this I/O request │ │ │ │

ino

│ │ │ │ i-node number of the mapped file │ │ │ │ +

bdev

│ │ │ │ + target block device │ │ │ │ +

size

│ │ │ │ + total size in bytes │ │ │ │ +

vcnt

│ │ │ │ + bio vector count which represents number of array element (page, offset, length) which make up this I/O request │ │ │ │ +

idx

│ │ │ │ + offset into the bio vector array │ │ │ │

name

│ │ │ │ name of the probe point │ │ │ │ -

hw_segments

│ │ │ │ - number of segments after physical and DMA remapping hardware coalescing is performed │ │ │ │ -

phys_segments

│ │ │ │ - number of segments in this bio after physical address coalescing is performed │ │ │ │ +

opf

│ │ │ │ + operations and flags │ │ │ │

Context

│ │ │ │ The process makes block I/O request │ │ │ │

Prev Up Next
probe::ioblock.end Home probe::ioblock_trace.bounce
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-ioblock-trace-bounce.html │ │ │ │ @@ -1,44 +1,44 @@ │ │ │ │ probe::ioblock_trace.bounce
probe::ioblock_trace.bounce
Prev Chapter 9. IO Scheduler and block IO Tapset Next

Name

probe::ioblock_trace.bounce — │ │ │ │ Fires whenever a buffer bounce is needed for at least one page of a block IO request. │ │ │ │ -

Synopsis

ioblock_trace.bounce

Values

bdev

│ │ │ │ +

Synopsis

ioblock_trace.bounce

Values

vcnt

│ │ │ │ + bio vector count which represents number of array element (page, offset, length) which makes up this I/O request │ │ │ │ +

size

│ │ │ │ + total size in bytes │ │ │ │ +

p_start_sect

│ │ │ │ + points to the start sector of the partition structure of the device │ │ │ │ +

bdev

│ │ │ │ target block device │ │ │ │ +

ino

│ │ │ │ + i-node number of the mapped file │ │ │ │ +

name

│ │ │ │ + name of the probe point │ │ │ │

opf

│ │ │ │ operations and flags │ │ │ │ -

sector

│ │ │ │ - beginning sector for the entire bio │ │ │ │ -

rw

│ │ │ │ - binary trace for read/write request │ │ │ │ -

size

│ │ │ │ - total size in bytes │ │ │ │

idx

│ │ │ │ offset into the bio vector array │ │ │ │ phys_segments - number of segments in this bio after physical address coalescing is performed. │ │ │ │ +

rw

│ │ │ │ + binary trace for read/write request │ │ │ │ +

devname

│ │ │ │ + device for which a buffer bounce was needed. │ │ │ │ +

bytes_done

│ │ │ │ + number of bytes transferred │ │ │ │ +

sector

│ │ │ │ + beginning sector for the entire bio │ │ │ │

flags

│ │ │ │ see below │ │ │ │ BIO_UPTODATE 0 ok after I/O completion │ │ │ │ BIO_RW_BLOCK 1 RW_AHEAD set, and read/write would block │ │ │ │ BIO_EOF 2 out-out-bounds error │ │ │ │ BIO_SEG_VALID 3 nr_hw_seg valid │ │ │ │ BIO_CLONED 4 doesn't own data │ │ │ │ BIO_BOUNCED 5 bio is a bounce bio │ │ │ │ BIO_USER_MAPPED 6 contains user pages │ │ │ │ BIO_EOPNOTSUPP 7 not supported │ │ │ │

bdev_contains

│ │ │ │ points to the device object which contains the partition (when bio structure represents a partition) │ │ │ │ -

bytes_done

│ │ │ │ - number of bytes transferred │ │ │ │

q

│ │ │ │ request queue on which this bio was queued. │ │ │ │ -

name

│ │ │ │ - name of the probe point │ │ │ │ -

p_start_sect

│ │ │ │ - points to the start sector of the partition structure of the device │ │ │ │ -

vcnt

│ │ │ │ - bio vector count which represents number of array element (page, offset, length) which makes up this I/O request │ │ │ │ -

ino

│ │ │ │ - i-node number of the mapped file │ │ │ │ -

devname

│ │ │ │ - device for which a buffer bounce was needed. │ │ │ │

Context

│ │ │ │ The process creating a block IO request. │ │ │ │

Prev Up Next
probe::ioblock.request Home probe::ioblock_trace.end
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-ioblock-trace-end.html │ │ │ │ @@ -1,44 +1,44 @@ │ │ │ │ probe::ioblock_trace.end
probe::ioblock_trace.end
Prev Chapter 9. IO Scheduler and block IO Tapset Next

Name

probe::ioblock_trace.end — │ │ │ │ Fires whenever a block I/O transfer is complete. │ │ │ │ -

Synopsis

ioblock_trace.end

Values

idx

│ │ │ │ - offset into the bio vector array │ │ │ │ - phys_segments - number of segments in this bio after physical address coalescing is performed. │ │ │ │ -

rw

│ │ │ │ - binary trace for read/write request │ │ │ │ +

Synopsis

ioblock_trace.end

Values

vcnt

│ │ │ │ + bio vector count which represents number of array element (page, offset, length) which makes up this I/O request │ │ │ │

size

│ │ │ │ total size in bytes │ │ │ │ -

q

│ │ │ │ - request queue on which this bio was queued. │ │ │ │ -

bytes_done

│ │ │ │ - number of bytes transferred │ │ │ │ +

ino

│ │ │ │ + i-node number of the mapped file │ │ │ │ +

bdev

│ │ │ │ + target block device │ │ │ │ +

p_start_sect

│ │ │ │ + points to the start sector of the partition structure of the device │ │ │ │ +

opf

│ │ │ │ + operations and flags │ │ │ │ +

name

│ │ │ │ + name of the probe point │ │ │ │ +

idx

│ │ │ │ + offset into the bio vector array │ │ │ │ + phys_segments - number of segments in this bio after physical address coalescing is performed. │ │ │ │

flags

│ │ │ │ see below │ │ │ │ BIO_UPTODATE 0 ok after I/O completion │ │ │ │ BIO_RW_BLOCK 1 RW_AHEAD set, and read/write would block │ │ │ │ BIO_EOF 2 out-out-bounds error │ │ │ │ BIO_SEG_VALID 3 nr_hw_seg valid │ │ │ │ BIO_CLONED 4 doesn't own data │ │ │ │ BIO_BOUNCED 5 bio is a bounce bio │ │ │ │ BIO_USER_MAPPED 6 contains user pages │ │ │ │ BIO_EOPNOTSUPP 7 not supported │ │ │ │ -

bdev_contains

│ │ │ │ - points to the device object which contains the partition (when bio structure represents a partition) │ │ │ │ -

bdev

│ │ │ │ - target block device │ │ │ │

sector

│ │ │ │ beginning sector for the entire bio │ │ │ │ -

opf

│ │ │ │ - operations and flags │ │ │ │ -

p_start_sect

│ │ │ │ - points to the start sector of the partition structure of the device │ │ │ │ +

rw

│ │ │ │ + binary trace for read/write request │ │ │ │ +

bytes_done

│ │ │ │ + number of bytes transferred │ │ │ │

devname

│ │ │ │ block device name │ │ │ │ -

ino

│ │ │ │ - i-node number of the mapped file │ │ │ │ -

vcnt

│ │ │ │ - bio vector count which represents number of array element (page, offset, length) which makes up this I/O request │ │ │ │ -

name

│ │ │ │ - name of the probe point │ │ │ │ +

q

│ │ │ │ + request queue on which this bio was queued. │ │ │ │ +

bdev_contains

│ │ │ │ + points to the device object which contains the partition (when bio structure represents a partition) │ │ │ │

Context

│ │ │ │ The process signals the transfer is done. │ │ │ │

Prev Up Next
probe::ioblock_trace.bounce Home probe::ioblock_trace.request
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-ioblock-trace-request.html │ │ │ │ @@ -1,44 +1,44 @@ │ │ │ │ probe::ioblock_trace.request
probe::ioblock_trace.request
Prev Chapter 9. IO Scheduler and block IO Tapset Next

Name

probe::ioblock_trace.request — │ │ │ │ Fires just as a generic block I/O request is created for a bio. │ │ │ │ -

Synopsis

ioblock_trace.request

Values

q

│ │ │ │ - request queue on which this bio was queued. │ │ │ │ +

Synopsis

ioblock_trace.request

Values

size

│ │ │ │ + total size in bytes │ │ │ │ +

vcnt

│ │ │ │ + bio vector count which represents number of array element (page, offset, length) which make up this I/O request │ │ │ │ +

p_start_sect

│ │ │ │ + points to the start sector of the partition structure of the device │ │ │ │ +

bdev

│ │ │ │ + target block device │ │ │ │ +

ino

│ │ │ │ + i-node number of the mapped file │ │ │ │ +

name

│ │ │ │ + name of the probe point │ │ │ │ +

opf

│ │ │ │ + operations and flags │ │ │ │ +

idx

│ │ │ │ + offset into the bio vector array │ │ │ │ + phys_segments - number of segments in this bio after physical address coalescing is performed. │ │ │ │ +

rw

│ │ │ │ + binary trace for read/write request │ │ │ │ +

devname

│ │ │ │ + block device name │ │ │ │

bytes_done

│ │ │ │ number of bytes transferred │ │ │ │ -

bdev_contains

│ │ │ │ - points to the device object which contains the partition (when bio structure represents a partition) │ │ │ │ +

sector

│ │ │ │ + beginning sector for the entire bio │ │ │ │

flags

│ │ │ │ see below │ │ │ │ BIO_UPTODATE 0 ok after I/O completion │ │ │ │ BIO_RW_BLOCK 1 RW_AHEAD set, and read/write would block │ │ │ │ BIO_EOF 2 out-out-bounds error │ │ │ │ BIO_SEG_VALID 3 nr_hw_seg valid │ │ │ │ BIO_CLONED 4 doesn't own data │ │ │ │ BIO_BOUNCED 5 bio is a bounce bio │ │ │ │ BIO_USER_MAPPED 6 contains user pages │ │ │ │ BIO_EOPNOTSUPP 7 not supported │ │ │ │ -

idx

│ │ │ │ - offset into the bio vector array │ │ │ │ - phys_segments - number of segments in this bio after physical address coalescing is performed. │ │ │ │ -

size

│ │ │ │ - total size in bytes │ │ │ │ -

rw

│ │ │ │ - binary trace for read/write request │ │ │ │ -

opf

│ │ │ │ - operations and flags │ │ │ │ -

sector

│ │ │ │ - beginning sector for the entire bio │ │ │ │ -

bdev

│ │ │ │ - target block device │ │ │ │ -

ino

│ │ │ │ - i-node number of the mapped file │ │ │ │ -

vcnt

│ │ │ │ - bio vector count which represents number of array element (page, offset, length) which make up this I/O request │ │ │ │ -

devname

│ │ │ │ - block device name │ │ │ │ -

p_start_sect

│ │ │ │ - points to the start sector of the partition structure of the device │ │ │ │ -

name

│ │ │ │ - name of the probe point │ │ │ │ +

bdev_contains

│ │ │ │ + points to the device object which contains the partition (when bio structure represents a partition) │ │ │ │ +

q

│ │ │ │ + request queue on which this bio was queued. │ │ │ │

Context

│ │ │ │ The process makes block I/O request │ │ │ │

Prev Up Next
probe::ioblock_trace.end Home probe::ioscheduler.elv_add_request
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-ioscheduler-elv-add-request-kp.html │ │ │ │ @@ -1,17 +1,17 @@ │ │ │ │ probe::ioscheduler.elv_add_request.kp
probe::ioscheduler.elv_add_request.kp
Prev Chapter 9. IO Scheduler and block IO Tapset Next

Name

probe::ioscheduler.elv_add_request.kp — │ │ │ │ kprobe based probe to indicate that a request was added to the request queue │ │ │ │ -

Synopsis

ioscheduler.elv_add_request.kp

Values

q

│ │ │ │ - pointer to request queue │ │ │ │ -

rq_flags

│ │ │ │ - Request flags │ │ │ │ -

disk_minor

│ │ │ │ - Disk minor number of the request │ │ │ │ -

rq

│ │ │ │ +

Synopsis

ioscheduler.elv_add_request.kp

Values

rq

│ │ │ │ Address of the request │ │ │ │ -

disk_major

│ │ │ │ - Disk major number of the request │ │ │ │ +

q

│ │ │ │ + pointer to request queue │ │ │ │

elevator_name

│ │ │ │ The type of I/O elevator currently enabled │ │ │ │ +

disk_minor

│ │ │ │ + Disk minor number of the request │ │ │ │

name

│ │ │ │ Name of the probe point │ │ │ │ +

disk_major

│ │ │ │ + Disk major number of the request │ │ │ │ +

rq_flags

│ │ │ │ + Request flags │ │ │ │

Prev Up Next
probe::ioscheduler.elv_add_request Home probe::ioscheduler.elv_add_request.tp
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-ioscheduler-elv-add-request-tp.html │ │ │ │ @@ -1,17 +1,17 @@ │ │ │ │ probe::ioscheduler.elv_add_request.tp
probe::ioscheduler.elv_add_request.tp
Prev Chapter 9. IO Scheduler and block IO Tapset Next

Name

probe::ioscheduler.elv_add_request.tp — │ │ │ │ tracepoint based probe to indicate a request is added to the request queue. │ │ │ │ -

Synopsis

ioscheduler.elv_add_request.tp

Values

name

│ │ │ │ - Name of the probe point │ │ │ │ +

Synopsis

ioscheduler.elv_add_request.tp

Values

q

│ │ │ │ + Pointer to request queue. │ │ │ │

rq

│ │ │ │ Address of request. │ │ │ │

disk_major

│ │ │ │ Disk major no of request. │ │ │ │ -

elevator_name

│ │ │ │ - The type of I/O elevator currently enabled. │ │ │ │ -

disk_minor

│ │ │ │ - Disk minor number of request. │ │ │ │

rq_flags

│ │ │ │ Request flags. │ │ │ │ -

q

│ │ │ │ - Pointer to request queue. │ │ │ │ +

name

│ │ │ │ + Name of the probe point │ │ │ │ +

disk_minor

│ │ │ │ + Disk minor number of request. │ │ │ │ +

elevator_name

│ │ │ │ + The type of I/O elevator currently enabled. │ │ │ │

Prev Up Next
probe::ioscheduler.elv_add_request.kp Home probe::ioscheduler.elv_completed_request
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-ioscheduler-elv-add-request.html │ │ │ │ @@ -1,15 +1,15 @@ │ │ │ │ probe::ioscheduler.elv_add_request
probe::ioscheduler.elv_add_request
Prev Chapter 9. IO Scheduler and block IO Tapset Next

Name

probe::ioscheduler.elv_add_request — │ │ │ │ probe to indicate request is added to the request queue. │ │ │ │ -

Synopsis

ioscheduler.elv_add_request

Values

rq_flags

│ │ │ │ - Request flags. │ │ │ │ -

q

│ │ │ │ +

Synopsis

ioscheduler.elv_add_request

Values

q

│ │ │ │ Pointer to request queue. │ │ │ │ +

rq

│ │ │ │ + Address of request. │ │ │ │ +

rq_flags

│ │ │ │ + Request flags. │ │ │ │ +

disk_major

│ │ │ │ + Disk major no of request. │ │ │ │

disk_minor

│ │ │ │ Disk minor number of request. │ │ │ │

elevator_name

│ │ │ │ The type of I/O elevator currently enabled. │ │ │ │ -

disk_major

│ │ │ │ - Disk major no of request. │ │ │ │ -

rq

│ │ │ │ - Address of request. │ │ │ │

Prev Up Next
probe::ioblock_trace.request Home probe::ioscheduler.elv_add_request.kp
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-ioscheduler-elv-completed-request.html │ │ │ │┄ Ordering differences only │ │ │ │ @@ -1,15 +1,15 @@ │ │ │ │ probe::ioscheduler.elv_completed_request
probe::ioscheduler.elv_completed_request
Prev Chapter 9. IO Scheduler and block IO Tapset Next

Name

probe::ioscheduler.elv_completed_request — │ │ │ │ Fires when a request is completed │ │ │ │

Synopsis

ioscheduler.elv_completed_request

Values

rq

│ │ │ │ Address of the request │ │ │ │ -

elevator_name

│ │ │ │ - The type of I/O elevator currently enabled │ │ │ │

disk_major

│ │ │ │ Disk major number of the request │ │ │ │

rq_flags

│ │ │ │ Request flags │ │ │ │ -

disk_minor

│ │ │ │ - Disk minor number of the request │ │ │ │

name

│ │ │ │ Name of the probe point │ │ │ │ +

disk_minor

│ │ │ │ + Disk minor number of the request │ │ │ │ +

elevator_name

│ │ │ │ + The type of I/O elevator currently enabled │ │ │ │

Prev Up Next
probe::ioscheduler.elv_add_request.tp Home probe::ioscheduler.elv_next_request
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-ioscheduler-elv-next-request-return.html │ │ │ │┄ Ordering differences only │ │ │ │ @@ -1,13 +1,13 @@ │ │ │ │ probe::ioscheduler.elv_next_request.return
probe::ioscheduler.elv_next_request.return
Prev Chapter 9. IO Scheduler and block IO Tapset Next

Name

probe::ioscheduler.elv_next_request.return — │ │ │ │ Fires when a request retrieval issues a return signal │ │ │ │

Synopsis

ioscheduler.elv_next_request.return

Values

rq_flags

│ │ │ │ Request flags │ │ │ │

disk_major

│ │ │ │ Disk major number of the request │ │ │ │ -

rq

│ │ │ │ - Address of the request │ │ │ │ -

name

│ │ │ │ - Name of the probe point │ │ │ │

disk_minor

│ │ │ │ Disk minor number of the request │ │ │ │ +

name

│ │ │ │ + Name of the probe point │ │ │ │ +

rq

│ │ │ │ + Address of the request │ │ │ │

Prev Up Next
probe::ioscheduler.elv_next_request Home probe::ioscheduler_trace.elv_abort_request
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-ioscheduler-trace-elv-abort-request.html │ │ │ │ @@ -1,15 +1,15 @@ │ │ │ │ probe::ioscheduler_trace.elv_abort_request
probe::ioscheduler_trace.elv_abort_request
Prev Chapter 9. IO Scheduler and block IO Tapset Next

Name

probe::ioscheduler_trace.elv_abort_request — │ │ │ │ Fires when a request is aborted. │ │ │ │ -

Synopsis

ioscheduler_trace.elv_abort_request

Values

elevator_name

│ │ │ │ - The type of I/O elevator currently enabled. │ │ │ │ -

disk_major

│ │ │ │ - Disk major no of request. │ │ │ │ -

rq

│ │ │ │ +

Synopsis

ioscheduler_trace.elv_abort_request

Values

rq

│ │ │ │ Address of request. │ │ │ │

name

│ │ │ │ Name of the probe point │ │ │ │ -

rq_flags

│ │ │ │ - Request flags. │ │ │ │

disk_minor

│ │ │ │ Disk minor number of request. │ │ │ │ +

elevator_name

│ │ │ │ + The type of I/O elevator currently enabled. │ │ │ │ +

disk_major

│ │ │ │ + Disk major no of request. │ │ │ │ +

rq_flags

│ │ │ │ + Request flags. │ │ │ │

Prev Up Next
probe::ioscheduler.elv_next_request.return Home probe::ioscheduler_trace.elv_completed_request
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-ioscheduler-trace-elv-completed-request.html │ │ │ │ @@ -1,17 +1,17 @@ │ │ │ │ probe::ioscheduler_trace.elv_completed_request
probe::ioscheduler_trace.elv_completed_request
Prev Chapter 9. IO Scheduler and block IO Tapset Next

Name

probe::ioscheduler_trace.elv_completed_request — │ │ │ │ Fires when a request is │ │ │ │ -

Synopsis

ioscheduler_trace.elv_completed_request

Values

elevator_name

│ │ │ │ - The type of I/O elevator currently enabled. │ │ │ │ -

disk_major

│ │ │ │ - Disk major no of request. │ │ │ │ -

rq

│ │ │ │ +

Synopsis

ioscheduler_trace.elv_completed_request

Values

rq

│ │ │ │ Address of request. │ │ │ │ +

elevator_name

│ │ │ │ + The type of I/O elevator currently enabled. │ │ │ │ +

disk_minor

│ │ │ │ + Disk minor number of request. │ │ │ │

name

│ │ │ │ Name of the probe point │ │ │ │ +

disk_major

│ │ │ │ + Disk major no of request. │ │ │ │

rq_flags

│ │ │ │ Request flags. │ │ │ │ -

disk_minor

│ │ │ │ - Disk minor number of request. │ │ │ │

Description

│ │ │ │ completed. │ │ │ │

Prev Up Next
probe::ioscheduler_trace.elv_abort_request Home probe::ioscheduler_trace.elv_issue_request
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-ioscheduler-trace-elv-issue-request.html │ │ │ │ @@ -1,17 +1,17 @@ │ │ │ │ probe::ioscheduler_trace.elv_issue_request
probe::ioscheduler_trace.elv_issue_request
Prev Chapter 9. IO Scheduler and block IO Tapset Next

Name

probe::ioscheduler_trace.elv_issue_request — │ │ │ │ Fires when a request is │ │ │ │ -

Synopsis

ioscheduler_trace.elv_issue_request

Values

disk_minor

│ │ │ │ - Disk minor number of request. │ │ │ │ +

Synopsis

ioscheduler_trace.elv_issue_request

Values

rq

│ │ │ │ + Address of request. │ │ │ │

rq_flags

│ │ │ │ Request flags. │ │ │ │ -

name

│ │ │ │ - Name of the probe point │ │ │ │

disk_major

│ │ │ │ Disk major no of request. │ │ │ │

elevator_name

│ │ │ │ The type of I/O elevator currently enabled. │ │ │ │ -

rq

│ │ │ │ - Address of request. │ │ │ │ +

disk_minor

│ │ │ │ + Disk minor number of request. │ │ │ │ +

name

│ │ │ │ + Name of the probe point │ │ │ │

Description

│ │ │ │ scheduled. │ │ │ │

Prev Up Next
probe::ioscheduler_trace.elv_completed_request Home probe::ioscheduler_trace.elv_requeue_request
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-ioscheduler-trace-elv-requeue-request.html │ │ │ │ @@ -1,17 +1,17 @@ │ │ │ │ probe::ioscheduler_trace.elv_requeue_request
probe::ioscheduler_trace.elv_requeue_request
Prev Chapter 9. IO Scheduler and block IO Tapset Next

Name

probe::ioscheduler_trace.elv_requeue_request — │ │ │ │ Fires when a request is │ │ │ │ -

Synopsis

ioscheduler_trace.elv_requeue_request

Values

name

│ │ │ │ - Name of the probe point │ │ │ │ +

Synopsis

ioscheduler_trace.elv_requeue_request

Values

rq_flags

│ │ │ │ + Request flags. │ │ │ │

disk_major

│ │ │ │ Disk major no of request. │ │ │ │

elevator_name

│ │ │ │ The type of I/O elevator currently enabled. │ │ │ │ -

rq

│ │ │ │ - Address of request. │ │ │ │

disk_minor

│ │ │ │ Disk minor number of request. │ │ │ │ -

rq_flags

│ │ │ │ - Request flags. │ │ │ │ +

name

│ │ │ │ + Name of the probe point │ │ │ │ +

rq

│ │ │ │ + Address of request. │ │ │ │

Description

│ │ │ │ put back on the queue, when the hadware cannot accept more requests. │ │ │ │

Prev Up Next
probe::ioscheduler_trace.elv_issue_request Home probe::ioscheduler_trace.plug
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-ipmib-FragFails.html │ │ │ │ @@ -1,12 +1,12 @@ │ │ │ │ probe::ipmib.FragFails
probe::ipmib.FragFails
Prev Chapter 15. SNMP Information Tapset Next

Name

probe::ipmib.FragFails — │ │ │ │ Count datagram fragmented unsuccessfully │ │ │ │ -

Synopsis

ipmib.FragFails

Values

skb

│ │ │ │ - pointer to the struct sk_buff being acted on │ │ │ │ -

op

│ │ │ │ +

Synopsis

ipmib.FragFails

Values

op

│ │ │ │ Value to be added to the counter (default value of 1) │ │ │ │ +

skb

│ │ │ │ + pointer to the struct sk_buff being acted on │ │ │ │

Description

│ │ │ │ The packet pointed to by skb is filtered by the function │ │ │ │ ipmib_filter_key. If the packet passes the filter is is │ │ │ │ counted in the global FragFails (equivalent to SNMP's MIB │ │ │ │ IPSTATS_MIB_FRAGFAILS) │ │ │ │

Prev Up Next
probe::ipmib.ForwDatagrams Home probe::ipmib.FragOKs
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-ipmib-FragOKs.html │ │ │ │ @@ -1,12 +1,12 @@ │ │ │ │ probe::ipmib.FragOKs
probe::ipmib.FragOKs
Prev Chapter 15. SNMP Information Tapset Next

Name

probe::ipmib.FragOKs — │ │ │ │ Count datagram fragmented successfully │ │ │ │ -

Synopsis

ipmib.FragOKs

Values

skb

│ │ │ │ - pointer to the struct sk_buff being acted on │ │ │ │ -

op

│ │ │ │ +

Synopsis

ipmib.FragOKs

Values

op

│ │ │ │ value to be added to the counter (default value of 1) │ │ │ │ +

skb

│ │ │ │ + pointer to the struct sk_buff being acted on │ │ │ │

Description

│ │ │ │ The packet pointed to by skb is filtered by the function │ │ │ │ ipmib_filter_key. If the packet passes the filter is is │ │ │ │ counted in the global FragOKs (equivalent to SNMP's MIB │ │ │ │ IPSTATS_MIB_FRAGOKS) │ │ │ │

Prev Up Next
probe::ipmib.FragFails Home probe::ipmib.InAddrErrors
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-ipmib-InAddrErrors.html │ │ │ │ @@ -1,12 +1,12 @@ │ │ │ │ probe::ipmib.InAddrErrors
probe::ipmib.InAddrErrors
Prev Chapter 15. SNMP Information Tapset Next

Name

probe::ipmib.InAddrErrors — │ │ │ │ Count arriving packets with an incorrect address │ │ │ │ -

Synopsis

ipmib.InAddrErrors

Values

op

│ │ │ │ - value to be added to the counter (default value of 1) │ │ │ │ -

skb

│ │ │ │ +

Synopsis

ipmib.InAddrErrors

Values

skb

│ │ │ │ pointer to the struct sk_buff being acted on │ │ │ │ +

op

│ │ │ │ + value to be added to the counter (default value of 1) │ │ │ │

Description

│ │ │ │ The packet pointed to by skb is filtered by the function │ │ │ │ ipmib_filter_key. If the packet passes the filter is is │ │ │ │ counted in the global InAddrErrors (equivalent to SNMP's MIB │ │ │ │ IPSTATS_MIB_INADDRERRORS) │ │ │ │

Prev Up Next
probe::ipmib.FragOKs Home probe::ipmib.InDiscards
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-ipmib-InNoRoutes.html │ │ │ │ @@ -1,12 +1,12 @@ │ │ │ │ probe::ipmib.InNoRoutes
probe::ipmib.InNoRoutes
Prev Chapter 15. SNMP Information Tapset Next

Name

probe::ipmib.InNoRoutes — │ │ │ │ Count an arriving packet with no matching socket │ │ │ │ -

Synopsis

ipmib.InNoRoutes

Values

op

│ │ │ │ - value to be added to the counter (default value of 1) │ │ │ │ -

skb

│ │ │ │ +

Synopsis

ipmib.InNoRoutes

Values

skb

│ │ │ │ pointer to the struct sk_buff being acted on │ │ │ │ +

op

│ │ │ │ + value to be added to the counter (default value of 1) │ │ │ │

Description

│ │ │ │ The packet pointed to by skb is filtered by the function │ │ │ │ ipmib_filter_key. If the packet passes the filter is is │ │ │ │ counted in the global InNoRoutes (equivalent to SNMP's MIB │ │ │ │ IPSTATS_MIB_INNOROUTES) │ │ │ │

Prev Up Next
probe::ipmib.InDiscards Home probe::ipmib.InReceives
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-ipmib-InReceives.html │ │ │ │ @@ -1,12 +1,12 @@ │ │ │ │ probe::ipmib.InReceives
probe::ipmib.InReceives
Prev Chapter 15. SNMP Information Tapset Next

Name

probe::ipmib.InReceives — │ │ │ │ Count an arriving packet │ │ │ │ -

Synopsis

ipmib.InReceives

Values

op

│ │ │ │ - value to be added to the counter (default value of 1) │ │ │ │ -

skb

│ │ │ │ +

Synopsis

ipmib.InReceives

Values

skb

│ │ │ │ pointer to the struct sk_buff being acted on │ │ │ │ +

op

│ │ │ │ + value to be added to the counter (default value of 1) │ │ │ │

Description

│ │ │ │ The packet pointed to by skb is filtered by the function │ │ │ │ ipmib_filter_key. If the packet passes the filter is is │ │ │ │ counted in the global InReceives (equivalent to SNMP's MIB │ │ │ │ IPSTATS_MIB_INRECEIVES) │ │ │ │

Prev Up Next
probe::ipmib.InNoRoutes Home probe::ipmib.InUnknownProtos
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-irq-handler-entry.html │ │ │ │ @@ -1,27 +1,27 @@ │ │ │ │ probe::irq_handler.entry
probe::irq_handler.entry
Prev Chapter 12. Interrupt Request (IRQ) Tapset Next

Name

probe::irq_handler.entry — │ │ │ │ Execution of interrupt handler starting │ │ │ │ -

Synopsis

irq_handler.entry

Values

flags

│ │ │ │ - Flags for IRQ handler │ │ │ │ -

dev_name

│ │ │ │ +

Synopsis

irq_handler.entry

Values

dev_name

│ │ │ │ name of device │ │ │ │ -

thread

│ │ │ │ - thread pointer for threaded interrupts │ │ │ │ -

handler

│ │ │ │ - interrupt handler function │ │ │ │ +

thread_flags

│ │ │ │ + Flags related to thread │ │ │ │

dir

│ │ │ │ pointer to the proc/irq/NN/name entry │ │ │ │ -

action

│ │ │ │ - struct irqaction* for this interrupt num │ │ │ │ +

flags_str

│ │ │ │ + symbolic string representation of IRQ flags │ │ │ │

next_irqaction

│ │ │ │ pointer to next irqaction for shared interrupts │ │ │ │ +

action

│ │ │ │ + struct irqaction* for this interrupt num │ │ │ │ +

flags

│ │ │ │ + Flags for IRQ handler │ │ │ │ +

dev_id

│ │ │ │ + Cookie to identify device │ │ │ │

thread_fn

│ │ │ │ interrupt handler function for threaded interrupts │ │ │ │ -

flags_str

│ │ │ │ - symbolic string representation of IRQ flags │ │ │ │ +

thread

│ │ │ │ + thread pointer for threaded interrupts │ │ │ │

irq

│ │ │ │ irq number │ │ │ │ -

dev_id

│ │ │ │ - Cookie to identify device │ │ │ │ -

thread_flags

│ │ │ │ - Flags related to thread │ │ │ │ +

handler

│ │ │ │ + interrupt handler function │ │ │ │

Prev Up Next
Chapter 12. Interrupt Request (IRQ) Tapset Home probe::irq_handler.exit
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-irq-handler-exit.html │ │ │ │ @@ -1,29 +1,29 @@ │ │ │ │ probe::irq_handler.exit
probe::irq_handler.exit
Prev Chapter 12. Interrupt Request (IRQ) Tapset Next

Name

probe::irq_handler.exit — │ │ │ │ Execution of interrupt handler completed │ │ │ │ -

Synopsis

irq_handler.exit

Values

irq

│ │ │ │ +

Synopsis

irq_handler.exit

Values

handler

│ │ │ │ + interrupt handler function that was executed │ │ │ │ +

irq

│ │ │ │ interrupt number │ │ │ │ -

thread_flags

│ │ │ │ - Flags related to thread │ │ │ │

dev_id

│ │ │ │ Cookie to identify device │ │ │ │

thread_fn

│ │ │ │ interrupt handler function for threaded interrupts │ │ │ │ +

thread

│ │ │ │ + thread pointer for threaded interrupts │ │ │ │

flags_str

│ │ │ │ symbolic string representation of IRQ flags │ │ │ │ -

action

│ │ │ │ - struct irqaction* │ │ │ │

next_irqaction

│ │ │ │ pointer to next irqaction for shared interrupts │ │ │ │ -

dev_name

│ │ │ │ - name of device │ │ │ │

flags

│ │ │ │ flags for IRQ handler │ │ │ │ -

ret

│ │ │ │ - return value of the handler │ │ │ │ -

thread

│ │ │ │ - thread pointer for threaded interrupts │ │ │ │ +

action

│ │ │ │ + struct irqaction* │ │ │ │ +

dev_name

│ │ │ │ + name of device │ │ │ │ +

thread_flags

│ │ │ │ + Flags related to thread │ │ │ │

dir

│ │ │ │ pointer to the proc/irq/NN/name entry │ │ │ │ -

handler

│ │ │ │ - interrupt handler function that was executed │ │ │ │ +

ret

│ │ │ │ + return value of the handler │ │ │ │

Prev Up Next
probe::irq_handler.entry Home probe::softirq.entry
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-json-data.html │ │ │ │ @@ -1,15 +1,15 @@ │ │ │ │ probe::json_data
probe::json_data
Prev Chapter 33. JSON Tapset Next

Name

probe::json_data — │ │ │ │ Fires whenever JSON data is wanted by a reader. │ │ │ │

Synopsis

json_data

Values

│ │ │ │ None │ │ │ │

Context

│ │ │ │ This probe fires when the JSON data is about to be read. This │ │ │ │ probe must gather up data and then call the following macros to │ │ │ │ - output the data in JSON format. First, @json_output_data_start │ │ │ │ + output the data in JSON format. First, json_output_data_start() │ │ │ │ must be called. That call is followed by one or more of the │ │ │ │ following (one call for each data item): │ │ │ │ - @json_output_string_value, @json_output_numeric_value, │ │ │ │ - @json_output_array_string_value, and │ │ │ │ - @json_output_array_numeric_value. Finally @json_output_data_end │ │ │ │ + json_output_string_value(), json_output_numeric_value(), │ │ │ │ + json_output_array_string_value(), and │ │ │ │ + json_output_array_numeric_value(). Finally json_output_data_end() │ │ │ │ must be called. │ │ │ │

Prev Up Next
macro::json_output_string_value Home Chapter 34. Output file switching Tapset
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-kprocess-create.html │ │ │ │ @@ -1,12 +1,12 @@ │ │ │ │ probe::kprocess.create
probe::kprocess.create
Prev Chapter 16. Kernel Process Tapset Next

Name

probe::kprocess.create — │ │ │ │ Fires whenever a new process or thread is successfully created │ │ │ │ -

Synopsis

kprocess.create

Values

new_pid

│ │ │ │ - The PID of the newly created process │ │ │ │ -

new_tid

│ │ │ │ +

Synopsis

kprocess.create

Values

new_tid

│ │ │ │ The TID of the newly created task │ │ │ │ +

new_pid

│ │ │ │ + The PID of the newly created process │ │ │ │

Context

│ │ │ │ Parent of the created process. │ │ │ │

Description

│ │ │ │ Fires whenever a new process is successfully created, either as a result of │ │ │ │ fork (or one of its syscall variants), or a new kernel thread. │ │ │ │

Prev Up Next
function::target_set_report Home probe::kprocess.exec
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-kprocess-exec-complete.html │ │ │ │┄ Ordering differences only │ │ │ │ @@ -1,17 +1,17 @@ │ │ │ │ probe::kprocess.exec_complete
probe::kprocess.exec_complete
Prev Chapter 16. Kernel Process Tapset Next

Name

probe::kprocess.exec_complete — │ │ │ │ Return from exec to a new program │ │ │ │

Synopsis

kprocess.exec_complete

Values

success

│ │ │ │ A boolean indicating whether the exec was successful │ │ │ │ -

retstr

│ │ │ │ - A string representation of errno (SystemTap v2.5+) │ │ │ │

name

│ │ │ │ Name of the system call (“execve”) (SystemTap v2.5+) │ │ │ │

errno

│ │ │ │ The error number resulting from the exec │ │ │ │ +

retstr

│ │ │ │ + A string representation of errno (SystemTap v2.5+) │ │ │ │

Context

│ │ │ │ On success, the context of the new executable. │ │ │ │ On failure, remains in the context of the caller. │ │ │ │

Description

│ │ │ │ Fires at the completion of an exec call. Aliased to the │ │ │ │ syscall.execve.return probe in SystemTap v2.5+. │ │ │ │

Prev Up Next
probe::kprocess.exec Home probe::kprocess.exit
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-kprocess-exec.html │ │ │ │ @@ -1,18 +1,18 @@ │ │ │ │ probe::kprocess.exec
probe::kprocess.exec
Prev Chapter 16. Kernel Process Tapset Next

Name

probe::kprocess.exec — │ │ │ │ Attempt to exec to a new program │ │ │ │ -

Synopsis

kprocess.exec

Values

filename

│ │ │ │ - The path to the new executable │ │ │ │ -

name

│ │ │ │ - Name of the system call (“execve”) (SystemTap v2.5+) │ │ │ │ -

argstr

│ │ │ │ +

Synopsis

kprocess.exec

Values

argstr

│ │ │ │ A string containing the filename followed by the │ │ │ │ arguments to pass, excluding 0th arg (SystemTap v2.5+) │ │ │ │

args

│ │ │ │ The arguments to pass to the new executable, including │ │ │ │ the 0th arg (SystemTap v2.5+) │ │ │ │ +

filename

│ │ │ │ + The path to the new executable │ │ │ │ +

name

│ │ │ │ + Name of the system call (“execve”) (SystemTap v2.5+) │ │ │ │

Context

│ │ │ │ The caller of exec. │ │ │ │

Description

│ │ │ │ Fires whenever a process attempts to exec to a new program. Aliased │ │ │ │ to the syscall.execve probe in SystemTap v2.5+. │ │ │ │

Prev Up Next
probe::kprocess.create Home probe::kprocess.exec_complete
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-kprocess-release.html │ │ │ │ @@ -1,17 +1,17 @@ │ │ │ │ probe::kprocess.release
probe::kprocess.release
Prev Chapter 16. Kernel Process Tapset Next

Name

probe::kprocess.release — │ │ │ │ Process released │ │ │ │ -

Synopsis

kprocess.release

Values

task

│ │ │ │ - A task handle to the process being released │ │ │ │ +

Synopsis

kprocess.release

Values

released_pid

│ │ │ │ + PID of the process being released │ │ │ │

pid

│ │ │ │ Same as released_pid for compatibility (deprecated) │ │ │ │ +

task

│ │ │ │ + A task handle to the process being released │ │ │ │

released_tid

│ │ │ │ TID of the task being released │ │ │ │ -

released_pid

│ │ │ │ - PID of the process being released │ │ │ │

Context

│ │ │ │ The context of the parent, if it wanted notification of this process' │ │ │ │ termination, else the context of the process itself. │ │ │ │

Description

│ │ │ │ Fires when a process is released from the kernel. This always follows a │ │ │ │ kprocess.exit, though it may be delayed somewhat if the process waits in a │ │ │ │ zombie state. │ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-linuxmib-DelayedACKs.html │ │ │ │ @@ -1,12 +1,12 @@ │ │ │ │ probe::linuxmib.DelayedACKs

probe::linuxmib.DelayedACKs
Prev Chapter 15. SNMP Information Tapset Next

Name

probe::linuxmib.DelayedACKs — │ │ │ │ Count of delayed acks │ │ │ │ -

Synopsis

linuxmib.DelayedACKs

Values

op

│ │ │ │ - Value to be added to the counter (default value of 1) │ │ │ │ -

sk

│ │ │ │ +

Synopsis

linuxmib.DelayedACKs

Values

sk

│ │ │ │ Pointer to the struct sock being acted on │ │ │ │ +

op

│ │ │ │ + Value to be added to the counter (default value of 1) │ │ │ │

Description

│ │ │ │ The packet pointed to by skb is filtered by the function │ │ │ │ linuxmib_filter_key. If the packet passes the filter is is │ │ │ │ counted in the global DelayedACKs (equivalent to SNMP's MIB │ │ │ │ LINUX_MIB_DELAYEDACKS) │ │ │ │

Prev Up Next
probe::ipmib.ReasmTimeout Home probe::linuxmib.ListenDrops
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-linuxmib-ListenOverflows.html │ │ │ │ @@ -1,12 +1,12 @@ │ │ │ │ probe::linuxmib.ListenOverflows
probe::linuxmib.ListenOverflows
Prev Chapter 15. SNMP Information Tapset Next

Name

probe::linuxmib.ListenOverflows — │ │ │ │ Count of times a listen queue overflowed │ │ │ │ -

Synopsis

linuxmib.ListenOverflows

Values

op

│ │ │ │ - Value to be added to the counter (default value of 1) │ │ │ │ -

sk

│ │ │ │ +

Synopsis

linuxmib.ListenOverflows

Values

sk

│ │ │ │ Pointer to the struct sock being acted on │ │ │ │ +

op

│ │ │ │ + Value to be added to the counter (default value of 1) │ │ │ │

Description

│ │ │ │ The packet pointed to by skb is filtered by the function │ │ │ │ linuxmib_filter_key. If the packet passes the filter is is │ │ │ │ counted in the global ListenOverflows (equivalent to SNMP's MIB │ │ │ │ LINUX_MIB_LISTENOVERFLOWS) │ │ │ │

Prev Up Next
probe::linuxmib.ListenDrops Home probe::linuxmib.TCPMemoryPressures
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-netdev-change-mac.html │ │ │ │ @@ -1,11 +1,11 @@ │ │ │ │ probe::netdev.change_mac
probe::netdev.change_mac
Prev Chapter 13. Networking Tapset Next

Name

probe::netdev.change_mac — │ │ │ │ Called when the netdev_name has the MAC changed │ │ │ │ -

Synopsis

netdev.change_mac

Values

mac_len

│ │ │ │ - The MAC length │ │ │ │ -

new_mac

│ │ │ │ +

Synopsis

netdev.change_mac

Values

new_mac

│ │ │ │ The new MAC address │ │ │ │ +

mac_len

│ │ │ │ + The MAC length │ │ │ │

dev_name

│ │ │ │ The device that will have the MAC changed │ │ │ │

old_mac

│ │ │ │ The current MAC address │ │ │ │

Prev Up Next
function::ntohs Home probe::netdev.change_mtu
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-netdev-hard-transmit.html │ │ │ │┄ Ordering differences only │ │ │ │ @@ -1,11 +1,11 @@ │ │ │ │ probe::netdev.hard_transmit
probe::netdev.hard_transmit
Prev Chapter 13. Networking Tapset Next

Name

probe::netdev.hard_transmit — │ │ │ │ Called when the devices is going to TX (hard) │ │ │ │

Synopsis

netdev.hard_transmit

Values

dev_name

│ │ │ │ The device scheduled to transmit │ │ │ │ -

length

│ │ │ │ - The length of the transmit buffer. │ │ │ │ -

protocol

│ │ │ │ - The protocol used in the transmission │ │ │ │

truesize

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

protocol

│ │ │ │ + The protocol used in the transmission │ │ │ │ +

length

│ │ │ │ + The length of the transmit buffer. │ │ │ │

Prev Up Next
probe::netdev.get_stats Home probe::netdev.ioctl
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-netdev-receive.html │ │ │ │ @@ -1,9 +1,9 @@ │ │ │ │ probe::netdev.receive
probe::netdev.receive
Prev Chapter 13. Networking Tapset Next

Name

probe::netdev.receive — │ │ │ │ Data received from network device. │ │ │ │ -

Synopsis

netdev.receive

Values

protocol

│ │ │ │ +

Synopsis

netdev.receive

Values

length

│ │ │ │ + The length of the receiving buffer. │ │ │ │ +

protocol

│ │ │ │ Protocol of received packet. │ │ │ │

dev_name

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

length

│ │ │ │ - The length of the receiving buffer. │ │ │ │

Prev Up Next
probe::netdev.open Home probe::netdev.register
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-netdev-set-promiscuity.html │ │ │ │ @@ -1,11 +1,11 @@ │ │ │ │ probe::netdev.set_promiscuity
probe::netdev.set_promiscuity
Prev Chapter 13. Networking Tapset Next

Name

probe::netdev.set_promiscuity — │ │ │ │ Called when the device enters/leaves promiscuity │ │ │ │ -

Synopsis

netdev.set_promiscuity

Values

enable

│ │ │ │ +

Synopsis

netdev.set_promiscuity

Values

disable

│ │ │ │ + If the device is leaving promiscuity mode │ │ │ │ +

dev_name

│ │ │ │ + The device that is entering/leaving promiscuity mode │ │ │ │ +

enable

│ │ │ │ If the device is entering promiscuity mode │ │ │ │

inc

│ │ │ │ Count the number of promiscuity openers │ │ │ │ -

dev_name

│ │ │ │ - The device that is entering/leaving promiscuity mode │ │ │ │ -

disable

│ │ │ │ - If the device is leaving promiscuity mode │ │ │ │

Prev Up Next
probe::netdev.rx Home probe::netdev.transmit
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-netdev-transmit.html │ │ │ │ @@ -1,11 +1,11 @@ │ │ │ │ probe::netdev.transmit
probe::netdev.transmit
Prev Chapter 13. Networking Tapset Next

Name

probe::netdev.transmit — │ │ │ │ Network device transmitting buffer │ │ │ │ -

Synopsis

netdev.transmit

Values

protocol

│ │ │ │ +

Synopsis

netdev.transmit

Values

length

│ │ │ │ + The length of the transmit buffer. │ │ │ │ +

protocol

│ │ │ │ The protocol of this packet(defined in include/linux/if_ether.h). │ │ │ │

truesize

│ │ │ │ The size of the data to be transmitted. │ │ │ │

dev_name

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

length

│ │ │ │ - The length of the transmit buffer. │ │ │ │

Prev Up Next
probe::netdev.set_promiscuity Home probe::netdev.unregister
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-netfilter-arp-forward.html │ │ │ │ @@ -1,53 +1,53 @@ │ │ │ │ probe::netfilter.arp.forward
probe::netfilter.arp.forward
Prev Chapter 13. Networking Tapset Next

Name

probe::netfilter.arp.forward — │ │ │ │ - Called for each ARP packet to be forwarded │ │ │ │ -

Synopsis

netfilter.arp.forward

Values

data_hex

│ │ │ │ - A hexadecimal string representing the packet buffer contents │ │ │ │ -

ar_op

│ │ │ │ - ARP opcode (command) │ │ │ │ -

nf_stop

│ │ │ │ - Constant used to signify a 'stop' verdict │ │ │ │ -

nf_drop

│ │ │ │ - Constant used to signify a 'drop' verdict │ │ │ │ -

ar_hln

│ │ │ │ - Length of hardware address │ │ │ │ -

nf_stolen

│ │ │ │ - Constant used to signify a 'stolen' verdict │ │ │ │ -

nf_repeat

│ │ │ │ +

Synopsis

netfilter.arp.forward

Values

nf_repeat

│ │ │ │ Constant used to signify a 'repeat' verdict │ │ │ │ -

ar_sha

│ │ │ │ - Ethernet+IP only (ar_pro==0x800): source hardware (MAC) address │ │ │ │

ar_hrd

│ │ │ │ Format of hardware address │ │ │ │ -

nf_accept

│ │ │ │ - Constant used to signify an 'accept' verdict │ │ │ │

nf_queue

│ │ │ │ Constant used to signify a 'queue' verdict │ │ │ │ -

indev

│ │ │ │ - Address of net_device representing input device, 0 if unknown │ │ │ │ +

nf_stolen

│ │ │ │ + Constant used to signify a 'stolen' verdict │ │ │ │ +

indev_name

│ │ │ │ + Name of network device packet was received on (if known) │ │ │ │ +

ar_op

│ │ │ │ + ARP opcode (command) │ │ │ │ +

ar_hln

│ │ │ │ + Length of hardware address │ │ │ │ +

ar_pro

│ │ │ │ + Format of protocol address │ │ │ │

ar_tha

│ │ │ │ Ethernet+IP only (ar_pro==0x800): target hardware (MAC) address │ │ │ │ -

ar_pln

│ │ │ │ - Length of protocol address │ │ │ │ -

length

│ │ │ │ - The length of the packet buffer contents, in bytes │ │ │ │ -

ar_data

│ │ │ │ - Address of ARP packet data region (after the header) │ │ │ │ +

indev

│ │ │ │ + Address of net_device representing input device, 0 if unknown │ │ │ │

outdev

│ │ │ │ Address of net_device representing output device, 0 if unknown │ │ │ │ +

nf_stop

│ │ │ │ + Constant used to signify a 'stop' verdict │ │ │ │

ar_sip

│ │ │ │ Ethernet+IP only (ar_pro==0x800): source IP address │ │ │ │ +

arphdr

│ │ │ │ + Address of ARP header │ │ │ │ +

nf_accept

│ │ │ │ + Constant used to signify an 'accept' verdict │ │ │ │ +

ar_data

│ │ │ │ + Address of ARP packet data region (after the header) │ │ │ │

pf

│ │ │ │ Protocol family -- always “arp” │ │ │ │ -

indev_name

│ │ │ │ - Name of network device packet was received on (if known) │ │ │ │ -

ar_tip

│ │ │ │ - Ethernet+IP only (ar_pro==0x800): target IP address │ │ │ │ -

outdev_name

│ │ │ │ - Name of network device packet will be routed to (if known) │ │ │ │ +

data_hex

│ │ │ │ + A hexadecimal string representing the packet buffer contents │ │ │ │ +

nf_drop

│ │ │ │ + Constant used to signify a 'drop' verdict │ │ │ │ +

length

│ │ │ │ + The length of the packet buffer contents, in bytes │ │ │ │ +

ar_sha

│ │ │ │ + Ethernet+IP only (ar_pro==0x800): source hardware (MAC) address │ │ │ │ +

ar_pln

│ │ │ │ + Length of protocol address │ │ │ │

data_str

│ │ │ │ A string representing the packet buffer contents │ │ │ │ -

arphdr

│ │ │ │ - Address of ARP header │ │ │ │ -

ar_pro

│ │ │ │ - Format of protocol address │ │ │ │ +

outdev_name

│ │ │ │ + Name of network device packet will be routed to (if known) │ │ │ │ +

ar_tip

│ │ │ │ + Ethernet+IP only (ar_pro==0x800): target IP address │ │ │ │

Prev Up Next
probe::netdev.unregister Home probe::netfilter.arp.in
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-netfilter-arp-in.html │ │ │ │┄ Ordering differences only │ │ │ │ @@ -1,53 +1,53 @@ │ │ │ │ probe::netfilter.arp.in
probe::netfilter.arp.in
Prev Chapter 13. Networking Tapset Next

Name

probe::netfilter.arp.in — │ │ │ │ - Called for each incoming ARP packet │ │ │ │

Synopsis

netfilter.arp.in

Values

data_str

│ │ │ │ A string representing the packet buffer contents │ │ │ │ -

arphdr

│ │ │ │ - Address of ARP header │ │ │ │ -

ar_pro

│ │ │ │ - Format of protocol address │ │ │ │ -

outdev

│ │ │ │ - Address of net_device representing output device, 0 if unknown │ │ │ │ -

ar_sip

│ │ │ │ - Ethernet+IP only (ar_pro==0x800): source IP address │ │ │ │ -

pf

│ │ │ │ - Protocol family -- always “arp” │ │ │ │ -

indev_name

│ │ │ │ - Name of network device packet was received on (if known) │ │ │ │ +

ar_pln

│ │ │ │ + Length of protocol address │ │ │ │

ar_tip

│ │ │ │ Ethernet+IP only (ar_pro==0x800): target IP address │ │ │ │

outdev_name

│ │ │ │ Name of network device packet will be routed to (if known) │ │ │ │ -

nf_repeat

│ │ │ │ - Constant used to signify a 'repeat' verdict │ │ │ │ -

ar_sha

│ │ │ │ - Ethernet+IP only (ar_pro==0x800): source hardware (MAC) address │ │ │ │ -

ar_hrd

│ │ │ │ - Format of hardware address │ │ │ │ +

arphdr

│ │ │ │ + Address of ARP header │ │ │ │

nf_accept

│ │ │ │ Constant used to signify an 'accept' verdict │ │ │ │ -

nf_queue

│ │ │ │ - Constant used to signify a 'queue' verdict │ │ │ │ -

ar_tha

│ │ │ │ - Ethernet+IP only (ar_pro==0x800): target hardware (MAC) address │ │ │ │ -

indev

│ │ │ │ - Address of net_device representing input device, 0 if unknown │ │ │ │ -

ar_pln

│ │ │ │ - Length of protocol address │ │ │ │ -

ar_data

│ │ │ │ - Address of ARP packet data region (after the header) │ │ │ │

length

│ │ │ │ The length of the packet buffer contents, in bytes │ │ │ │ +

ar_sha

│ │ │ │ + Ethernet+IP only (ar_pro==0x800): source hardware (MAC) address │ │ │ │

data_hex

│ │ │ │ A hexadecimal string representing the packet buffer contents │ │ │ │ -

ar_op

│ │ │ │ - ARP opcode (command) │ │ │ │ -

nf_stop

│ │ │ │ - Constant used to signify a 'stop' verdict │ │ │ │

nf_drop

│ │ │ │ Constant used to signify a 'drop' verdict │ │ │ │ +

ar_data

│ │ │ │ + Address of ARP packet data region (after the header) │ │ │ │ +

pf

│ │ │ │ + Protocol family -- always “arp” │ │ │ │ +

outdev

│ │ │ │ + Address of net_device representing output device, 0 if unknown │ │ │ │ +

ar_sip

│ │ │ │ + Ethernet+IP only (ar_pro==0x800): source IP address │ │ │ │ +

nf_stop

│ │ │ │ + Constant used to signify a 'stop' verdict │ │ │ │ +

nf_repeat

│ │ │ │ + Constant used to signify a 'repeat' verdict │ │ │ │ +

indev

│ │ │ │ + Address of net_device representing input device, 0 if unknown │ │ │ │

ar_hln

│ │ │ │ Length of hardware address │ │ │ │ +

ar_op

│ │ │ │ + ARP opcode (command) │ │ │ │ +

ar_pro

│ │ │ │ + Format of protocol address │ │ │ │ +

ar_tha

│ │ │ │ + Ethernet+IP only (ar_pro==0x800): target hardware (MAC) address │ │ │ │ +

ar_hrd

│ │ │ │ + Format of hardware address │ │ │ │ +

nf_queue

│ │ │ │ + Constant used to signify a 'queue' verdict │ │ │ │

nf_stolen

│ │ │ │ Constant used to signify a 'stolen' verdict │ │ │ │ +

indev_name

│ │ │ │ + Name of network device packet was received on (if known) │ │ │ │

Prev Up Next
probe::netfilter.arp.forward Home probe::netfilter.arp.out
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-netfilter-arp-out.html │ │ │ │ @@ -1,53 +1,53 @@ │ │ │ │ probe::netfilter.arp.out
probe::netfilter.arp.out
Prev Chapter 13. Networking Tapset Next

Name

probe::netfilter.arp.out — │ │ │ │ - Called for each outgoing ARP packet │ │ │ │ -

Synopsis

netfilter.arp.out

Values

indev_name

│ │ │ │ - Name of network device packet was received on (if known) │ │ │ │ -

ar_tip

│ │ │ │ - Ethernet+IP only (ar_pro==0x800): target IP address │ │ │ │ -

outdev_name

│ │ │ │ - Name of network device packet will be routed to (if known) │ │ │ │ -

ar_sip

│ │ │ │ - Ethernet+IP only (ar_pro==0x800): source IP address │ │ │ │ -

outdev

│ │ │ │ - Address of net_device representing output device, 0 if unknown │ │ │ │ -

pf

│ │ │ │ - Protocol family -- always “arp” │ │ │ │ -

ar_pro

│ │ │ │ - Format of protocol address │ │ │ │ -

data_str

│ │ │ │ - A string representing the packet buffer contents │ │ │ │ -

arphdr

│ │ │ │ - Address of ARP header │ │ │ │ -

nf_stolen

│ │ │ │ - Constant used to signify a 'stolen' verdict │ │ │ │ +

Synopsis

netfilter.arp.out

Values

nf_drop

│ │ │ │ + Constant used to signify a 'drop' verdict │ │ │ │

data_hex

│ │ │ │ A hexadecimal string representing the packet buffer contents │ │ │ │ -

ar_op

│ │ │ │ - ARP opcode (command) │ │ │ │ -

nf_drop

│ │ │ │ - Constant used to signify a 'drop' verdict │ │ │ │ -

nf_stop

│ │ │ │ - Constant used to signify a 'stop' verdict │ │ │ │ -

ar_hln

│ │ │ │ - Length of hardware address │ │ │ │ +

pf

│ │ │ │ + Protocol family -- always “arp” │ │ │ │ +

ar_data

│ │ │ │ + Address of ARP packet data region (after the header) │ │ │ │ +

length

│ │ │ │ + The length of the packet buffer contents, in bytes │ │ │ │ +

ar_sha

│ │ │ │ + Ethernet+IP only (ar_pro==0x800): source hardware (MAC) address │ │ │ │

nf_accept

│ │ │ │ Constant used to signify an 'accept' verdict │ │ │ │ +

arphdr

│ │ │ │ + Address of ARP header │ │ │ │ +

outdev_name

│ │ │ │ + Name of network device packet will be routed to (if known) │ │ │ │ +

ar_tip

│ │ │ │ + Ethernet+IP only (ar_pro==0x800): target IP address │ │ │ │ +

ar_pln

│ │ │ │ + Length of protocol address │ │ │ │ +

data_str

│ │ │ │ + A string representing the packet buffer contents │ │ │ │ +

ar_pro

│ │ │ │ + Format of protocol address │ │ │ │

ar_tha

│ │ │ │ Ethernet+IP only (ar_pro==0x800): target hardware (MAC) address │ │ │ │ -

indev

│ │ │ │ - Address of net_device representing input device, 0 if unknown │ │ │ │ +

ar_hln

│ │ │ │ + Length of hardware address │ │ │ │ +

ar_op

│ │ │ │ + ARP opcode (command) │ │ │ │ +

indev_name

│ │ │ │ + Name of network device packet was received on (if known) │ │ │ │

nf_queue

│ │ │ │ Constant used to signify a 'queue' verdict │ │ │ │ -

ar_pln

│ │ │ │ - Length of protocol address │ │ │ │ -

ar_data

│ │ │ │ - Address of ARP packet data region (after the header) │ │ │ │ -

length

│ │ │ │ - The length of the packet buffer contents, in bytes │ │ │ │ -

nf_repeat

│ │ │ │ - Constant used to signify a 'repeat' verdict │ │ │ │ +

nf_stolen

│ │ │ │ + Constant used to signify a 'stolen' verdict │ │ │ │

ar_hrd

│ │ │ │ Format of hardware address │ │ │ │ -

ar_sha

│ │ │ │ - Ethernet+IP only (ar_pro==0x800): source hardware (MAC) address │ │ │ │ +

indev

│ │ │ │ + Address of net_device representing input device, 0 if unknown │ │ │ │ +

nf_repeat

│ │ │ │ + Constant used to signify a 'repeat' verdict │ │ │ │ +

ar_sip

│ │ │ │ + Ethernet+IP only (ar_pro==0x800): source IP address │ │ │ │ +

nf_stop

│ │ │ │ + Constant used to signify a 'stop' verdict │ │ │ │ +

outdev

│ │ │ │ + Address of net_device representing output device, 0 if unknown │ │ │ │

Prev Up Next
probe::netfilter.arp.in Home probe::netfilter.bridge.forward
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-netfilter-bridge-forward.html │ │ │ │ @@ -1,67 +1,67 @@ │ │ │ │ probe::netfilter.bridge.forward
probe::netfilter.bridge.forward
Prev Chapter 13. Networking Tapset Next

Name

probe::netfilter.bridge.forward — │ │ │ │ Called on an incoming bridging packet destined for some other computer │ │ │ │ -

Synopsis

netfilter.bridge.forward

Values

llcpdu

│ │ │ │ - Address of LLC Protocol Data Unit │ │ │ │ -

br_bid

│ │ │ │ - Identity of bridge │ │ │ │ -

data_str

│ │ │ │ - A string representing the packet buffer contents │ │ │ │ -

br_cost

│ │ │ │ - Total cost from transmitting bridge to root │ │ │ │ -

br_flags

│ │ │ │ - BPDU flags │ │ │ │ -

indev_name

│ │ │ │ - Name of network device packet was received on (if known) │ │ │ │ -

br_mac

│ │ │ │ - Bridge MAC address │ │ │ │ -

br_type

│ │ │ │ - BPDU type │ │ │ │ -

protocol

│ │ │ │ - Packet protocol │ │ │ │ -

br_poid

│ │ │ │ +

Synopsis

netfilter.bridge.forward

Values

br_poid

│ │ │ │ Port identifier │ │ │ │ -

outdev_name

│ │ │ │ - Name of network device packet will be routed to (if known) │ │ │ │ -

pf

│ │ │ │ - Protocol family -- always “bridge” │ │ │ │ -

br_htime

│ │ │ │ - Hello time in 1/256 secs │ │ │ │ -

br_prid

│ │ │ │ - Protocol identifier │ │ │ │ +

br_fd

│ │ │ │ + Forward delay in 1/256 secs │ │ │ │

outdev

│ │ │ │ Address of net_device representing output device, 0 if unknown │ │ │ │ -

br_msg

│ │ │ │ - Message age in 1/256 secs │ │ │ │ -

nf_queue

│ │ │ │ - Constant used to signify a 'queue' verdict │ │ │ │ -

indev

│ │ │ │ - Address of net_device representing input device, 0 if unknown │ │ │ │ -

nf_accept

│ │ │ │ - Constant used to signify an 'accept' verdict │ │ │ │ -

length

│ │ │ │ - The length of the packet buffer contents, in bytes │ │ │ │ -

nf_repeat

│ │ │ │ - Constant used to signify a 'repeat' verdict │ │ │ │ +

br_prid

│ │ │ │ + Protocol identifier │ │ │ │ +

llcproto_stp

│ │ │ │ + Constant used to signify Bridge Spanning Tree Protocol packet │ │ │ │

br_rid

│ │ │ │ Identity of root bridge │ │ │ │ +

nf_stop

│ │ │ │ + Constant used to signify a 'stop' verdict │ │ │ │ +

protocol

│ │ │ │ + Packet protocol │ │ │ │ +

brhdr

│ │ │ │ + Address of bridge header │ │ │ │ +

br_flags

│ │ │ │ + BPDU flags │ │ │ │ +

nf_repeat

│ │ │ │ + Constant used to signify a 'repeat' verdict │ │ │ │ +

br_bid

│ │ │ │ + Identity of bridge │ │ │ │ +

nf_queue

│ │ │ │ + Constant used to signify a 'queue' verdict │ │ │ │

nf_stolen

│ │ │ │ Constant used to signify a 'stolen' verdict │ │ │ │ +

br_mac

│ │ │ │ + Bridge MAC address │ │ │ │ +

indev_name

│ │ │ │ + Name of network device packet was received on (if known) │ │ │ │ +

indev

│ │ │ │ + Address of net_device representing input device, 0 if unknown │ │ │ │

br_rmac

│ │ │ │ Root bridge MAC address │ │ │ │ -

llcproto_stp

│ │ │ │ - Constant used to signify Bridge Spanning Tree Protocol packet │ │ │ │ -

brhdr

│ │ │ │ - Address of bridge header │ │ │ │ +

br_msg

│ │ │ │ + Message age in 1/256 secs │ │ │ │ +

data_str

│ │ │ │ + A string representing the packet buffer contents │ │ │ │ +

outdev_name

│ │ │ │ + Name of network device packet will be routed to (if known) │ │ │ │ +

llcpdu

│ │ │ │ + Address of LLC Protocol Data Unit │ │ │ │ +

br_htime

│ │ │ │ + Hello time in 1/256 secs │ │ │ │

br_vid

│ │ │ │ Protocol version identifier │ │ │ │ -

br_fd

│ │ │ │ - Forward delay in 1/256 secs │ │ │ │ +

nf_accept

│ │ │ │ + Constant used to signify an 'accept' verdict │ │ │ │ +

br_cost

│ │ │ │ + Total cost from transmitting bridge to root │ │ │ │ +

nf_drop

│ │ │ │ + Constant used to signify a 'drop' verdict │ │ │ │

data_hex

│ │ │ │ A hexadecimal string representing the packet buffer contents │ │ │ │ -

nf_stop

│ │ │ │ - Constant used to signify a 'stop' verdict │ │ │ │ +

pf

│ │ │ │ + Protocol family -- always “bridge” │ │ │ │ +

length

│ │ │ │ + The length of the packet buffer contents, in bytes │ │ │ │

br_max

│ │ │ │ Max age in 1/256 secs │ │ │ │ -

nf_drop

│ │ │ │ - Constant used to signify a 'drop' verdict │ │ │ │ +

br_type

│ │ │ │ + BPDU type │ │ │ │

Prev Up Next
probe::netfilter.arp.out Home probe::netfilter.bridge.local_in
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-netfilter-bridge-local-in.html │ │ │ │ @@ -1,67 +1,67 @@ │ │ │ │ probe::netfilter.bridge.local_in
probe::netfilter.bridge.local_in
Prev Chapter 13. Networking Tapset Next

Name

probe::netfilter.bridge.local_in — │ │ │ │ Called on a bridging packet destined for the local computer │ │ │ │ -

Synopsis

netfilter.bridge.local_in

Values

br_cost

│ │ │ │ +

Synopsis

netfilter.bridge.local_in

Values

nf_accept

│ │ │ │ + Constant used to signify an 'accept' verdict │ │ │ │ +

br_vid

│ │ │ │ + Protocol version identifier │ │ │ │ +

br_cost

│ │ │ │ Total cost from transmitting bridge to root │ │ │ │ +

data_hex

│ │ │ │ + A hexadecimal string representing the packet buffer contents │ │ │ │ +

nf_drop

│ │ │ │ + Constant used to signify a 'drop' verdict │ │ │ │ +

pf

│ │ │ │ + Protocol family -- always “bridge” │ │ │ │ +

br_max

│ │ │ │ + Max age in 1/256 secs │ │ │ │ +

length

│ │ │ │ + The length of the packet buffer contents, in bytes │ │ │ │ +

br_type

│ │ │ │ + BPDU type │ │ │ │ +

br_rmac

│ │ │ │ + Root bridge MAC address │ │ │ │ +

br_msg

│ │ │ │ + Message age in 1/256 secs │ │ │ │

data_str

│ │ │ │ A string representing the packet buffer contents │ │ │ │ -

br_bid

│ │ │ │ - Identity of bridge │ │ │ │ +

outdev_name

│ │ │ │ + Name of network device packet will be routed to (if known) │ │ │ │

llcpdu

│ │ │ │ Address of LLC Protocol Data Unit │ │ │ │ -

br_msg

│ │ │ │ - Message age in 1/256 secs │ │ │ │ -

br_prid

│ │ │ │ - Protocol identifier │ │ │ │

br_htime

│ │ │ │ Hello time in 1/256 secs │ │ │ │ -

outdev

│ │ │ │ - Address of net_device representing output device, 0 if unknown │ │ │ │ -

pf

│ │ │ │ - Protocol family -- always “bridge” │ │ │ │ -

outdev_name

│ │ │ │ - Name of network device packet will be routed to (if known) │ │ │ │ -

br_poid

│ │ │ │ - Port identifier │ │ │ │ -

protocol

│ │ │ │ - Packet protocol │ │ │ │ -

br_type

│ │ │ │ - BPDU type │ │ │ │ -

indev_name

│ │ │ │ - Name of network device packet was received on (if known) │ │ │ │ -

br_mac

│ │ │ │ - Bridge MAC address │ │ │ │

br_flags

│ │ │ │ BPDU flags │ │ │ │ -

br_rid

│ │ │ │ - Identity of root bridge │ │ │ │

nf_repeat

│ │ │ │ Constant used to signify a 'repeat' verdict │ │ │ │ -

length

│ │ │ │ - The length of the packet buffer contents, in bytes │ │ │ │ -

nf_accept

│ │ │ │ - Constant used to signify an 'accept' verdict │ │ │ │ -

indev

│ │ │ │ - Address of net_device representing input device, 0 if unknown │ │ │ │ +

br_bid

│ │ │ │ + Identity of bridge │ │ │ │ +

indev_name

│ │ │ │ + Name of network device packet was received on (if known) │ │ │ │

nf_queue

│ │ │ │ Constant used to signify a 'queue' verdict │ │ │ │ -

br_max

│ │ │ │ - Max age in 1/256 secs │ │ │ │ -

nf_drop

│ │ │ │ - Constant used to signify a 'drop' verdict │ │ │ │ -

nf_stop

│ │ │ │ - Constant used to signify a 'stop' verdict │ │ │ │ -

data_hex

│ │ │ │ - A hexadecimal string representing the packet buffer contents │ │ │ │ +

nf_stolen

│ │ │ │ + Constant used to signify a 'stolen' verdict │ │ │ │ +

br_mac

│ │ │ │ + Bridge MAC address │ │ │ │ +

indev

│ │ │ │ + Address of net_device representing input device, 0 if unknown │ │ │ │

br_fd

│ │ │ │ Forward delay in 1/256 secs │ │ │ │ -

br_vid

│ │ │ │ - Protocol version identifier │ │ │ │ -

brhdr

│ │ │ │ - Address of bridge header │ │ │ │ -

br_rmac

│ │ │ │ - Root bridge MAC address │ │ │ │ +

br_poid

│ │ │ │ + Port identifier │ │ │ │ +

br_prid

│ │ │ │ + Protocol identifier │ │ │ │ +

outdev

│ │ │ │ + Address of net_device representing output device, 0 if unknown │ │ │ │

llcproto_stp

│ │ │ │ Constant used to signify Bridge Spanning Tree Protocol packet │ │ │ │ -

nf_stolen

│ │ │ │ - Constant used to signify a 'stolen' verdict │ │ │ │ +

nf_stop

│ │ │ │ + Constant used to signify a 'stop' verdict │ │ │ │ +

br_rid

│ │ │ │ + Identity of root bridge │ │ │ │ +

protocol

│ │ │ │ + Packet protocol │ │ │ │ +

brhdr

│ │ │ │ + Address of bridge header │ │ │ │

Prev Up Next
probe::netfilter.bridge.forward Home probe::netfilter.bridge.local_out
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-netfilter-bridge-local-out.html │ │ │ │ @@ -1,67 +1,67 @@ │ │ │ │ probe::netfilter.bridge.local_out
probe::netfilter.bridge.local_out
Prev Chapter 13. Networking Tapset Next

Name

probe::netfilter.bridge.local_out — │ │ │ │ Called on a bridging packet coming from a local process │ │ │ │ -

Synopsis

netfilter.bridge.local_out

Values

llcpdu

│ │ │ │ - Address of LLC Protocol Data Unit │ │ │ │ -

br_bid

│ │ │ │ - Identity of bridge │ │ │ │ -

data_str

│ │ │ │ - A string representing the packet buffer contents │ │ │ │ -

br_cost

│ │ │ │ +

Synopsis

netfilter.bridge.local_out

Values

br_cost

│ │ │ │ Total cost from transmitting bridge to root │ │ │ │ -

br_flags

│ │ │ │ - BPDU flags │ │ │ │ -

indev_name

│ │ │ │ - Name of network device packet was received on (if known) │ │ │ │ -

br_mac

│ │ │ │ - Bridge MAC address │ │ │ │ -

protocol

│ │ │ │ - Packet protocol │ │ │ │ +

nf_accept

│ │ │ │ + Constant used to signify an 'accept' verdict │ │ │ │ +

br_vid

│ │ │ │ + Protocol version identifier │ │ │ │

br_type

│ │ │ │ BPDU type │ │ │ │ -

outdev_name

│ │ │ │ - Name of network device packet will be routed to (if known) │ │ │ │ -

br_poid

│ │ │ │ - Port identifier │ │ │ │ +

br_max

│ │ │ │ + Max age in 1/256 secs │ │ │ │ +

length

│ │ │ │ + The length of the packet buffer contents, in bytes │ │ │ │

pf

│ │ │ │ Protocol family -- always “bridge” │ │ │ │ -

br_htime

│ │ │ │ - Hello time in 1/256 secs │ │ │ │ -

br_prid

│ │ │ │ - Protocol identifier │ │ │ │ -

outdev

│ │ │ │ - Address of net_device representing output device, 0 if unknown │ │ │ │ +

data_hex

│ │ │ │ + A hexadecimal string representing the packet buffer contents │ │ │ │ +

nf_drop

│ │ │ │ + Constant used to signify a 'drop' verdict │ │ │ │ +

data_str

│ │ │ │ + A string representing the packet buffer contents │ │ │ │

br_msg

│ │ │ │ Message age in 1/256 secs │ │ │ │ +

br_rmac

│ │ │ │ + Root bridge MAC address │ │ │ │ +

br_htime

│ │ │ │ + Hello time in 1/256 secs │ │ │ │ +

llcpdu

│ │ │ │ + Address of LLC Protocol Data Unit │ │ │ │ +

outdev_name

│ │ │ │ + Name of network device packet will be routed to (if known) │ │ │ │ +

nf_repeat

│ │ │ │ + Constant used to signify a 'repeat' verdict │ │ │ │ +

br_flags

│ │ │ │ + BPDU flags │ │ │ │

indev

│ │ │ │ Address of net_device representing input device, 0 if unknown │ │ │ │ +

br_mac

│ │ │ │ + Bridge MAC address │ │ │ │

nf_queue

│ │ │ │ Constant used to signify a 'queue' verdict │ │ │ │ -

nf_accept

│ │ │ │ - Constant used to signify an 'accept' verdict │ │ │ │ -

length

│ │ │ │ - The length of the packet buffer contents, in bytes │ │ │ │ -

nf_repeat

│ │ │ │ - Constant used to signify a 'repeat' verdict │ │ │ │ -

br_rid

│ │ │ │ - Identity of root bridge │ │ │ │ -

llcproto_stp

│ │ │ │ - Constant used to signify Bridge Spanning Tree Protocol packet │ │ │ │ -

br_rmac

│ │ │ │ - Root bridge MAC address │ │ │ │

nf_stolen

│ │ │ │ Constant used to signify a 'stolen' verdict │ │ │ │ -

brhdr

│ │ │ │ - Address of bridge header │ │ │ │ -

br_vid

│ │ │ │ - Protocol version identifier │ │ │ │ +

indev_name

│ │ │ │ + Name of network device packet was received on (if known) │ │ │ │ +

br_bid

│ │ │ │ + Identity of bridge │ │ │ │ +

llcproto_stp

│ │ │ │ + Constant used to signify Bridge Spanning Tree Protocol packet │ │ │ │ +

br_prid

│ │ │ │ + Protocol identifier │ │ │ │ +

outdev

│ │ │ │ + Address of net_device representing output device, 0 if unknown │ │ │ │

br_fd

│ │ │ │ Forward delay in 1/256 secs │ │ │ │ -

data_hex

│ │ │ │ - A hexadecimal string representing the packet buffer contents │ │ │ │ -

nf_drop

│ │ │ │ - Constant used to signify a 'drop' verdict │ │ │ │ -

br_max

│ │ │ │ - Max age in 1/256 secs │ │ │ │ +

br_poid

│ │ │ │ + Port identifier │ │ │ │ +

brhdr

│ │ │ │ + Address of bridge header │ │ │ │ +

protocol

│ │ │ │ + Packet protocol │ │ │ │

nf_stop

│ │ │ │ Constant used to signify a 'stop' verdict │ │ │ │ +

br_rid

│ │ │ │ + Identity of root bridge │ │ │ │

Prev Up Next
probe::netfilter.bridge.local_in Home probe::netfilter.bridge.post_routing
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-netfilter-bridge-post-routing.html │ │ │ │ @@ -1,67 +1,67 @@ │ │ │ │ probe::netfilter.bridge.post_routing
probe::netfilter.bridge.post_routing
Prev Chapter 13. Networking Tapset Next

Name

probe::netfilter.bridge.post_routing — │ │ │ │ - Called before a bridging packet hits the wire │ │ │ │ -

Synopsis

netfilter.bridge.post_routing

Values

nf_accept

│ │ │ │ - Constant used to signify an 'accept' verdict │ │ │ │ -

indev

│ │ │ │ +

Synopsis

netfilter.bridge.post_routing

Values

indev

│ │ │ │ Address of net_device representing input device, 0 if unknown │ │ │ │ +

br_bid

│ │ │ │ + Identity of bridge │ │ │ │ +

nf_stolen

│ │ │ │ + Constant used to signify a 'stolen' verdict │ │ │ │

nf_queue

│ │ │ │ Constant used to signify a 'queue' verdict │ │ │ │ -

length

│ │ │ │ - The length of the packet buffer contents, in bytes │ │ │ │ -

br_rid

│ │ │ │ - Identity of root bridge │ │ │ │ +

indev_name

│ │ │ │ + Name of network device packet was received on (if known) │ │ │ │ +

br_mac

│ │ │ │ + Bridge MAC address │ │ │ │

nf_repeat

│ │ │ │ Constant used to signify a 'repeat' verdict │ │ │ │ +

br_flags

│ │ │ │ + BPDU flags │ │ │ │ +

protocol

│ │ │ │ + Packet protocol │ │ │ │

brhdr

│ │ │ │ Address of bridge header │ │ │ │ +

nf_stop

│ │ │ │ + Constant used to signify a 'stop' verdict │ │ │ │ +

br_rid

│ │ │ │ + Identity of root bridge │ │ │ │

llcproto_stp

│ │ │ │ Constant used to signify Bridge Spanning Tree Protocol packet │ │ │ │ -

br_rmac

│ │ │ │ - Root bridge MAC address │ │ │ │ -

nf_stolen

│ │ │ │ - Constant used to signify a 'stolen' verdict │ │ │ │

br_fd

│ │ │ │ Forward delay in 1/256 secs │ │ │ │ -

br_vid

│ │ │ │ - Protocol version identifier │ │ │ │ -

data_hex

│ │ │ │ - A hexadecimal string representing the packet buffer contents │ │ │ │ -

nf_drop

│ │ │ │ - Constant used to signify a 'drop' verdict │ │ │ │ -

br_max

│ │ │ │ - Max age in 1/256 secs │ │ │ │ -

nf_stop

│ │ │ │ - Constant used to signify a 'stop' verdict │ │ │ │ -

llcpdu

│ │ │ │ - Address of LLC Protocol Data Unit │ │ │ │ -

data_str

│ │ │ │ - A string representing the packet buffer contents │ │ │ │ -

br_bid

│ │ │ │ - Identity of bridge │ │ │ │ -

br_cost

│ │ │ │ - Total cost from transmitting bridge to root │ │ │ │ -

br_mac

│ │ │ │ - Bridge MAC address │ │ │ │ -

indev_name

│ │ │ │ - Name of network device packet was received on (if known) │ │ │ │ -

br_flags

│ │ │ │ - BPDU flags │ │ │ │

br_poid

│ │ │ │ Port identifier │ │ │ │ -

outdev_name

│ │ │ │ - Name of network device packet will be routed to (if known) │ │ │ │ -

protocol

│ │ │ │ - Packet protocol │ │ │ │ -

br_type

│ │ │ │ - BPDU type │ │ │ │ -

br_htime

│ │ │ │ - Hello time in 1/256 secs │ │ │ │ -

outdev

│ │ │ │ - Address of net_device representing output device, 0 if unknown │ │ │ │

br_prid

│ │ │ │ Protocol identifier │ │ │ │ +

outdev

│ │ │ │ + Address of net_device representing output device, 0 if unknown │ │ │ │ +

br_max

│ │ │ │ + Max age in 1/256 secs │ │ │ │ +

length

│ │ │ │ + The length of the packet buffer contents, in bytes │ │ │ │ +

br_type

│ │ │ │ + BPDU type │ │ │ │ +

nf_drop

│ │ │ │ + Constant used to signify a 'drop' verdict │ │ │ │ +

data_hex

│ │ │ │ + A hexadecimal string representing the packet buffer contents │ │ │ │

pf

│ │ │ │ Protocol family -- always “bridge” │ │ │ │ +

nf_accept

│ │ │ │ + Constant used to signify an 'accept' verdict │ │ │ │ +

br_vid

│ │ │ │ + Protocol version identifier │ │ │ │ +

br_cost

│ │ │ │ + Total cost from transmitting bridge to root │ │ │ │ +

llcpdu

│ │ │ │ + Address of LLC Protocol Data Unit │ │ │ │ +

br_htime

│ │ │ │ + Hello time in 1/256 secs │ │ │ │ +

outdev_name

│ │ │ │ + Name of network device packet will be routed to (if known) │ │ │ │ +

data_str

│ │ │ │ + A string representing the packet buffer contents │ │ │ │ +

br_rmac

│ │ │ │ + Root bridge MAC address │ │ │ │

br_msg

│ │ │ │ Message age in 1/256 secs │ │ │ │

Prev Up Next
probe::netfilter.bridge.local_out Home probe::netfilter.bridge.pre_routing
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-netfilter-bridge-pre-routing.html │ │ │ │ @@ -1,67 +1,67 @@ │ │ │ │ probe::netfilter.bridge.pre_routing
probe::netfilter.bridge.pre_routing
Prev Chapter 13. Networking Tapset Next

Name

probe::netfilter.bridge.pre_routing — │ │ │ │ - Called before a bridging packet is routed │ │ │ │ -

Synopsis

netfilter.bridge.pre_routing

Values

brhdr

│ │ │ │ - Address of bridge header │ │ │ │ -

nf_stolen

│ │ │ │ - Constant used to signify a 'stolen' verdict │ │ │ │ -

llcproto_stp

│ │ │ │ - Constant used to signify Bridge Spanning Tree Protocol packet │ │ │ │ -

br_rmac

│ │ │ │ - Root bridge MAC address │ │ │ │ -

br_fd

│ │ │ │ - Forward delay in 1/256 secs │ │ │ │ +

Synopsis

netfilter.bridge.pre_routing

Values

br_cost

│ │ │ │ + Total cost from transmitting bridge to root │ │ │ │ +

nf_accept

│ │ │ │ + Constant used to signify an 'accept' verdict │ │ │ │

br_vid

│ │ │ │ Protocol version identifier │ │ │ │ -

data_hex

│ │ │ │ - A hexadecimal string representing the packet buffer contents │ │ │ │ -

nf_stop

│ │ │ │ - Constant used to signify a 'stop' verdict │ │ │ │ -

nf_drop

│ │ │ │ - Constant used to signify a 'drop' verdict │ │ │ │ +

br_type

│ │ │ │ + BPDU type │ │ │ │

br_max

│ │ │ │ Max age in 1/256 secs │ │ │ │ -

nf_accept

│ │ │ │ - Constant used to signify an 'accept' verdict │ │ │ │ -

nf_queue

│ │ │ │ - Constant used to signify a 'queue' verdict │ │ │ │ -

indev

│ │ │ │ - Address of net_device representing input device, 0 if unknown │ │ │ │

length

│ │ │ │ The length of the packet buffer contents, in bytes │ │ │ │ -

br_rid

│ │ │ │ - Identity of root bridge │ │ │ │ +

pf

│ │ │ │ + Protocol family -- always “bridge” │ │ │ │ +

nf_drop

│ │ │ │ + Constant used to signify a 'drop' verdict │ │ │ │ +

data_hex

│ │ │ │ + A hexadecimal string representing the packet buffer contents │ │ │ │ +

data_str

│ │ │ │ + A string representing the packet buffer contents │ │ │ │ +

br_msg

│ │ │ │ + Message age in 1/256 secs │ │ │ │ +

br_rmac

│ │ │ │ + Root bridge MAC address │ │ │ │ +

br_htime

│ │ │ │ + Hello time in 1/256 secs │ │ │ │ +

llcpdu

│ │ │ │ + Address of LLC Protocol Data Unit │ │ │ │ +

outdev_name

│ │ │ │ + Name of network device packet will be routed to (if known) │ │ │ │

nf_repeat

│ │ │ │ Constant used to signify a 'repeat' verdict │ │ │ │ +

br_flags

│ │ │ │ + BPDU flags │ │ │ │ +

indev

│ │ │ │ + Address of net_device representing input device, 0 if unknown │ │ │ │ +

nf_queue

│ │ │ │ + Constant used to signify a 'queue' verdict │ │ │ │

indev_name

│ │ │ │ Name of network device packet was received on (if known) │ │ │ │ +

nf_stolen

│ │ │ │ + Constant used to signify a 'stolen' verdict │ │ │ │

br_mac

│ │ │ │ Bridge MAC address │ │ │ │ -

br_flags

│ │ │ │ - BPDU flags │ │ │ │ -

outdev_name

│ │ │ │ - Name of network device packet will be routed to (if known) │ │ │ │ -

br_poid

│ │ │ │ - Port identifier │ │ │ │ -

br_type

│ │ │ │ - BPDU type │ │ │ │ -

protocol

│ │ │ │ - Packet protocol │ │ │ │ -

br_htime

│ │ │ │ - Hello time in 1/256 secs │ │ │ │ +

br_bid

│ │ │ │ + Identity of bridge │ │ │ │ +

llcproto_stp

│ │ │ │ + Constant used to signify Bridge Spanning Tree Protocol packet │ │ │ │

br_prid

│ │ │ │ Protocol identifier │ │ │ │

outdev

│ │ │ │ Address of net_device representing output device, 0 if unknown │ │ │ │ -

pf

│ │ │ │ - Protocol family -- always “bridge” │ │ │ │ -

br_msg

│ │ │ │ - Message age in 1/256 secs │ │ │ │ -

llcpdu

│ │ │ │ - Address of LLC Protocol Data Unit │ │ │ │ -

data_str

│ │ │ │ - A string representing the packet buffer contents │ │ │ │ -

br_bid

│ │ │ │ - Identity of bridge │ │ │ │ -

br_cost

│ │ │ │ - Total cost from transmitting bridge to root │ │ │ │ +

br_fd

│ │ │ │ + Forward delay in 1/256 secs │ │ │ │ +

br_poid

│ │ │ │ + Port identifier │ │ │ │ +

brhdr

│ │ │ │ + Address of bridge header │ │ │ │ +

protocol

│ │ │ │ + Packet protocol │ │ │ │ +

nf_stop

│ │ │ │ + Constant used to signify a 'stop' verdict │ │ │ │ +

br_rid

│ │ │ │ + Identity of root bridge │ │ │ │

Prev Up Next
probe::netfilter.bridge.post_routing Home probe::netfilter.ip.forward
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-netfilter-ip-forward.html │ │ │ │ @@ -1,61 +1,61 @@ │ │ │ │ probe::netfilter.ip.forward
probe::netfilter.ip.forward
Prev Chapter 13. Networking Tapset Next

Name

probe::netfilter.ip.forward — │ │ │ │ Called on an incoming IP packet addressed to some other computer │ │ │ │ -

Synopsis

netfilter.ip.forward

Values

daddr

│ │ │ │ - A string representing the destination IP address │ │ │ │ -

outdev

│ │ │ │ - Address of net_device representing output device, 0 if unknown │ │ │ │ -

pf

│ │ │ │ - Protocol family -- either “ipv4” or “ipv6” │ │ │ │ -

dport

│ │ │ │ - TCP or UDP destination port (ipv4 only) │ │ │ │ -

indev_name

│ │ │ │ - Name of network device packet was received on (if known) │ │ │ │ -

saddr

│ │ │ │ - A string representing the source IP address │ │ │ │ +

Synopsis

netfilter.ip.forward

Values

iphdr

│ │ │ │ + Address of IP header │ │ │ │ +

family

│ │ │ │ + IP address family │ │ │ │ +

ipproto_udp

│ │ │ │ + Constant used to signify that the packet protocol is UDP │ │ │ │

outdev_name

│ │ │ │ Name of network device packet will be routed to (if known) │ │ │ │ +

saddr

│ │ │ │ + A string representing the source IP address │ │ │ │

sport

│ │ │ │ TCP or UDP source port (ipv4 only) │ │ │ │ -

protocol

│ │ │ │ - Packet protocol from driver (ipv4 only) │ │ │ │

data_str

│ │ │ │ A string representing the packet buffer contents │ │ │ │ -

ipproto_tcp

│ │ │ │ - Constant used to signify that the packet protocol is TCP │ │ │ │ +

fin

│ │ │ │ + TCP FIN flag (if protocol is TCP; ipv4 only) │ │ │ │

rst

│ │ │ │ TCP RST flag (if protocol is TCP; ipv4 only) │ │ │ │ -

syn

│ │ │ │ - TCP SYN flag (if protocol is TCP; ipv4 only) │ │ │ │ -

family

│ │ │ │ - IP address family │ │ │ │ -

ipproto_udp

│ │ │ │ - Constant used to signify that the packet protocol is UDP │ │ │ │ -

urg

│ │ │ │ - TCP URG flag (if protocol is TCP; ipv4 only) │ │ │ │ +

pf

│ │ │ │ + Protocol family -- either “ipv4” or “ipv6” │ │ │ │

data_hex

│ │ │ │ A hexadecimal string representing the packet buffer contents │ │ │ │ -

fin

│ │ │ │ - TCP FIN flag (if protocol is TCP; ipv4 only) │ │ │ │

nf_drop

│ │ │ │ Constant used to signify a 'drop' verdict │ │ │ │ +

length

│ │ │ │ + The length of the packet buffer contents, in bytes │ │ │ │ +

nf_accept

│ │ │ │ + Constant used to signify an 'accept' verdict │ │ │ │

nf_stop

│ │ │ │ Constant used to signify a 'stop' verdict │ │ │ │ -

nf_stolen

│ │ │ │ - Constant used to signify a 'stolen' verdict │ │ │ │ -

psh

│ │ │ │ - TCP PSH flag (if protocol is TCP; ipv4 only) │ │ │ │ -

nf_repeat

│ │ │ │ - Constant used to signify a 'repeat' verdict │ │ │ │

ack

│ │ │ │ TCP ACK flag (if protocol is TCP; ipv4 only) │ │ │ │ -

nf_accept

│ │ │ │ - Constant used to signify an 'accept' verdict │ │ │ │ -

iphdr

│ │ │ │ - Address of IP header │ │ │ │ -

indev

│ │ │ │ - Address of net_device representing input device, 0 if unknown │ │ │ │ +

protocol

│ │ │ │ + Packet protocol from driver (ipv4 only) │ │ │ │ +

urg

│ │ │ │ + TCP URG flag (if protocol is TCP; ipv4 only) │ │ │ │ +

outdev

│ │ │ │ + Address of net_device representing output device, 0 if unknown │ │ │ │ +

psh

│ │ │ │ + TCP PSH flag (if protocol is TCP; ipv4 only) │ │ │ │ +

daddr

│ │ │ │ + A string representing the destination IP address │ │ │ │ +

nf_stolen

│ │ │ │ + Constant used to signify a 'stolen' verdict │ │ │ │

nf_queue

│ │ │ │ Constant used to signify a 'queue' verdict │ │ │ │ -

length

│ │ │ │ - The length of the packet buffer contents, in bytes │ │ │ │ +

indev_name

│ │ │ │ + Name of network device packet was received on (if known) │ │ │ │ +

ipproto_tcp

│ │ │ │ + Constant used to signify that the packet protocol is TCP │ │ │ │ +

indev

│ │ │ │ + Address of net_device representing input device, 0 if unknown │ │ │ │ +

syn

│ │ │ │ + TCP SYN flag (if protocol is TCP; ipv4 only) │ │ │ │ +

nf_repeat

│ │ │ │ + Constant used to signify a 'repeat' verdict │ │ │ │ +

dport

│ │ │ │ + TCP or UDP destination port (ipv4 only) │ │ │ │

Prev Up Next
probe::netfilter.bridge.pre_routing Home probe::netfilter.ip.local_in
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-netfilter-ip-local-in.html │ │ │ │ @@ -1,61 +1,61 @@ │ │ │ │ probe::netfilter.ip.local_in
probe::netfilter.ip.local_in
Prev Chapter 13. Networking Tapset Next

Name

probe::netfilter.ip.local_in — │ │ │ │ Called on an incoming IP packet addressed to the local computer │ │ │ │ -

Synopsis

netfilter.ip.local_in

Values

saddr

│ │ │ │ - A string representing the source IP address │ │ │ │ -

indev_name

│ │ │ │ - Name of network device packet was received on (if known) │ │ │ │ -

sport

│ │ │ │ - TCP or UDP source port (ipv4 only) │ │ │ │ -

protocol

│ │ │ │ - Packet protocol from driver (ipv4 only) │ │ │ │ -

outdev_name

│ │ │ │ - Name of network device packet will be routed to (if known) │ │ │ │ -

pf

│ │ │ │ - Protocol family -- either “ipv4” or “ipv6” │ │ │ │ -

outdev

│ │ │ │ - Address of net_device representing output device, 0 if unknown │ │ │ │ +

Synopsis

netfilter.ip.local_in

Values

ipproto_tcp

│ │ │ │ + Constant used to signify that the packet protocol is TCP │ │ │ │ +

indev

│ │ │ │ + Address of net_device representing input device, 0 if unknown │ │ │ │

daddr

│ │ │ │ A string representing the destination IP address │ │ │ │ +

nf_queue

│ │ │ │ + Constant used to signify a 'queue' verdict │ │ │ │ +

nf_stolen

│ │ │ │ + Constant used to signify a 'stolen' verdict │ │ │ │ +

indev_name

│ │ │ │ + Name of network device packet was received on (if known) │ │ │ │ +

nf_repeat

│ │ │ │ + Constant used to signify a 'repeat' verdict │ │ │ │

dport

│ │ │ │ TCP or UDP destination port (ipv4 only) │ │ │ │ -

ipproto_udp

│ │ │ │ - Constant used to signify that the packet protocol is UDP │ │ │ │ -

rst

│ │ │ │ - TCP RST flag (if protocol is TCP; ipv4 only) │ │ │ │ -

data_str

│ │ │ │ - A string representing the packet buffer contents │ │ │ │ -

ipproto_tcp

│ │ │ │ - Constant used to signify that the packet protocol is TCP │ │ │ │ -

family

│ │ │ │ - IP address family │ │ │ │

syn

│ │ │ │ TCP SYN flag (if protocol is TCP; ipv4 only) │ │ │ │ -

nf_stolen

│ │ │ │ - Constant used to signify a 'stolen' verdict │ │ │ │ -

fin

│ │ │ │ - TCP FIN flag (if protocol is TCP; ipv4 only) │ │ │ │ -

data_hex

│ │ │ │ - A hexadecimal string representing the packet buffer contents │ │ │ │ -

urg

│ │ │ │ - TCP URG flag (if protocol is TCP; ipv4 only) │ │ │ │ +

ack

│ │ │ │ + TCP ACK flag (if protocol is TCP; ipv4 only) │ │ │ │ +

protocol

│ │ │ │ + Packet protocol from driver (ipv4 only) │ │ │ │

nf_stop

│ │ │ │ Constant used to signify a 'stop' verdict │ │ │ │ +

psh

│ │ │ │ + TCP PSH flag (if protocol is TCP; ipv4 only) │ │ │ │ +

urg

│ │ │ │ + TCP URG flag (if protocol is TCP; ipv4 only) │ │ │ │ +

outdev

│ │ │ │ + Address of net_device representing output device, 0 if unknown │ │ │ │ +

length

│ │ │ │ + The length of the packet buffer contents, in bytes │ │ │ │ +

pf

│ │ │ │ + Protocol family -- either “ipv4” or “ipv6” │ │ │ │ +

data_hex

│ │ │ │ + A hexadecimal string representing the packet buffer contents │ │ │ │

nf_drop

│ │ │ │ Constant used to signify a 'drop' verdict │ │ │ │ -

nf_queue

│ │ │ │ - Constant used to signify a 'queue' verdict │ │ │ │ -

indev

│ │ │ │ - Address of net_device representing input device, 0 if unknown │ │ │ │

nf_accept

│ │ │ │ Constant used to signify an 'accept' verdict │ │ │ │ +

saddr

│ │ │ │ + A string representing the source IP address │ │ │ │ +

family

│ │ │ │ + IP address family │ │ │ │

iphdr

│ │ │ │ Address of IP header │ │ │ │ -

length

│ │ │ │ - The length of the packet buffer contents, in bytes │ │ │ │ -

psh

│ │ │ │ - TCP PSH flag (if protocol is TCP; ipv4 only) │ │ │ │ -

nf_repeat

│ │ │ │ - Constant used to signify a 'repeat' verdict │ │ │ │ -

ack

│ │ │ │ - TCP ACK flag (if protocol is TCP; ipv4 only) │ │ │ │ +

ipproto_udp

│ │ │ │ + Constant used to signify that the packet protocol is UDP │ │ │ │ +

outdev_name

│ │ │ │ + Name of network device packet will be routed to (if known) │ │ │ │ +

data_str

│ │ │ │ + A string representing the packet buffer contents │ │ │ │ +

fin

│ │ │ │ + TCP FIN flag (if protocol is TCP; ipv4 only) │ │ │ │ +

rst

│ │ │ │ + TCP RST flag (if protocol is TCP; ipv4 only) │ │ │ │ +

sport

│ │ │ │ + TCP or UDP source port (ipv4 only) │ │ │ │

Prev Up Next
probe::netfilter.ip.forward Home probe::netfilter.ip.local_out
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-netfilter-ip-local-out.html │ │ │ │ @@ -1,61 +1,61 @@ │ │ │ │ probe::netfilter.ip.local_out
probe::netfilter.ip.local_out
Prev Chapter 13. Networking Tapset Next

Name

probe::netfilter.ip.local_out — │ │ │ │ Called on an outgoing IP packet │ │ │ │ -

Synopsis

netfilter.ip.local_out

Values

ipproto_udp

│ │ │ │ +

Synopsis

netfilter.ip.local_out

Values

data_hex

│ │ │ │ + A hexadecimal string representing the packet buffer contents │ │ │ │ +

nf_drop

│ │ │ │ + Constant used to signify a 'drop' verdict │ │ │ │ +

pf

│ │ │ │ + Protocol family -- either “ipv4” or “ipv6” │ │ │ │ +

length

│ │ │ │ + The length of the packet buffer contents, in bytes │ │ │ │ +

nf_accept

│ │ │ │ + Constant used to signify an 'accept' verdict │ │ │ │ +

outdev_name

│ │ │ │ + Name of network device packet will be routed to (if known) │ │ │ │ +

ipproto_udp

│ │ │ │ Constant used to signify that the packet protocol is UDP │ │ │ │ -

rst

│ │ │ │ - TCP RST flag (if protocol is TCP; ipv4 only) │ │ │ │ -

data_str

│ │ │ │ - A string representing the packet buffer contents │ │ │ │ -

ipproto_tcp

│ │ │ │ - Constant used to signify that the packet protocol is TCP │ │ │ │

family

│ │ │ │ IP address family │ │ │ │ -

syn

│ │ │ │ - TCP SYN flag (if protocol is TCP; ipv4 only) │ │ │ │ +

iphdr

│ │ │ │ + Address of IP header │ │ │ │

saddr

│ │ │ │ A string representing the source IP address │ │ │ │ -

indev_name

│ │ │ │ - Name of network device packet was received on (if known) │ │ │ │ -

protocol

│ │ │ │ - Packet protocol from driver (ipv4 only) │ │ │ │

sport

│ │ │ │ TCP or UDP source port (ipv4 only) │ │ │ │ -

outdev_name

│ │ │ │ - Name of network device packet will be routed to (if known) │ │ │ │ -

pf

│ │ │ │ - Protocol family -- either “ipv4” or “ipv6” │ │ │ │ -

outdev

│ │ │ │ - Address of net_device representing output device, 0 if unknown │ │ │ │ -

daddr

│ │ │ │ - A string representing the destination IP address │ │ │ │ -

dport

│ │ │ │ - TCP or UDP destination port (ipv4 only) │ │ │ │ +

rst

│ │ │ │ + TCP RST flag (if protocol is TCP; ipv4 only) │ │ │ │ +

fin

│ │ │ │ + TCP FIN flag (if protocol is TCP; ipv4 only) │ │ │ │ +

data_str

│ │ │ │ + A string representing the packet buffer contents │ │ │ │ +

indev_name

│ │ │ │ + Name of network device packet was received on (if known) │ │ │ │

nf_queue

│ │ │ │ Constant used to signify a 'queue' verdict │ │ │ │ +

nf_stolen

│ │ │ │ + Constant used to signify a 'stolen' verdict │ │ │ │ +

daddr

│ │ │ │ + A string representing the destination IP address │ │ │ │

indev

│ │ │ │ Address of net_device representing input device, 0 if unknown │ │ │ │ -

nf_accept

│ │ │ │ - Constant used to signify an 'accept' verdict │ │ │ │ -

iphdr

│ │ │ │ - Address of IP header │ │ │ │ -

length

│ │ │ │ - The length of the packet buffer contents, in bytes │ │ │ │ +

ipproto_tcp

│ │ │ │ + Constant used to signify that the packet protocol is TCP │ │ │ │ +

syn

│ │ │ │ + TCP SYN flag (if protocol is TCP; ipv4 only) │ │ │ │ +

dport

│ │ │ │ + TCP or UDP destination port (ipv4 only) │ │ │ │

nf_repeat

│ │ │ │ Constant used to signify a 'repeat' verdict │ │ │ │ -

psh

│ │ │ │ - TCP PSH flag (if protocol is TCP; ipv4 only) │ │ │ │ +

nf_stop

│ │ │ │ + Constant used to signify a 'stop' verdict │ │ │ │ +

protocol

│ │ │ │ + Packet protocol from driver (ipv4 only) │ │ │ │

ack

│ │ │ │ TCP ACK flag (if protocol is TCP; ipv4 only) │ │ │ │ -

nf_stolen

│ │ │ │ - Constant used to signify a 'stolen' verdict │ │ │ │ -

fin

│ │ │ │ - TCP FIN flag (if protocol is TCP; ipv4 only) │ │ │ │ +

outdev

│ │ │ │ + Address of net_device representing output device, 0 if unknown │ │ │ │

urg

│ │ │ │ TCP URG flag (if protocol is TCP; ipv4 only) │ │ │ │ -

data_hex

│ │ │ │ - A hexadecimal string representing the packet buffer contents │ │ │ │ -

nf_stop

│ │ │ │ - Constant used to signify a 'stop' verdict │ │ │ │ -

nf_drop

│ │ │ │ - Constant used to signify a 'drop' verdict │ │ │ │ +

psh

│ │ │ │ + TCP PSH flag (if protocol is TCP; ipv4 only) │ │ │ │

Prev Up Next
probe::netfilter.ip.local_in Home probe::netfilter.ip.post_routing
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-netfilter-ip-post-routing.html │ │ │ │ @@ -1,61 +1,61 @@ │ │ │ │ probe::netfilter.ip.post_routing
probe::netfilter.ip.post_routing
Prev Chapter 13. Networking Tapset Next

Name

probe::netfilter.ip.post_routing — │ │ │ │ Called immediately before an outgoing IP packet leaves the computer │ │ │ │ -

Synopsis

netfilter.ip.post_routing

Values

nf_accept

│ │ │ │ - Constant used to signify an 'accept' verdict │ │ │ │ -

iphdr

│ │ │ │ - Address of IP header │ │ │ │ -

nf_queue

│ │ │ │ - Constant used to signify a 'queue' verdict │ │ │ │ +

Synopsis

netfilter.ip.post_routing

Values

nf_repeat

│ │ │ │ + Constant used to signify a 'repeat' verdict │ │ │ │ +

dport

│ │ │ │ + TCP or UDP destination port (ipv4 only) │ │ │ │ +

syn

│ │ │ │ + TCP SYN flag (if protocol is TCP; ipv4 only) │ │ │ │ +

ipproto_tcp

│ │ │ │ + Constant used to signify that the packet protocol is TCP │ │ │ │

indev

│ │ │ │ Address of net_device representing input device, 0 if unknown │ │ │ │ -

length

│ │ │ │ - The length of the packet buffer contents, in bytes │ │ │ │ -

psh

│ │ │ │ - TCP PSH flag (if protocol is TCP; ipv4 only) │ │ │ │ -

nf_repeat

│ │ │ │ - Constant used to signify a 'repeat' verdict │ │ │ │ -

ack

│ │ │ │ - TCP ACK flag (if protocol is TCP; ipv4 only) │ │ │ │ +

daddr

│ │ │ │ + A string representing the destination IP address │ │ │ │ +

nf_queue

│ │ │ │ + Constant used to signify a 'queue' verdict │ │ │ │ +

indev_name

│ │ │ │ + Name of network device packet was received on (if known) │ │ │ │

nf_stolen

│ │ │ │ Constant used to signify a 'stolen' verdict │ │ │ │ +

psh

│ │ │ │ + TCP PSH flag (if protocol is TCP; ipv4 only) │ │ │ │

urg

│ │ │ │ TCP URG flag (if protocol is TCP; ipv4 only) │ │ │ │ -

data_hex

│ │ │ │ - A hexadecimal string representing the packet buffer contents │ │ │ │ -

fin

│ │ │ │ - TCP FIN flag (if protocol is TCP; ipv4 only) │ │ │ │ +

outdev

│ │ │ │ + Address of net_device representing output device, 0 if unknown │ │ │ │ +

ack

│ │ │ │ + TCP ACK flag (if protocol is TCP; ipv4 only) │ │ │ │ +

protocol

│ │ │ │ + Packet protocol from driver (ipv4 only) │ │ │ │

nf_stop

│ │ │ │ Constant used to signify a 'stop' verdict │ │ │ │ +

nf_accept

│ │ │ │ + Constant used to signify an 'accept' verdict │ │ │ │ +

length

│ │ │ │ + The length of the packet buffer contents, in bytes │ │ │ │ +

pf

│ │ │ │ + Protocol family -- either “ipv4” or “ipv6” │ │ │ │

nf_drop

│ │ │ │ Constant used to signify a 'drop' verdict │ │ │ │ -

ipproto_udp

│ │ │ │ - Constant used to signify that the packet protocol is UDP │ │ │ │ -

ipproto_tcp

│ │ │ │ - Constant used to signify that the packet protocol is TCP │ │ │ │ -

data_str

│ │ │ │ - A string representing the packet buffer contents │ │ │ │ +

data_hex

│ │ │ │ + A hexadecimal string representing the packet buffer contents │ │ │ │

rst

│ │ │ │ TCP RST flag (if protocol is TCP; ipv4 only) │ │ │ │ -

syn

│ │ │ │ - TCP SYN flag (if protocol is TCP; ipv4 only) │ │ │ │ -

family

│ │ │ │ - IP address family │ │ │ │ -

indev_name

│ │ │ │ - Name of network device packet was received on (if known) │ │ │ │ +

fin

│ │ │ │ + TCP FIN flag (if protocol is TCP; ipv4 only) │ │ │ │ +

data_str

│ │ │ │ + A string representing the packet buffer contents │ │ │ │ +

sport

│ │ │ │ + TCP or UDP source port (ipv4 only) │ │ │ │

saddr

│ │ │ │ A string representing the source IP address │ │ │ │ +

family

│ │ │ │ + IP address family │ │ │ │ +

iphdr

│ │ │ │ + Address of IP header │ │ │ │ +

ipproto_udp

│ │ │ │ + Constant used to signify that the packet protocol is UDP │ │ │ │

outdev_name

│ │ │ │ Name of network device packet will be routed to (if known) │ │ │ │ -

sport

│ │ │ │ - TCP or UDP source port (ipv4 only) │ │ │ │ -

protocol

│ │ │ │ - Packet protocol from driver (ipv4 only) │ │ │ │ -

outdev

│ │ │ │ - Address of net_device representing output device, 0 if unknown │ │ │ │ -

daddr

│ │ │ │ - A string representing the destination IP address │ │ │ │ -

pf

│ │ │ │ - Protocol family -- either “ipv4” or “ipv6” │ │ │ │ -

dport

│ │ │ │ - TCP or UDP destination port (ipv4 only) │ │ │ │

Prev Up Next
probe::netfilter.ip.local_out Home probe::netfilter.ip.pre_routing
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-netfilter-ip-pre-routing.html │ │ │ │ @@ -1,61 +1,61 @@ │ │ │ │ probe::netfilter.ip.pre_routing
probe::netfilter.ip.pre_routing
Prev Chapter 13. Networking Tapset Next

Name

probe::netfilter.ip.pre_routing — │ │ │ │ Called before an IP packet is routed │ │ │ │ -

Synopsis

netfilter.ip.pre_routing

Values

dport

│ │ │ │ +

Synopsis

netfilter.ip.pre_routing

Values

syn

│ │ │ │ + TCP SYN flag (if protocol is TCP; ipv4 only) │ │ │ │ +

nf_repeat

│ │ │ │ + Constant used to signify a 'repeat' verdict │ │ │ │ +

dport

│ │ │ │ TCP or UDP destination port (ipv4 only) │ │ │ │ -

outdev

│ │ │ │ - Address of net_device representing output device, 0 if unknown │ │ │ │ -

daddr

│ │ │ │ - A string representing the destination IP address │ │ │ │ -

pf

│ │ │ │ - Protocol family - either 'ipv4' or 'ipv6' │ │ │ │ -

outdev_name

│ │ │ │ - Name of network device packet will be routed to (if known) │ │ │ │ -

protocol

│ │ │ │ - Packet protocol from driver (ipv4 only) │ │ │ │ -

sport

│ │ │ │ - TCP or UDP source port (ipv4 only) │ │ │ │

indev_name

│ │ │ │ Name of network device packet was received on (if known) │ │ │ │ -

saddr

│ │ │ │ - A string representing the source IP address │ │ │ │ -

syn

│ │ │ │ - TCP SYN flag (if protocol is TCP; ipv4 only) │ │ │ │ -

family

│ │ │ │ - IP address family │ │ │ │ +

nf_stolen

│ │ │ │ + Constant used to signify a 'stolen' verdict │ │ │ │ +

nf_queue

│ │ │ │ + Constant used to signify a 'queue' verdict │ │ │ │ +

daddr

│ │ │ │ + A string representing the destination IP address │ │ │ │ +

indev

│ │ │ │ + Address of net_device representing input device, 0 if unknown │ │ │ │

ipproto_tcp

│ │ │ │ Constant used to signify that the packet protocol is TCP │ │ │ │ -

data_str

│ │ │ │ - A string representing the packet buffer contents │ │ │ │ -

rst

│ │ │ │ - TCP RST flag (if protocol is TCP; ipv4 only) │ │ │ │ -

ipproto_udp

│ │ │ │ - Constant used to signify that the packet protocol is UDP │ │ │ │ -

nf_stop

│ │ │ │ - Constant used to signify a 'stop' verdict │ │ │ │ -

nf_drop

│ │ │ │ - Constant used to signify a 'drop' verdict │ │ │ │ +

outdev

│ │ │ │ + Address of net_device representing output device, 0 if unknown │ │ │ │

urg

│ │ │ │ TCP URG flag (if protocol is TCP; ipv4 only) │ │ │ │ -

data_hex

│ │ │ │ - A hexadecimal string representing the packet buffer contents │ │ │ │ -

fin

│ │ │ │ - TCP FIN flag (if protocol is TCP; ipv4 only) │ │ │ │ -

nf_stolen

│ │ │ │ - Constant used to signify a 'stolen' verdict │ │ │ │ -

ack

│ │ │ │ - TCP ACK flag (if protocol is TCP; ipv4 only) │ │ │ │

psh

│ │ │ │ TCP PSH flag (if protocol is TCP; ipv4 only) │ │ │ │ -

nf_repeat

│ │ │ │ - Constant used to signify a 'repeat' verdict │ │ │ │ +

nf_stop

│ │ │ │ + Constant used to signify a 'stop' verdict │ │ │ │ +

ack

│ │ │ │ + TCP ACK flag (if protocol is TCP; ipv4 only) │ │ │ │ +

protocol

│ │ │ │ + Packet protocol from driver (ipv4 only) │ │ │ │ +

nf_accept

│ │ │ │ + Constant used to signify an 'accept' verdict │ │ │ │ +

pf

│ │ │ │ + Protocol family - either 'ipv4' or 'ipv6' │ │ │ │ +

data_hex

│ │ │ │ + A hexadecimal string representing the packet buffer contents │ │ │ │ +

nf_drop

│ │ │ │ + Constant used to signify a 'drop' verdict │ │ │ │

length

│ │ │ │ The length of the packet buffer contents, in bytes │ │ │ │ +

sport

│ │ │ │ + TCP or UDP source port (ipv4 only) │ │ │ │ +

fin

│ │ │ │ + TCP FIN flag (if protocol is TCP; ipv4 only) │ │ │ │ +

rst

│ │ │ │ + TCP RST flag (if protocol is TCP; ipv4 only) │ │ │ │ +

data_str

│ │ │ │ + A string representing the packet buffer contents │ │ │ │ +

ipproto_udp

│ │ │ │ + Constant used to signify that the packet protocol is UDP │ │ │ │ +

family

│ │ │ │ + IP address family │ │ │ │

iphdr

│ │ │ │ Address of IP header │ │ │ │ -

nf_accept

│ │ │ │ - Constant used to signify an 'accept' verdict │ │ │ │ -

nf_queue

│ │ │ │ - Constant used to signify a 'queue' verdict │ │ │ │ -

indev

│ │ │ │ - Address of net_device representing input device, 0 if unknown │ │ │ │ +

outdev_name

│ │ │ │ + Name of network device packet will be routed to (if known) │ │ │ │ +

saddr

│ │ │ │ + A string representing the source IP address │ │ │ │

Prev Up Next
probe::netfilter.ip.post_routing Home probe::sunrpc.clnt.bind_new_program
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-aop-readahead.html │ │ │ │ @@ -1,19 +1,19 @@ │ │ │ │ probe::nfs.aop.readahead
probe::nfs.aop.readahead
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.aop.readahead — │ │ │ │ NFS client reading multiple pages │ │ │ │ -

Synopsis

nfs.aop.readahead

Values

rpages

│ │ │ │ - read size (in pages) │ │ │ │ +

Synopsis

nfs.aop.readahead

Values

rsize

│ │ │ │ + read size (in bytes) │ │ │ │

ino

│ │ │ │ inode number │ │ │ │

nr_pages

│ │ │ │ number of pages attempted to read in this execution │ │ │ │ -

rsize

│ │ │ │ - read size (in bytes) │ │ │ │ -

file

│ │ │ │ - filp argument │ │ │ │ -

size

│ │ │ │ - number of pages attempted to read in this execution │ │ │ │

dev

│ │ │ │ device identifier │ │ │ │ +

size

│ │ │ │ + number of pages attempted to read in this execution │ │ │ │ +

rpages

│ │ │ │ + read size (in pages) │ │ │ │ +

file

│ │ │ │ + filp argument │ │ │ │

Description

│ │ │ │ Fires when in readahead way, read several pages once │ │ │ │

Prev Up Next
probe:: Home probe::nfs.aop.readpage
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-aop-readpage.html │ │ │ │ @@ -1,27 +1,27 @@ │ │ │ │ probe::nfs.aop.readpage
probe::nfs.aop.readpage
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.aop.readpage — │ │ │ │ NFS client synchronously reading a page │ │ │ │ -

Synopsis

nfs.aop.readpage

Values

file

│ │ │ │ - file argument │ │ │ │ -

size

│ │ │ │ - number of pages to be read in this execution │ │ │ │ +

Synopsis

nfs.aop.readpage

Values

i_size

│ │ │ │ + file length in bytes │ │ │ │ +

i_flag

│ │ │ │ + file flags │ │ │ │ +

sb_flag

│ │ │ │ + super block flags │ │ │ │

dev

│ │ │ │ device identifier │ │ │ │ +

rsize

│ │ │ │ + read size (in bytes) │ │ │ │ +

ino

│ │ │ │ + inode number │ │ │ │ +

file

│ │ │ │ + file argument │ │ │ │

__page

│ │ │ │ the address of page │ │ │ │ -

i_flag

│ │ │ │ - file flags │ │ │ │ -

i_size

│ │ │ │ - file length in bytes │ │ │ │

page_index

│ │ │ │ offset within mapping, can used a page identifier │ │ │ │ and position identifier in the page frame │ │ │ │ -

rsize

│ │ │ │ - read size (in bytes) │ │ │ │ -

sb_flag

│ │ │ │ - super block flags │ │ │ │ -

ino

│ │ │ │ - inode number │ │ │ │ +

size

│ │ │ │ + number of pages to be read in this execution │ │ │ │

Description

│ │ │ │ Read the page over, only fires when a previous async │ │ │ │ read operation failed │ │ │ │

Prev Up Next
probe::nfs.aop.readahead Home probe::nfs.aop.readpages
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-aop-readpages.html │ │ │ │ @@ -1,19 +1,19 @@ │ │ │ │ probe::nfs.aop.readpages
probe::nfs.aop.readpages
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.aop.readpages — │ │ │ │ NFS client reading multiple pages │ │ │ │ -

Synopsis

nfs.aop.readpages

Values

nr_pages

│ │ │ │ +

Synopsis

nfs.aop.readpages

Values

file

│ │ │ │ + filp argument │ │ │ │ +

size

│ │ │ │ number of pages attempted to read in this execution │ │ │ │ -

rsize

│ │ │ │ - read size (in bytes) │ │ │ │

rpages

│ │ │ │ read size (in pages) │ │ │ │ -

ino

│ │ │ │ - inode number │ │ │ │ -

file

│ │ │ │ - filp argument │ │ │ │ -

size

│ │ │ │ +

nr_pages

│ │ │ │ number of pages attempted to read in this execution │ │ │ │

dev

│ │ │ │ device identifier │ │ │ │ +

rsize

│ │ │ │ + read size (in bytes) │ │ │ │ +

ino

│ │ │ │ + inode number │ │ │ │

Description

│ │ │ │ Fires when in readahead way, read several pages once │ │ │ │

Prev Up Next
probe::nfs.aop.readpage Home probe::nfs.aop.release_page
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-aop-release-page.html │ │ │ │ @@ -1,16 +1,16 @@ │ │ │ │ probe::nfs.aop.release_page
probe::nfs.aop.release_page
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.aop.release_page — │ │ │ │ NFS client releasing page │ │ │ │ -

Synopsis

nfs.aop.release_page

Values

dev

│ │ │ │ +

Synopsis

nfs.aop.release_page

Values

ino

│ │ │ │ + inode number │ │ │ │ +

dev

│ │ │ │ device identifier │ │ │ │ +

page_index

│ │ │ │ + offset within mapping, can used a page identifier │ │ │ │ + and position identifier in the page frame │ │ │ │

size

│ │ │ │ release pages │ │ │ │ -

ino

│ │ │ │ - inode number │ │ │ │

__page

│ │ │ │ the address of page │ │ │ │ -

page_index

│ │ │ │ - offset within mapping, can used a page identifier │ │ │ │ - and position identifier in the page frame │ │ │ │

Description

│ │ │ │ Fires when do a release operation on NFS. │ │ │ │

Prev Up Next
probe::nfs.aop.readpages Home probe::nfs.aop.set_page_dirty
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-aop-write-begin.html │ │ │ │ @@ -1,21 +1,21 @@ │ │ │ │ probe::nfs.aop.write_begin
probe::nfs.aop.write_begin
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.aop.write_begin — │ │ │ │ NFS client begin to write data │ │ │ │ -

Synopsis

nfs.aop.write_begin

Values

offset

│ │ │ │ - start address of this write operation │ │ │ │ -

size

│ │ │ │ - write bytes │ │ │ │ -

dev

│ │ │ │ +

Synopsis

nfs.aop.write_begin

Values

dev

│ │ │ │ device identifier │ │ │ │ +

offset

│ │ │ │ + start address of this write operation │ │ │ │

to

│ │ │ │ end address of this write operation │ │ │ │

ino

│ │ │ │ inode number │ │ │ │

__page

│ │ │ │ the address of page │ │ │ │ +

size

│ │ │ │ + write bytes │ │ │ │

page_index

│ │ │ │ offset within mapping, can used a page identifier │ │ │ │ and position identifier in the page frame │ │ │ │

Description

│ │ │ │ Occurs when write operation occurs on nfs. It prepare a page for writing, │ │ │ │ look for a request corresponding to the page. If there │ │ │ │ is one, and it belongs to another file, it flush it out │ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-aop-write-end.html │ │ │ │ @@ -1,27 +1,27 @@ │ │ │ │ probe::nfs.aop.write_end

probe::nfs.aop.write_end
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.aop.write_end — │ │ │ │ NFS client complete writing data │ │ │ │ -

Synopsis

nfs.aop.write_end

Values

page_index

│ │ │ │ +

Synopsis

nfs.aop.write_end

Values

size

│ │ │ │ + write bytes │ │ │ │ +

page_index

│ │ │ │ offset within mapping, can used a page identifier and position identifier in the page frame │ │ │ │

__page

│ │ │ │ the address of page │ │ │ │ -

sb_flag

│ │ │ │ - super block flags │ │ │ │ +

to

│ │ │ │ + end address of this write operation │ │ │ │

ino

│ │ │ │ inode number │ │ │ │ +

sb_flag

│ │ │ │ + super block flags │ │ │ │ +

dev

│ │ │ │ + device identifier │ │ │ │

i_size

│ │ │ │ file length in bytes │ │ │ │ -

to

│ │ │ │ - end address of this write operation │ │ │ │

i_flag

│ │ │ │ file flags │ │ │ │ -

dev

│ │ │ │ - device identifier │ │ │ │ -

size

│ │ │ │ - write bytes │ │ │ │

offset

│ │ │ │ start address of this write operation │ │ │ │

Description

│ │ │ │ Fires when do a write operation on nfs, │ │ │ │ often after prepare_write │ │ │ │

│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-aop-writepage.html │ │ │ │ @@ -1,33 +1,33 @@ │ │ │ │ probe::nfs.aop.writepage

probe::nfs.aop.writepage
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.aop.writepage — │ │ │ │ NFS client writing a mapped page to the NFS server │ │ │ │ -

Synopsis

nfs.aop.writepage

Values

__page

│ │ │ │ +

Synopsis

nfs.aop.writepage

Values

wsize

│ │ │ │ + write size │ │ │ │ +

__page

│ │ │ │ the address of page │ │ │ │ -

i_state

│ │ │ │ - inode state flags │ │ │ │ -

for_reclaim

│ │ │ │ - a flag of writeback_control, │ │ │ │ - indicates if it's invoked from the page allocator │ │ │ │

page_index

│ │ │ │ offset within mapping, │ │ │ │ can used a page identifier and position identifier in the page frame │ │ │ │ +

size

│ │ │ │ + number of pages to be written in this execution │ │ │ │ +

for_reclaim

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

i_flag

│ │ │ │ file flags │ │ │ │ +

i_size

│ │ │ │ + file length in bytes │ │ │ │

dev

│ │ │ │ device identifier │ │ │ │ +

i_state

│ │ │ │ + inode state flags │ │ │ │ +

sb_flag

│ │ │ │ + super block flags │ │ │ │ +

ino

│ │ │ │ + inode number │ │ │ │

for_kupdate

│ │ │ │ a flag of writeback_control, │ │ │ │ indicates if it's a kupdate writeback │ │ │ │ -

size

│ │ │ │ - number of pages to be written in this execution │ │ │ │ -

ino

│ │ │ │ - inode number │ │ │ │ -

sb_flag

│ │ │ │ - super block flags │ │ │ │ -

wsize

│ │ │ │ - write size │ │ │ │ -

i_size

│ │ │ │ - file length in bytes │ │ │ │

Description

│ │ │ │ The priority of wb is decided by the flags │ │ │ │ for_reclaim and for_kupdate. │ │ │ │

Prev Up Next
probe::nfs.aop.write_end Home probe::nfs.aop.writepages
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-aop-writepages.html │ │ │ │ @@ -1,24 +1,24 @@ │ │ │ │ probe::nfs.aop.writepages
probe::nfs.aop.writepages
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.aop.writepages — │ │ │ │ NFS client writing several dirty pages to the NFS server │ │ │ │ -

Synopsis

nfs.aop.writepages

Values

wsize

│ │ │ │ - write size │ │ │ │ -

nr_to_write

│ │ │ │ - number of pages attempted to be written in this execution │ │ │ │ +

Synopsis

nfs.aop.writepages

Values

dev

│ │ │ │ + device identifier │ │ │ │

wpages

│ │ │ │ write size (in pages) │ │ │ │ -

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 │ │ │ │ +

ino

│ │ │ │ + inode number │ │ │ │ +

nr_to_write

│ │ │ │ + number of pages attempted to be written in this execution │ │ │ │ +

wsize

│ │ │ │ + write size │ │ │ │

size

│ │ │ │ number of pages attempted to be written in this execution │ │ │ │ -

dev

│ │ │ │ - device identifier │ │ │ │ -

for_reclaim

│ │ │ │ - a flag of writeback_control, │ │ │ │ - indicates if it's invoked from the page allocator │ │ │ │

Description

│ │ │ │ The priority of wb is decided by the flags │ │ │ │ for_reclaim and for_kupdate. │ │ │ │

Prev Up Next
probe::nfs.aop.writepage Home probe::nfs.fop.aio_read
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-aio-read.html │ │ │ │ @@ -1,25 +1,25 @@ │ │ │ │ probe::nfs.fop.aio_read
probe::nfs.fop.aio_read
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.fop.aio_read — │ │ │ │ NFS client aio_read file operation │ │ │ │ -

Synopsis

nfs.fop.aio_read

Values

cache_time

│ │ │ │ - when we started read-caching this inode │ │ │ │ -

pos

│ │ │ │ - current position of file │ │ │ │ +

Synopsis

nfs.fop.aio_read

Values

parent_name

│ │ │ │ + parent dir name │ │ │ │ +

count

│ │ │ │ + read bytes │ │ │ │

attrtimeo

│ │ │ │ how long the cached information is assumed to be valid. │ │ │ │ We need to revalidate the cached attrs for this inode │ │ │ │ if jiffies - read_cache_jiffies > attrtimeo. │ │ │ │

dev

│ │ │ │ device identifier │ │ │ │ +

pos

│ │ │ │ + current position of file │ │ │ │ +

cache_time

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

cache_valid

│ │ │ │ + cache related bit mask flag │ │ │ │

file_name

│ │ │ │ file name │ │ │ │

ino

│ │ │ │ inode number │ │ │ │

buf

│ │ │ │ the address of buf in user space │ │ │ │ -

cache_valid

│ │ │ │ - cache related bit mask flag │ │ │ │ -

count

│ │ │ │ - read bytes │ │ │ │ -

parent_name

│ │ │ │ - parent dir name │ │ │ │

Prev Up Next
probe::nfs.aop.writepages Home probe::nfs.fop.aio_write
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-aio-write.html │ │ │ │ @@ -1,17 +1,17 @@ │ │ │ │ probe::nfs.fop.aio_write
probe::nfs.fop.aio_write
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.fop.aio_write — │ │ │ │ NFS client aio_write file operation │ │ │ │ -

Synopsis

nfs.fop.aio_write

Values

dev

│ │ │ │ - device identifier │ │ │ │ -

pos

│ │ │ │ - offset of the file │ │ │ │ -

parent_name

│ │ │ │ - parent dir name │ │ │ │ -

count

│ │ │ │ - read bytes │ │ │ │ -

file_name

│ │ │ │ +

Synopsis

nfs.fop.aio_write

Values

file_name

│ │ │ │ file name │ │ │ │

ino

│ │ │ │ inode number │ │ │ │

buf

│ │ │ │ the address of buf in user space │ │ │ │ +

parent_name

│ │ │ │ + parent dir name │ │ │ │ +

dev

│ │ │ │ + device identifier │ │ │ │ +

count

│ │ │ │ + read bytes │ │ │ │ +

pos

│ │ │ │ + offset of the file │ │ │ │

Prev Up Next
probe::nfs.fop.aio_read Home probe::nfs.fop.check_flags
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-flush.html │ │ │ │ @@ -1,11 +1,11 @@ │ │ │ │ probe::nfs.fop.flush
probe::nfs.fop.flush
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.fop.flush — │ │ │ │ NFS client flush file operation │ │ │ │ -

Synopsis

nfs.fop.flush

Values

dev

│ │ │ │ +

Synopsis

nfs.fop.flush

Values

ino

│ │ │ │ + inode number │ │ │ │ +

dev

│ │ │ │ device identifier │ │ │ │ -

ndirty

│ │ │ │ - number of dirty page │ │ │ │

mode

│ │ │ │ file mode │ │ │ │ -

ino

│ │ │ │ - inode number │ │ │ │ +

ndirty

│ │ │ │ + number of dirty page │ │ │ │

Prev Up Next
probe::nfs.fop.check_flags Home probe::nfs.fop.fsync
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-fsync.html │ │ │ │┄ Ordering differences only │ │ │ │ @@ -1,9 +1,9 @@ │ │ │ │ probe::nfs.fop.fsync
probe::nfs.fop.fsync
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.fop.fsync — │ │ │ │ NFS client fsync operation │ │ │ │

Synopsis

nfs.fop.fsync

Values

dev

│ │ │ │ device identifier │ │ │ │ -

ndirty

│ │ │ │ - number of dirty pages │ │ │ │

ino

│ │ │ │ inode number │ │ │ │ +

ndirty

│ │ │ │ + number of dirty pages │ │ │ │

Prev Up Next
probe::nfs.fop.flush Home probe::nfs.fop.llseek
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-llseek.html │ │ │ │┄ Ordering differences only │ │ │ │ @@ -1,13 +1,13 @@ │ │ │ │ probe::nfs.fop.llseek
probe::nfs.fop.llseek
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.fop.llseek — │ │ │ │ NFS client llseek operation │ │ │ │

Synopsis

nfs.fop.llseek

Values

whence_str

│ │ │ │ symbolic string representation of the position to seek from │ │ │ │ -

offset

│ │ │ │ - the offset of the file will be repositioned │ │ │ │ -

dev

│ │ │ │ - device identifier │ │ │ │

whence

│ │ │ │ the position to seek from │ │ │ │

ino

│ │ │ │ inode number │ │ │ │ +

offset

│ │ │ │ + the offset of the file will be repositioned │ │ │ │ +

dev

│ │ │ │ + device identifier │ │ │ │

Prev Up Next
probe::nfs.fop.fsync Home probe::nfs.fop.lock
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-lock.html │ │ │ │ @@ -1,19 +1,19 @@ │ │ │ │ probe::nfs.fop.lock
probe::nfs.fop.lock
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.fop.lock — │ │ │ │ NFS client file lock operation │ │ │ │ -

Synopsis

nfs.fop.lock

Values

fl_flag

│ │ │ │ - lock flags │ │ │ │ -

fl_end

│ │ │ │ - ending offset of locked region │ │ │ │ -

ino

│ │ │ │ - inode number │ │ │ │ -

cmd

│ │ │ │ - cmd arguments │ │ │ │ +

Synopsis

nfs.fop.lock

Values

dev

│ │ │ │ + device identifier │ │ │ │

fl_start

│ │ │ │ starting offset of locked region │ │ │ │ -

dev

│ │ │ │ - device identifier │ │ │ │ +

fl_end

│ │ │ │ + ending offset of locked region │ │ │ │

fl_type

│ │ │ │ lock type │ │ │ │ +

ino

│ │ │ │ + inode number │ │ │ │

i_mode

│ │ │ │ file type and access rights │ │ │ │ +

cmd

│ │ │ │ + cmd arguments │ │ │ │ +

fl_flag

│ │ │ │ + lock flags │ │ │ │

Prev Up Next
probe::nfs.fop.llseek Home probe::nfs.fop.mmap
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-mmap.html │ │ │ │ @@ -1,27 +1,27 @@ │ │ │ │ probe::nfs.fop.mmap
probe::nfs.fop.mmap
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.fop.mmap — │ │ │ │ NFS client mmap operation │ │ │ │ -

Synopsis

nfs.fop.mmap

Values

cache_time

│ │ │ │ - when we started read-caching this inode │ │ │ │ -

vm_start

│ │ │ │ - start address within vm_mm │ │ │ │ -

attrtimeo

│ │ │ │ - how long the cached information is assumed to be valid. │ │ │ │ - We need to revalidate the cached attrs for this inode │ │ │ │ - if jiffies - read_cache_jiffies > attrtimeo. │ │ │ │ +

Synopsis

nfs.fop.mmap

Values

vm_flag

│ │ │ │ + vm flags │ │ │ │ +

ino

│ │ │ │ + inode number │ │ │ │

dev

│ │ │ │ device identifier │ │ │ │ +

cache_valid

│ │ │ │ + cache related bit mask flag │ │ │ │

file_name

│ │ │ │ file name │ │ │ │ -

ino

│ │ │ │ - inode number │ │ │ │

buf

│ │ │ │ the address of buf in user space │ │ │ │ -

vm_flag

│ │ │ │ - vm flags │ │ │ │ -

vm_end

│ │ │ │ - the first byte after end address within vm_mm │ │ │ │ -

cache_valid

│ │ │ │ - cache related bit mask flag │ │ │ │

parent_name

│ │ │ │ parent dir name │ │ │ │ +

attrtimeo

│ │ │ │ + how long the cached information is assumed to be valid. │ │ │ │ + We need to revalidate the cached attrs for this inode │ │ │ │ + if jiffies - read_cache_jiffies > attrtimeo. │ │ │ │ +

cache_time

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

vm_end

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

vm_start

│ │ │ │ + start address within vm_mm │ │ │ │

Prev Up Next
probe::nfs.fop.lock Home probe::nfs.fop.open
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-open.html │ │ │ │ @@ -1,13 +1,13 @@ │ │ │ │ probe::nfs.fop.open
probe::nfs.fop.open
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.fop.open — │ │ │ │ NFS client file open operation │ │ │ │ -

Synopsis

nfs.fop.open

Values

file_name

│ │ │ │ - file name │ │ │ │ +

Synopsis

nfs.fop.open

Values

flag

│ │ │ │ + file flag │ │ │ │

ino

│ │ │ │ inode number │ │ │ │ -

flag

│ │ │ │ - file flag │ │ │ │

i_size

│ │ │ │ file length in bytes │ │ │ │

dev

│ │ │ │ device identifier │ │ │ │ +

file_name

│ │ │ │ + file name │ │ │ │

Prev Up Next
probe::nfs.fop.mmap Home probe::nfs.fop.read
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-read-iter.html │ │ │ │ @@ -1,23 +1,23 @@ │ │ │ │ probe::nfs.fop.read_iter
probe::nfs.fop.read_iter
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.fop.read_iter — │ │ │ │ NFS client read_iter file operation │ │ │ │ -

Synopsis

nfs.fop.read_iter

Values

file_name

│ │ │ │ - file name │ │ │ │ -

ino

│ │ │ │ +

Synopsis

nfs.fop.read_iter

Values

ino

│ │ │ │ inode number │ │ │ │ -

cache_valid

│ │ │ │ - cache related bit mask flag │ │ │ │ +

file_name

│ │ │ │ + file name │ │ │ │ +

attrtimeo

│ │ │ │ + how long the cached information is assumed to be valid. │ │ │ │ + We need to revalidate the cached attrs for this inode │ │ │ │ + if jiffies - read_cache_jiffies > attrtimeo. │ │ │ │

count

│ │ │ │ read bytes │ │ │ │ +

dev

│ │ │ │ + device identifier │ │ │ │

parent_name

│ │ │ │ parent dir name │ │ │ │ +

cache_valid

│ │ │ │ + cache related bit mask flag │ │ │ │

cache_time

│ │ │ │ when we started read-caching this inode │ │ │ │

pos

│ │ │ │ current position of file │ │ │ │ -

attrtimeo

│ │ │ │ - how long the cached information is assumed to be valid. │ │ │ │ - We need to revalidate the cached attrs for this inode │ │ │ │ - if jiffies - read_cache_jiffies > attrtimeo. │ │ │ │ -

dev

│ │ │ │ - device identifier │ │ │ │

Prev Up Next
probe::nfs.fop.read Home probe::nfs.fop.release
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-release.html │ │ │ │ @@ -1,9 +1,9 @@ │ │ │ │ probe::nfs.fop.release
probe::nfs.fop.release
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.fop.release — │ │ │ │ NFS client release page operation │ │ │ │ -

Synopsis

nfs.fop.release

Values

dev

│ │ │ │ - device identifier │ │ │ │ -

ino

│ │ │ │ +

Synopsis

nfs.fop.release

Values

ino

│ │ │ │ inode number │ │ │ │ +

dev

│ │ │ │ + device identifier │ │ │ │

mode

│ │ │ │ file mode │ │ │ │

Prev Up Next
probe::nfs.fop.read_iter Home probe::nfs.fop.sendfile
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-sendfile.html │ │ │ │ @@ -1,19 +1,19 @@ │ │ │ │ probe::nfs.fop.sendfile
probe::nfs.fop.sendfile
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.fop.sendfile — │ │ │ │ NFS client send file operation │ │ │ │ -

Synopsis

nfs.fop.sendfile

Values

dev

│ │ │ │ +

Synopsis

nfs.fop.sendfile

Values

cache_valid

│ │ │ │ + cache related bit mask flag │ │ │ │ +

dev

│ │ │ │ device identifier │ │ │ │ +

ino

│ │ │ │ + inode number │ │ │ │ +

cache_time

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

attrtimeo

│ │ │ │ how long the cached information is assumed to be valid. │ │ │ │ We need to revalidate the cached attrs for this inode │ │ │ │ if jiffies - read_cache_jiffies > attrtimeo. │ │ │ │ -

cache_time

│ │ │ │ - when we started read-caching this inode │ │ │ │ -

ppos

│ │ │ │ - current position of file │ │ │ │

count

│ │ │ │ read bytes │ │ │ │ -

cache_valid

│ │ │ │ - cache related bit mask flag │ │ │ │ -

ino

│ │ │ │ - inode number │ │ │ │ +

ppos

│ │ │ │ + current position of file │ │ │ │

Prev Up Next
probe::nfs.fop.release Home probe::nfs.fop.write
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-fop-write-iter.html │ │ │ │ @@ -1,15 +1,15 @@ │ │ │ │ probe::nfs.fop.write_iter
probe::nfs.fop.write_iter
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.fop.write_iter — │ │ │ │ NFS client write_iter file operation │ │ │ │ -

Synopsis

nfs.fop.write_iter

Values

parent_name

│ │ │ │ - parent dir name │ │ │ │ -

count

│ │ │ │ - read bytes │ │ │ │ -

ino

│ │ │ │ +

Synopsis

nfs.fop.write_iter

Values

ino

│ │ │ │ inode number │ │ │ │

file_name

│ │ │ │ file name │ │ │ │ -

dev

│ │ │ │ - device identifier │ │ │ │

pos

│ │ │ │ offset of the file │ │ │ │ +

parent_name

│ │ │ │ + parent dir name │ │ │ │ +

dev

│ │ │ │ + device identifier │ │ │ │ +

count

│ │ │ │ + read bytes │ │ │ │

Prev Up Next
probe::nfs.fop.write Home probe::nfs.proc.commit
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-commit-done.html │ │ │ │ @@ -1,20 +1,20 @@ │ │ │ │ probe::nfs.proc.commit_done
probe::nfs.proc.commit_done
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.proc.commit_done — │ │ │ │ NFS client response to a commit RPC task │ │ │ │ -

Synopsis

nfs.proc.commit_done

Values

prot

│ │ │ │ +

Synopsis

nfs.proc.commit_done

Values

version

│ │ │ │ + NFS version │ │ │ │ +

timestamp

│ │ │ │ + V4 timestamp, which is used for lease renewal │ │ │ │ +

prot

│ │ │ │ transfer protocol │ │ │ │ +

valid

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

count

│ │ │ │ + number of bytes committed │ │ │ │

server_ip

│ │ │ │ IP address of server │ │ │ │ -

timestamp

│ │ │ │ - V4 timestamp, which is used for lease renewal │ │ │ │ -

version

│ │ │ │ - NFS version │ │ │ │

status

│ │ │ │ result of last operation │ │ │ │ -

count

│ │ │ │ - number of bytes committed │ │ │ │ -

valid

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

Description

│ │ │ │ Fires when a reply to a commit RPC task is received │ │ │ │ or some commit operation error occur (timeout or socket shutdown). │ │ │ │

Prev Up Next
probe::nfs.proc.commit Home probe::nfs.proc.commit_setup
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-commit-setup.html │ │ │ │ @@ -1,25 +1,25 @@ │ │ │ │ probe::nfs.proc.commit_setup
probe::nfs.proc.commit_setup
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.proc.commit_setup — │ │ │ │ NFS client setting up a commit RPC task │ │ │ │ -

Synopsis

nfs.proc.commit_setup

Values

offset

│ │ │ │ - the file offset │ │ │ │ -

version

│ │ │ │ - NFS version │ │ │ │ +

Synopsis

nfs.proc.commit_setup

Values

server_ip

│ │ │ │ + IP address of server │ │ │ │

size

│ │ │ │ bytes in this commit │ │ │ │ +

prot

│ │ │ │ + transfer protocol │ │ │ │

count

│ │ │ │ bytes in this commit │ │ │ │ -

bitmask1

│ │ │ │ +

bitmask0

│ │ │ │ V4 bitmask representing the set of attributes supported │ │ │ │ on this filesystem │ │ │ │ -

prot

│ │ │ │ - transfer protocol │ │ │ │ -

server_ip

│ │ │ │ - IP address of server │ │ │ │ -

bitmask0

│ │ │ │ +

offset

│ │ │ │ + the file offset │ │ │ │ +

version

│ │ │ │ + NFS version │ │ │ │ +

bitmask1

│ │ │ │ V4 bitmask representing the set of attributes supported │ │ │ │ on this filesystem │ │ │ │

Description

│ │ │ │ The commit_setup function is used to setup a commit RPC task. │ │ │ │ Is is not doing the actual commit operation. │ │ │ │ It does not exist in NFSv2. │ │ │ │

Prev Up Next
probe::nfs.proc.commit_done Home probe::nfs.proc.create
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-commit.html │ │ │ │ @@ -1,25 +1,25 @@ │ │ │ │ probe::nfs.proc.commit
probe::nfs.proc.commit
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.proc.commit — │ │ │ │ NFS client committing data on server │ │ │ │ -

Synopsis

nfs.proc.commit

Values

size

│ │ │ │ - read bytes in this execution │ │ │ │ +

Synopsis

nfs.proc.commit

Values

bitmask1

│ │ │ │ + V4 bitmask representing the set of attributes supported │ │ │ │ + on this filesystem │ │ │ │

version

│ │ │ │ NFS version │ │ │ │

offset

│ │ │ │ the file offset │ │ │ │

bitmask0

│ │ │ │ V4 bitmask representing the set of attributes supported │ │ │ │ on this filesystem │ │ │ │ -

server_ip

│ │ │ │ - IP address of server │ │ │ │ -

bitmask1

│ │ │ │ - V4 bitmask representing the set of attributes supported │ │ │ │ - on this filesystem │ │ │ │

prot

│ │ │ │ transfer protocol │ │ │ │ +

size

│ │ │ │ + read bytes in this execution │ │ │ │ +

server_ip

│ │ │ │ + IP address of server │ │ │ │

Description

│ │ │ │ All the nfs.proc.commit kernel functions were removed in kernel │ │ │ │ commit 200baa in December 2006, so these probes do not exist on Linux │ │ │ │ 2.6.21 and newer kernels. │ │ │ │

│ │ │ │ │ │ │ │ Fires when client writes the buffered data to disk. │ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-create.html │ │ │ │ @@ -1,17 +1,17 @@ │ │ │ │ probe::nfs.proc.create

probe::nfs.proc.create
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.proc.create — │ │ │ │ NFS client creating file on server │ │ │ │ -

Synopsis

nfs.proc.create

Values

server_ip

│ │ │ │ - IP address of server │ │ │ │ -

fh

│ │ │ │ - file handle of parent dir │ │ │ │ -

prot

│ │ │ │ - transfer protocol │ │ │ │ -

filelen

│ │ │ │ - length of file name │ │ │ │ -

filename

│ │ │ │ +

Synopsis

nfs.proc.create

Values

filename

│ │ │ │ file name │ │ │ │

flag

│ │ │ │ indicates create mode (only for NFSv3 and NFSv4) │ │ │ │ +

prot

│ │ │ │ + transfer protocol │ │ │ │ +

server_ip

│ │ │ │ + IP address of server │ │ │ │ +

fh

│ │ │ │ + file handle of parent dir │ │ │ │

version

│ │ │ │ NFS version (the function is used for all NFS version) │ │ │ │ +

filelen

│ │ │ │ + length of file name │ │ │ │

Prev Up Next
probe::nfs.proc.commit_setup Home probe::nfs.proc.handle_exception
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-lookup.html │ │ │ │ @@ -1,19 +1,19 @@ │ │ │ │ probe::nfs.proc.lookup
probe::nfs.proc.lookup
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.proc.lookup — │ │ │ │ NFS client opens/searches a file on server │ │ │ │ -

Synopsis

nfs.proc.lookup

Values

prot

│ │ │ │ - transfer protocol │ │ │ │ -

bitmask1

│ │ │ │ - V4 bitmask representing the set of attributes supported │ │ │ │ - on this filesystem │ │ │ │ -

bitmask0

│ │ │ │ +

Synopsis

nfs.proc.lookup

Values

bitmask0

│ │ │ │ V4 bitmask representing the set of attributes supported │ │ │ │ on this filesystem │ │ │ │ +

filename

│ │ │ │ + the name of file which client opens/searches on server │ │ │ │

server_ip

│ │ │ │ IP address of server │ │ │ │ +

prot

│ │ │ │ + transfer protocol │ │ │ │ +

bitmask1

│ │ │ │ + V4 bitmask representing the set of attributes supported │ │ │ │ + on this filesystem │ │ │ │

version

│ │ │ │ NFS version │ │ │ │ -

filename

│ │ │ │ - the name of file which client opens/searches on server │ │ │ │

name_len

│ │ │ │ the length of file name │ │ │ │

Prev Up Next
probe::nfs.proc.handle_exception Home probe::nfs.proc.open
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-open.html │ │ │ │┄ Ordering differences only │ │ │ │ @@ -1,17 +1,17 @@ │ │ │ │ probe::nfs.proc.open
probe::nfs.proc.open
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.proc.open — │ │ │ │ NFS client allocates file read/write context information │ │ │ │

Synopsis

nfs.proc.open

Values

filename

│ │ │ │ file name │ │ │ │ +

server_ip

│ │ │ │ + IP address of server │ │ │ │ +

prot

│ │ │ │ + transfer protocol │ │ │ │

flag

│ │ │ │ file flag │ │ │ │ -

version

│ │ │ │ - NFS version (the function is used for all NFS version) │ │ │ │

mode

│ │ │ │ file mode │ │ │ │ -

prot

│ │ │ │ - transfer protocol │ │ │ │ -

server_ip

│ │ │ │ - IP address of server │ │ │ │ +

version

│ │ │ │ + NFS version (the function is used for all NFS version) │ │ │ │

Description

│ │ │ │ Allocate file read/write context information │ │ │ │

Prev Up Next
probe::nfs.proc.lookup Home probe::nfs.proc.read
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-read-done.html │ │ │ │ @@ -1,18 +1,18 @@ │ │ │ │ probe::nfs.proc.read_done
probe::nfs.proc.read_done
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.proc.read_done — │ │ │ │ NFS client response to a read RPC task │ │ │ │ -

Synopsis

nfs.proc.read_done

Values

prot

│ │ │ │ - transfer protocol │ │ │ │ -

server_ip

│ │ │ │ - IP address of server │ │ │ │ -

version

│ │ │ │ +

Synopsis

nfs.proc.read_done

Values

version

│ │ │ │ NFS version │ │ │ │

timestamp

│ │ │ │ V4 timestamp, which is used for lease renewal │ │ │ │ -

count

│ │ │ │ - number of bytes read │ │ │ │ +

server_ip

│ │ │ │ + IP address of server │ │ │ │

status

│ │ │ │ result of last operation │ │ │ │ +

prot

│ │ │ │ + transfer protocol │ │ │ │ +

count

│ │ │ │ + number of bytes read │ │ │ │

Description

│ │ │ │ Fires when a reply to a read RPC task is received or some read error occurs │ │ │ │ (timeout or socket shutdown). │ │ │ │

Prev Up Next
probe::nfs.proc.read Home probe::nfs.proc.read_setup
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-read-setup.html │ │ │ │ @@ -1,18 +1,18 @@ │ │ │ │ probe::nfs.proc.read_setup
probe::nfs.proc.read_setup
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.proc.read_setup — │ │ │ │ NFS client setting up a read RPC task │ │ │ │ -

Synopsis

nfs.proc.read_setup

Values

count

│ │ │ │ - read bytes in this execution │ │ │ │ -

version

│ │ │ │ +

Synopsis

nfs.proc.read_setup

Values

version

│ │ │ │ NFS version │ │ │ │ -

size

│ │ │ │ - read bytes in this execution │ │ │ │

offset

│ │ │ │ the file offset │ │ │ │ -

server_ip

│ │ │ │ - IP address of server │ │ │ │

prot

│ │ │ │ transfer protocol │ │ │ │ +

count

│ │ │ │ + read bytes in this execution │ │ │ │ +

server_ip

│ │ │ │ + IP address of server │ │ │ │ +

size

│ │ │ │ + read bytes in this execution │ │ │ │

Description

│ │ │ │ The read_setup function is used to setup a read RPC task. │ │ │ │ It is not doing the actual read operation. │ │ │ │

Prev Up Next
probe::nfs.proc.read_done Home probe::nfs.proc.release
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-read.html │ │ │ │ @@ -1,19 +1,19 @@ │ │ │ │ probe::nfs.proc.read
probe::nfs.proc.read
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.proc.read — │ │ │ │ NFS client synchronously reads file from server │ │ │ │ -

Synopsis

nfs.proc.read

Values

server_ip

│ │ │ │ +

Synopsis

nfs.proc.read

Values

version

│ │ │ │ + NFS version │ │ │ │ +

flags

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

server_ip

│ │ │ │ IP address of server │ │ │ │

prot

│ │ │ │ transfer protocol │ │ │ │

count

│ │ │ │ read bytes in this execution │ │ │ │ -

flags

│ │ │ │ - used to set task->tk_flags in rpc_init_task function │ │ │ │ -

version

│ │ │ │ - NFS version │ │ │ │

offset

│ │ │ │ the file offset │ │ │ │

Description

│ │ │ │ All the nfs.proc.read kernel functions were removed in kernel commit │ │ │ │ 8e0969 in December 2006, so these probes do not exist on Linux │ │ │ │ 2.6.21 and newer kernels. │ │ │ │

Prev Up Next
probe::nfs.proc.open Home probe::nfs.proc.read_done
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-release.html │ │ │ │ @@ -1,17 +1,17 @@ │ │ │ │ probe::nfs.proc.release
probe::nfs.proc.release
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.proc.release — │ │ │ │ NFS client releases file read/write context information │ │ │ │ -

Synopsis

nfs.proc.release

Values

filename

│ │ │ │ - file name │ │ │ │ +

Synopsis

nfs.proc.release

Values

mode

│ │ │ │ + file mode │ │ │ │

version

│ │ │ │ NFS version (the function is used for all NFS version) │ │ │ │ -

flag

│ │ │ │ - file flag │ │ │ │ +

filename

│ │ │ │ + file name │ │ │ │

server_ip

│ │ │ │ IP address of server │ │ │ │ -

mode

│ │ │ │ - file mode │ │ │ │

prot

│ │ │ │ transfer protocol │ │ │ │ +

flag

│ │ │ │ + file flag │ │ │ │

Description

│ │ │ │ Release file read/write context information │ │ │ │

Prev Up Next
probe::nfs.proc.read_setup Home probe::nfs.proc.remove
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-remove.html │ │ │ │ @@ -1,15 +1,15 @@ │ │ │ │ probe::nfs.proc.remove
probe::nfs.proc.remove
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.proc.remove — │ │ │ │ NFS client removes a file on server │ │ │ │ -

Synopsis

nfs.proc.remove

Values

filelen

│ │ │ │ - length of file name │ │ │ │ +

Synopsis

nfs.proc.remove

Values

fh

│ │ │ │ + file handle of parent dir │ │ │ │

version

│ │ │ │ NFS version (the function is used for all NFS version) │ │ │ │ +

filelen

│ │ │ │ + length of file name │ │ │ │

filename

│ │ │ │ file name │ │ │ │ -

server_ip

│ │ │ │ - IP address of server │ │ │ │

prot

│ │ │ │ transfer protocol │ │ │ │ -

fh

│ │ │ │ - file handle of parent dir │ │ │ │ +

server_ip

│ │ │ │ + IP address of server │ │ │ │

Prev Up Next
probe::nfs.proc.release Home probe::nfs.proc.rename
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-rename-done.html │ │ │ │ @@ -1,20 +1,20 @@ │ │ │ │ probe::nfs.proc.rename_done
probe::nfs.proc.rename_done
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.proc.rename_done — │ │ │ │ NFS client response to a rename RPC task │ │ │ │ -

Synopsis

nfs.proc.rename_done

Values

new_fh

│ │ │ │ - file handle of new parent dir │ │ │ │ +

Synopsis

nfs.proc.rename_done

Values

old_fh

│ │ │ │ + file handle of old parent dir │ │ │ │

version

│ │ │ │ NFS version │ │ │ │ +

new_fh

│ │ │ │ + file handle of new parent dir │ │ │ │

timestamp

│ │ │ │ V4 timestamp, which is used for lease renewal │ │ │ │

status

│ │ │ │ result of last operation │ │ │ │ -

prot

│ │ │ │ - transfer protocol │ │ │ │ -

old_fh

│ │ │ │ - file handle of old parent dir │ │ │ │

server_ip

│ │ │ │ IP address of server │ │ │ │ +

prot

│ │ │ │ + transfer protocol │ │ │ │

Description

│ │ │ │ Fires when a reply to a rename RPC task is received or some rename │ │ │ │ error occurs (timeout or socket shutdown). │ │ │ │

Prev Up Next
probe::nfs.proc.rename Home probe::nfs.proc.rename_setup
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-rename-setup.html │ │ │ │┄ Ordering differences only │ │ │ │ @@ -1,14 +1,14 @@ │ │ │ │ probe::nfs.proc.rename_setup
probe::nfs.proc.rename_setup
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.proc.rename_setup — │ │ │ │ NFS client setting up a rename RPC task │ │ │ │

Synopsis

nfs.proc.rename_setup

Values

version

│ │ │ │ NFS version │ │ │ │ -

server_ip

│ │ │ │ - IP address of server │ │ │ │

fh

│ │ │ │ file handle of parent dir │ │ │ │

prot

│ │ │ │ transfer protocol │ │ │ │ +

server_ip

│ │ │ │ + IP address of server │ │ │ │

Description

│ │ │ │ The rename_setup function is used to setup a rename RPC task. │ │ │ │ Is is not doing the actual rename operation. │ │ │ │

Prev Up Next
probe::nfs.proc.rename_done Home probe::nfs.proc.write
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-rename.html │ │ │ │ @@ -1,21 +1,21 @@ │ │ │ │ probe::nfs.proc.rename
probe::nfs.proc.rename
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.proc.rename — │ │ │ │ NFS client renames a file on server │ │ │ │ -

Synopsis

nfs.proc.rename

Values

old_fh

│ │ │ │ +

Synopsis

nfs.proc.rename

Values

new_filelen

│ │ │ │ + length of new file name │ │ │ │ +

old_fh

│ │ │ │ file handle of old parent dir │ │ │ │ -

server_ip

│ │ │ │ - IP address of server │ │ │ │

old_name

│ │ │ │ old file name │ │ │ │ -

prot

│ │ │ │ - transfer protocol │ │ │ │ -

old_filelen

│ │ │ │ - length of old file name │ │ │ │ -

new_filelen

│ │ │ │ - length of new file name │ │ │ │ -

new_fh

│ │ │ │ - file handle of new parent dir │ │ │ │

version

│ │ │ │ NFS version (the function is used for all NFS version) │ │ │ │ +

old_filelen

│ │ │ │ + length of old file name │ │ │ │

new_name

│ │ │ │ new file name │ │ │ │ +

new_fh

│ │ │ │ + file handle of new parent dir │ │ │ │ +

server_ip

│ │ │ │ + IP address of server │ │ │ │ +

prot

│ │ │ │ + transfer protocol │ │ │ │

Prev Up Next
probe::nfs.proc.remove Home probe::nfs.proc.rename_done
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-write-done.html │ │ │ │┄ Ordering differences only │ │ │ │ @@ -1,19 +1,19 @@ │ │ │ │ probe::nfs.proc.write_done
probe::nfs.proc.write_done
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.proc.write_done — │ │ │ │ NFS client response to a write RPC task │ │ │ │

Synopsis

nfs.proc.write_done

Values

server_ip

│ │ │ │ IP address of server │ │ │ │ -

prot

│ │ │ │ - transfer protocol │ │ │ │

status

│ │ │ │ result of last operation │ │ │ │ -

valid

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

prot

│ │ │ │ + transfer protocol │ │ │ │

count

│ │ │ │ number of bytes written │ │ │ │ +

valid

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

timestamp

│ │ │ │ V4 timestamp, which is used for lease renewal │ │ │ │

version

│ │ │ │ NFS version │ │ │ │

Description

│ │ │ │ Fires when a reply to a write RPC task is received or some write error occurs │ │ │ │ (timeout or socket shutdown). │ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-write-setup.html │ │ │ │ @@ -1,28 +1,28 @@ │ │ │ │ probe::nfs.proc.write_setup

probe::nfs.proc.write_setup
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.proc.write_setup — │ │ │ │ NFS client setting up a write RPC task │ │ │ │ -

Synopsis

nfs.proc.write_setup

Values

count

│ │ │ │ - bytes written in this execution │ │ │ │ -

size

│ │ │ │ - bytes written in this execution │ │ │ │ +

Synopsis

nfs.proc.write_setup

Values

bitmask1

│ │ │ │ + V4 bitmask representing the set of attributes supported │ │ │ │ + on this filesystem │ │ │ │

version

│ │ │ │ NFS version │ │ │ │

offset

│ │ │ │ the file offset │ │ │ │

bitmask0

│ │ │ │ V4 bitmask representing the set of attributes supported │ │ │ │ on this filesystem │ │ │ │ -

server_ip

│ │ │ │ - IP address of server │ │ │ │

how

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

prot

│ │ │ │ transfer protocol │ │ │ │ -

bitmask1

│ │ │ │ - V4 bitmask representing the set of attributes supported │ │ │ │ - on this filesystem │ │ │ │ +

count

│ │ │ │ + bytes written in this execution │ │ │ │ +

server_ip

│ │ │ │ + IP address of server │ │ │ │ +

size

│ │ │ │ + bytes written in this execution │ │ │ │

Description

│ │ │ │ The write_setup function is used to setup a write RPC task. │ │ │ │ It is not doing the actual write operation. │ │ │ │

Prev Up Next
probe::nfs.proc.write_done Home probe::nfsd.close
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfs-proc-write.html │ │ │ │ @@ -1,25 +1,25 @@ │ │ │ │ probe::nfs.proc.write
probe::nfs.proc.write
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfs.proc.write — │ │ │ │ NFS client synchronously writes file to server │ │ │ │ -

Synopsis

nfs.proc.write

Values

server_ip

│ │ │ │ - IP address of server │ │ │ │ +

Synopsis

nfs.proc.write

Values

offset

│ │ │ │ + the file offset │ │ │ │

bitmask0

│ │ │ │ V4 bitmask representing the set of attributes supported │ │ │ │ on this filesystem │ │ │ │

prot

│ │ │ │ transfer protocol │ │ │ │ +

server_ip

│ │ │ │ + IP address of server │ │ │ │ +

size

│ │ │ │ + read bytes in this execution │ │ │ │

bitmask1

│ │ │ │ V4 bitmask representing the set of attributes supported │ │ │ │ on this filesystem │ │ │ │ -

size

│ │ │ │ - read bytes in this execution │ │ │ │ -

version

│ │ │ │ - NFS version │ │ │ │

flags

│ │ │ │ used to set task->tk_flags in rpc_init_task function │ │ │ │ -

offset

│ │ │ │ - the file offset │ │ │ │ +

version

│ │ │ │ + NFS version │ │ │ │

Description

│ │ │ │ All the nfs.proc.write kernel functions were removed in kernel commit │ │ │ │ 200baa in December 2006, so these probes do not exist on Linux │ │ │ │ 2.6.21 and newer kernels. │ │ │ │

Prev Up Next
probe::nfs.proc.rename_setup Home probe::nfs.proc.write_done
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfsd-commit.html │ │ │ │ @@ -1,15 +1,15 @@ │ │ │ │ probe::nfsd.commit
probe::nfsd.commit
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfsd.commit — │ │ │ │ NFS server committing all pending writes to stable storage │ │ │ │ -

Synopsis

nfsd.commit

Values

client_ip

│ │ │ │ - the ip address of client │ │ │ │ -

fh

│ │ │ │ +

Synopsis

nfsd.commit

Values

fh

│ │ │ │ file handle (the first part is the length of the file handle) │ │ │ │ -

flag

│ │ │ │ - indicates whether this execution is a sync operation │ │ │ │ -

size

│ │ │ │ +

count

│ │ │ │ read bytes │ │ │ │ +

client_ip

│ │ │ │ + the ip address of client │ │ │ │

offset

│ │ │ │ the offset of file │ │ │ │ -

count

│ │ │ │ +

flag

│ │ │ │ + indicates whether this execution is a sync operation │ │ │ │ +

size

│ │ │ │ read bytes │ │ │ │

Prev Up Next
probe::nfsd.close Home probe::nfsd.create
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfsd-create.html │ │ │ │┄ Ordering differences only │ │ │ │ @@ -1,19 +1,19 @@ │ │ │ │ probe::nfsd.create
probe::nfsd.create
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfsd.create — │ │ │ │ NFS server creating a file(regular,dir,device,fifo) for client │ │ │ │

Synopsis

nfsd.create

Values

fh

│ │ │ │ file handle (the first part is the length of the file handle) │ │ │ │ -

iap_valid

│ │ │ │ - Attribute flags │ │ │ │ +

client_ip

│ │ │ │ + the ip address of client │ │ │ │ +

type

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

filelen

│ │ │ │ the length of file name │ │ │ │

filename

│ │ │ │ file name │ │ │ │

iap_mode

│ │ │ │ file access mode │ │ │ │ -

client_ip

│ │ │ │ - the ip address of client │ │ │ │ -

type

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

iap_valid

│ │ │ │ + Attribute flags │ │ │ │

Description

│ │ │ │ Sometimes nfsd will call nfsd_create_v3 instead of this this probe point. │ │ │ │

Prev Up Next
probe::nfsd.commit Home probe::nfsd.createv3
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfsd-createv3.html │ │ │ │ @@ -1,24 +1,24 @@ │ │ │ │ probe::nfsd.createv3
probe::nfsd.createv3
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfsd.createv3 — │ │ │ │ NFS server creating a regular file or set file attributes for client │ │ │ │ -

Synopsis

nfsd.createv3

Values

filename

│ │ │ │ - file name │ │ │ │ -

iap_mode

│ │ │ │ - file access mode │ │ │ │ -

client_ip

│ │ │ │ - the ip address of client │ │ │ │ +

Synopsis

nfsd.createv3

Values

truncp

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

fh

│ │ │ │ file handle (the first part is the length of the file handle) │ │ │ │ -

truncp

│ │ │ │ - trunp arguments, indicates if the file shouldbe truncate │ │ │ │

createmode

│ │ │ │ create mode .The possible values could be: NFS3_CREATE_EXCLUSIVE, NFS3_CREATE_UNCHECKED, or NFS3_CREATE_GUARDED │ │ │ │ -

iap_valid

│ │ │ │ - Attribute flags │ │ │ │ +

client_ip

│ │ │ │ + the ip address of client │ │ │ │

verifier

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

filename

│ │ │ │ + file name │ │ │ │ +

iap_mode

│ │ │ │ + file access mode │ │ │ │ +

iap_valid

│ │ │ │ + Attribute flags │ │ │ │

filelen

│ │ │ │ the length of file name │ │ │ │

Description

│ │ │ │ This probepoints is only called by nfsd3_proc_create and │ │ │ │ nfsd4_open when op_claim_type is NFS4_OPEN_CLAIM_NULL. │ │ │ │

Prev Up Next
probe::nfsd.create Home probe::nfsd.dispatch
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfsd-dispatch.html │ │ │ │ @@ -1,15 +1,15 @@ │ │ │ │ probe::nfsd.dispatch
probe::nfsd.dispatch
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfsd.dispatch — │ │ │ │ NFS server receives an operation from client │ │ │ │ -

Synopsis

nfsd.dispatch

Values

client_ip

│ │ │ │ - the ip address of client │ │ │ │ -

proto

│ │ │ │ - transfer protocol │ │ │ │ -

prog

│ │ │ │ - program number │ │ │ │ +

Synopsis

nfsd.dispatch

Values

proc

│ │ │ │ + procedure number │ │ │ │

xid

│ │ │ │ transmission id │ │ │ │ -

proc

│ │ │ │ - procedure number │ │ │ │

version

│ │ │ │ nfs version │ │ │ │ +

prog

│ │ │ │ + program number │ │ │ │ +

proto

│ │ │ │ + transfer protocol │ │ │ │ +

client_ip

│ │ │ │ + the ip address of client │ │ │ │

Prev Up Next
probe::nfsd.createv3 Home probe::nfsd.lookup
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfsd-lookup.html │ │ │ │ @@ -1,11 +1,11 @@ │ │ │ │ probe::nfsd.lookup
probe::nfsd.lookup
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfsd.lookup — │ │ │ │ NFS server opening or searching file for a file for client │ │ │ │ -

Synopsis

nfsd.lookup

Values

fh

│ │ │ │ - file handle of parent dir(the first part is the length of the file handle) │ │ │ │ -

filelen

│ │ │ │ +

Synopsis

nfsd.lookup

Values

filelen

│ │ │ │ the length of file name │ │ │ │

filename

│ │ │ │ file name │ │ │ │ +

fh

│ │ │ │ + file handle of parent dir(the first part is the length of the file handle) │ │ │ │

client_ip

│ │ │ │ the ip address of client │ │ │ │

Prev Up Next
probe::nfsd.dispatch Home probe::nfsd.open
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfsd-open.html │ │ │ │ @@ -1,11 +1,11 @@ │ │ │ │ probe::nfsd.open
probe::nfsd.open
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfsd.open — │ │ │ │ NFS server opening a file for client │ │ │ │ -

Synopsis

nfsd.open

Values

fh

│ │ │ │ - file handle (the first part is the length of the file handle) │ │ │ │ +

Synopsis

nfsd.open

Values

type

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

access

│ │ │ │ indicates the type of open (read/write/commit/readdir...) │ │ │ │ -

type

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

fh

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

client_ip

│ │ │ │ the ip address of client │ │ │ │

Prev Up Next
probe::nfsd.lookup Home probe::nfsd.proc.commit
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfsd-proc-commit.html │ │ │ │ @@ -1,21 +1,21 @@ │ │ │ │ probe::nfsd.proc.commit
probe::nfsd.proc.commit
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfsd.proc.commit — │ │ │ │ NFS server performing a commit operation for client │ │ │ │ -

Synopsis

nfsd.proc.commit

Values

gid

│ │ │ │ - requester's group id │ │ │ │ -

uid

│ │ │ │ - requester's user id │ │ │ │ -

version

│ │ │ │ +

Synopsis

nfsd.proc.commit

Values

version

│ │ │ │ nfs version │ │ │ │ -

client_ip

│ │ │ │ - the ip address of client │ │ │ │ -

fh

│ │ │ │ - file handle (the first part is the length of the file handle) │ │ │ │

proto

│ │ │ │ transfer protocol │ │ │ │ -

offset

│ │ │ │ - the offset of file │ │ │ │ -

count

│ │ │ │ - read bytes │ │ │ │

size

│ │ │ │ read bytes │ │ │ │ +

fh

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

gid

│ │ │ │ + requester's group id │ │ │ │ +

count

│ │ │ │ + read bytes │ │ │ │ +

client_ip

│ │ │ │ + the ip address of client │ │ │ │ +

uid

│ │ │ │ + requester's user id │ │ │ │ +

offset

│ │ │ │ + the offset of file │ │ │ │

Prev Up Next
probe::nfsd.open Home probe::nfsd.proc.create
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfsd-proc-create.html │ │ │ │ @@ -1,19 +1,19 @@ │ │ │ │ probe::nfsd.proc.create
probe::nfsd.proc.create
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfsd.proc.create — │ │ │ │ NFS server creating a file for client │ │ │ │ -

Synopsis

nfsd.proc.create

Values

client_ip

│ │ │ │ - the ip address of client │ │ │ │ +

Synopsis

nfsd.proc.create

Values

gid

│ │ │ │ + requester's group id │ │ │ │ +

fh

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

uid

│ │ │ │ requester's user id │ │ │ │ +

client_ip

│ │ │ │ + the ip address of client │ │ │ │

version

│ │ │ │ nfs version │ │ │ │ -

filename

│ │ │ │ - file name │ │ │ │ -

gid

│ │ │ │ - requester's group id │ │ │ │

filelen

│ │ │ │ length of file name │ │ │ │ -

fh

│ │ │ │ - file handle (the first part is the length of the file handle) │ │ │ │

proto

│ │ │ │ transfer protocol │ │ │ │ +

filename

│ │ │ │ + file name │ │ │ │

Prev Up Next
probe::nfsd.proc.commit Home probe::nfsd.proc.lookup
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfsd-proc-lookup.html │ │ │ │ @@ -1,19 +1,19 @@ │ │ │ │ probe::nfsd.proc.lookup
probe::nfsd.proc.lookup
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfsd.proc.lookup — │ │ │ │ NFS server opening or searching for a file for client │ │ │ │ -

Synopsis

nfsd.proc.lookup

Values

filelen

│ │ │ │ - the length of file name │ │ │ │ -

version

│ │ │ │ +

Synopsis

nfsd.proc.lookup

Values

version

│ │ │ │ nfs version │ │ │ │ -

uid

│ │ │ │ - requester's user id │ │ │ │ -

client_ip

│ │ │ │ - the ip address of client │ │ │ │ +

fh

│ │ │ │ + file handle of parent dir (the first part is the length of the file handle) │ │ │ │

gid

│ │ │ │ requester's group id │ │ │ │ -

proto

│ │ │ │ - transfer protocol │ │ │ │ +

filelen

│ │ │ │ + the length of file name │ │ │ │ +

client_ip

│ │ │ │ + the ip address of client │ │ │ │

filename

│ │ │ │ file name │ │ │ │ -

fh

│ │ │ │ - file handle of parent dir (the first part is the length of the file handle) │ │ │ │ +

proto

│ │ │ │ + transfer protocol │ │ │ │ +

uid

│ │ │ │ + requester's user id │ │ │ │

Prev Up Next
probe::nfsd.proc.create Home probe::nfsd.proc.read
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfsd-proc-read.html │ │ │ │ @@ -1,25 +1,25 @@ │ │ │ │ probe::nfsd.proc.read
probe::nfsd.proc.read
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfsd.proc.read — │ │ │ │ NFS server reading file for client │ │ │ │ -

Synopsis

nfsd.proc.read

Values

client_ip

│ │ │ │ - the ip address of client │ │ │ │ +

Synopsis

nfsd.proc.read

Values

vlen

│ │ │ │ + read blocks │ │ │ │

version

│ │ │ │ nfs version │ │ │ │ -

uid

│ │ │ │ - requester's user id │ │ │ │ -

vlen

│ │ │ │ - read blocks │ │ │ │ +

fh

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

gid

│ │ │ │ requester's group id │ │ │ │ -

size

│ │ │ │ - read bytes │ │ │ │ -

count

│ │ │ │ - read bytes │ │ │ │ -

offset

│ │ │ │ - the offset of file │ │ │ │ +

client_ip

│ │ │ │ + the ip address of client │ │ │ │

proto

│ │ │ │ transfer protocol │ │ │ │ +

uid

│ │ │ │ + requester's user id │ │ │ │ +

offset

│ │ │ │ + the offset of file │ │ │ │ +

size

│ │ │ │ + read bytes │ │ │ │

vec

│ │ │ │ struct kvec, includes buf address in kernel address and length of each buffer │ │ │ │ -

fh

│ │ │ │ - file handle (the first part is the length of the file handle) │ │ │ │ +

count

│ │ │ │ + read bytes │ │ │ │

Prev Up Next
probe::nfsd.proc.lookup Home probe::nfsd.proc.remove
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfsd-proc-remove.html │ │ │ │ @@ -1,19 +1,19 @@ │ │ │ │ probe::nfsd.proc.remove
probe::nfsd.proc.remove
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfsd.proc.remove — │ │ │ │ NFS server removing a file for client │ │ │ │ -

Synopsis

nfsd.proc.remove

Values

client_ip

│ │ │ │ +

Synopsis

nfsd.proc.remove

Values

fh

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

gid

│ │ │ │ + requester's group id │ │ │ │ +

client_ip

│ │ │ │ the ip address of client │ │ │ │

uid

│ │ │ │ requester's user id │ │ │ │

version

│ │ │ │ nfs version │ │ │ │ -

filename

│ │ │ │ - file name │ │ │ │ -

gid

│ │ │ │ - requester's group id │ │ │ │

filelen

│ │ │ │ length of file name │ │ │ │ -

fh

│ │ │ │ - file handle (the first part is the length of the file handle) │ │ │ │

proto

│ │ │ │ transfer protocol │ │ │ │ +

filename

│ │ │ │ + file name │ │ │ │

Prev Up Next
probe::nfsd.proc.read Home probe::nfsd.proc.rename
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfsd-proc-rename.html │ │ │ │ @@ -1,21 +1,21 @@ │ │ │ │ probe::nfsd.proc.rename
probe::nfsd.proc.rename
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfsd.proc.rename — │ │ │ │ NFS Server renaming a file for client │ │ │ │ -

Synopsis

nfsd.proc.rename

Values

tlen

│ │ │ │ - length of new file name │ │ │ │ -

gid

│ │ │ │ - requester's group id │ │ │ │ -

filename

│ │ │ │ +

Synopsis

nfsd.proc.rename

Values

filename

│ │ │ │ old file name │ │ │ │ -

uid

│ │ │ │ - requester's user id │ │ │ │ +

tlen

│ │ │ │ + length of new file name │ │ │ │ +

tname

│ │ │ │ + new file name │ │ │ │ +

flen

│ │ │ │ + length of old file name │ │ │ │

client_ip

│ │ │ │ the ip address of client │ │ │ │ +

uid

│ │ │ │ + requester's user id │ │ │ │

fh

│ │ │ │ file handler of old path │ │ │ │ -

flen

│ │ │ │ - length of old file name │ │ │ │

tfh

│ │ │ │ file handler of new path │ │ │ │ -

tname

│ │ │ │ - new file name │ │ │ │ +

gid

│ │ │ │ + requester's group id │ │ │ │

Prev Up Next
probe::nfsd.proc.remove Home probe::nfsd.proc.write
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfsd-proc-write.html │ │ │ │ @@ -1,27 +1,27 @@ │ │ │ │ probe::nfsd.proc.write
probe::nfsd.proc.write
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfsd.proc.write — │ │ │ │ NFS server writing data to file for client │ │ │ │ -

Synopsis

nfsd.proc.write

Values

vec

│ │ │ │ - struct kvec, includes buf address in kernel address and length of each buffer │ │ │ │ -

fh

│ │ │ │ +

Synopsis

nfsd.proc.write

Values

fh

│ │ │ │ file handle (the first part is the length of the file handle) │ │ │ │ -

proto

│ │ │ │ - transfer protocol │ │ │ │ -

offset

│ │ │ │ - the offset of file │ │ │ │ -

count

│ │ │ │ - read bytes │ │ │ │ -

size

│ │ │ │ - read bytes │ │ │ │ -

gid

│ │ │ │ - requester's group id │ │ │ │

vlen

│ │ │ │ read blocks │ │ │ │ -

stable

│ │ │ │ - argp->stable │ │ │ │ +

gid

│ │ │ │ + requester's group id │ │ │ │ +

client_ip

│ │ │ │ + the ip address of client │ │ │ │ +

offset

│ │ │ │ + the offset of file │ │ │ │

uid

│ │ │ │ requester's user id │ │ │ │ +

vec

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

count

│ │ │ │ + read bytes │ │ │ │

version

│ │ │ │ nfs version │ │ │ │ -

client_ip

│ │ │ │ - the ip address of client │ │ │ │ +

stable

│ │ │ │ + argp->stable │ │ │ │ +

proto

│ │ │ │ + transfer protocol │ │ │ │ +

size

│ │ │ │ + read bytes │ │ │ │

Prev Up Next
probe::nfsd.proc.rename Home probe::nfsd.read
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfsd-read.html │ │ │ │ @@ -1,19 +1,19 @@ │ │ │ │ probe::nfsd.read
probe::nfsd.read
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfsd.read — │ │ │ │ NFS server reading data from a file for client │ │ │ │ -

Synopsis

nfsd.read

Values

count

│ │ │ │ - read bytes │ │ │ │ -

offset

│ │ │ │ - the offset of file │ │ │ │ -

size

│ │ │ │ - read bytes │ │ │ │ +

Synopsis

nfsd.read

Values

vlen

│ │ │ │ + read blocks │ │ │ │

fh

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

file

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

count

│ │ │ │ + read bytes │ │ │ │

vec

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

offset

│ │ │ │ + the offset of file │ │ │ │

client_ip

│ │ │ │ the ip address of client │ │ │ │ -

file

│ │ │ │ - argument file, indicates if the file has been opened. │ │ │ │ -

vlen

│ │ │ │ - read blocks │ │ │ │ +

size

│ │ │ │ + read bytes │ │ │ │

Prev Up Next
probe::nfsd.proc.write Home probe::nfsd.rename
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfsd-rename.html │ │ │ │ @@ -1,17 +1,17 @@ │ │ │ │ probe::nfsd.rename
probe::nfsd.rename
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfsd.rename — │ │ │ │ NFS server renaming a file for client │ │ │ │ -

Synopsis

nfsd.rename

Values

filename

│ │ │ │ - old file name │ │ │ │ -

tlen

│ │ │ │ +

Synopsis

nfsd.rename

Values

tlen

│ │ │ │ length of new file name │ │ │ │ -

client_ip

│ │ │ │ - the ip address of client │ │ │ │ -

fh

│ │ │ │ - file handler of old path │ │ │ │ -

flen

│ │ │ │ - length of old file name │ │ │ │

tname

│ │ │ │ new file name │ │ │ │ +

filename

│ │ │ │ + old file name │ │ │ │ +

flen

│ │ │ │ + length of old file name │ │ │ │ +

client_ip

│ │ │ │ + the ip address of client │ │ │ │

tfh

│ │ │ │ file handler of new path │ │ │ │ +

fh

│ │ │ │ + file handler of old path │ │ │ │

Prev Up Next
probe::nfsd.read Home probe::nfsd.unlink
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfsd-unlink.html │ │ │ │ @@ -1,13 +1,13 @@ │ │ │ │ probe::nfsd.unlink
probe::nfsd.unlink
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfsd.unlink — │ │ │ │ NFS server removing a file or a directory for client │ │ │ │ -

Synopsis

nfsd.unlink

Values

filename

│ │ │ │ - file name │ │ │ │ -

client_ip

│ │ │ │ +

Synopsis

nfsd.unlink

Values

client_ip

│ │ │ │ the ip address of client │ │ │ │ -

type

│ │ │ │ - file type (file or dir) │ │ │ │

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) │ │ │ │

Prev Up Next
probe::nfsd.rename Home probe::nfsd.write
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-nfsd-write.html │ │ │ │┄ Ordering differences only │ │ │ │ @@ -1,19 +1,19 @@ │ │ │ │ probe::nfsd.write
probe::nfsd.write
Prev Chapter 31. Network File Storage Tapsets Next

Name

probe::nfsd.write — │ │ │ │ NFS server writing data to a file for client │ │ │ │

Synopsis

nfsd.write

Values

client_ip

│ │ │ │ the ip address of client │ │ │ │ +

offset

│ │ │ │ + the offset of file │ │ │ │ +

count

│ │ │ │ + read bytes │ │ │ │ +

vec

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

file

│ │ │ │ argument file, indicates if the file has been opened. │ │ │ │

vlen

│ │ │ │ read blocks │ │ │ │ -

count

│ │ │ │ - read bytes │ │ │ │ -

offset

│ │ │ │ - the offset of file │ │ │ │ -

size

│ │ │ │ - read bytes │ │ │ │

fh

│ │ │ │ file handle (the first part is the length of the file handle) │ │ │ │ -

vec

│ │ │ │ - struct kvec, includes buf address in kernel address and length of each buffer │ │ │ │ +

size

│ │ │ │ + read bytes │ │ │ │

Prev Up Next
probe::nfsd.unlink Home Chapter 32. Speculation
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-scheduler-cpu-off.html │ │ │ │ @@ -1,13 +1,13 @@ │ │ │ │ probe::scheduler.cpu_off
probe::scheduler.cpu_off
Prev Chapter 8. Scheduler Tapset Next

Name

probe::scheduler.cpu_off — │ │ │ │ Process is about to stop running on a cpu │ │ │ │ -

Synopsis

scheduler.cpu_off

Values

task_next

│ │ │ │ - the process replacing current │ │ │ │ +

Synopsis

scheduler.cpu_off

Values

idle

│ │ │ │ + boolean indicating whether current is the idle process │ │ │ │

task_prev

│ │ │ │ the process leaving the cpu (same as current) │ │ │ │

name

│ │ │ │ name of the probe point │ │ │ │ -

idle

│ │ │ │ - boolean indicating whether current is the idle process │ │ │ │ +

task_next

│ │ │ │ + the process replacing current │ │ │ │

Context

│ │ │ │ The process leaving the cpu. │ │ │ │

Prev Up Next
probe::scheduler.balance Home probe::scheduler.cpu_on
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-scheduler-cpu-on.html │ │ │ │┄ Ordering differences only │ │ │ │ @@ -1,11 +1,11 @@ │ │ │ │ probe::scheduler.cpu_on
probe::scheduler.cpu_on
Prev Chapter 8. Scheduler Tapset Next

Name

probe::scheduler.cpu_on — │ │ │ │ Process is beginning execution on a cpu │ │ │ │

Synopsis

scheduler.cpu_on

Values

idle

│ │ │ │ - boolean indicating whether current is the idle process │ │ │ │ -

name

│ │ │ │ - name of the probe point │ │ │ │

task_prev

│ │ │ │ the process that was previously running on this cpu │ │ │ │ +

name

│ │ │ │ + name of the probe point │ │ │ │

Context

│ │ │ │ The resuming process. │ │ │ │

Prev Up Next
probe::scheduler.cpu_off Home probe::scheduler.ctxswitch
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-scheduler-ctxswitch.html │ │ │ │ @@ -1,25 +1,25 @@ │ │ │ │ probe::scheduler.ctxswitch
probe::scheduler.ctxswitch
Prev Chapter 8. Scheduler Tapset Next

Name

probe::scheduler.ctxswitch — │ │ │ │ A context switch is occuring. │ │ │ │ -

Synopsis

scheduler.ctxswitch

Values

prev_tid

│ │ │ │ - The TID of the process to be switched out │ │ │ │ -

prev_pid

│ │ │ │ - The PID of the process to be switched out │ │ │ │ -

name

│ │ │ │ - name of the probe point │ │ │ │ +

Synopsis

scheduler.ctxswitch

Values

next_task_name

│ │ │ │ + The name of the process to be switched in │ │ │ │

nexttsk_state

│ │ │ │ the state of the process to be switched in │ │ │ │ +

prevtsk_state

│ │ │ │ + the state of the process to be switched out │ │ │ │

prev_task_name

│ │ │ │ The name of the process to be switched out │ │ │ │ -

prev_priority

│ │ │ │ - The priority of the process to be switched out │ │ │ │ +

next_pid

│ │ │ │ + The PID of the process to be switched in │ │ │ │

next_priority

│ │ │ │ The priority of the process to be switched in │ │ │ │ -

prevtsk_state

│ │ │ │ - the state of the process to be switched out │ │ │ │ -

next_task_name

│ │ │ │ - The name of the process to be switched in │ │ │ │ +

name

│ │ │ │ + name of the probe point │ │ │ │

next_tid

│ │ │ │ The TID of the process to be switched in │ │ │ │ -

next_pid

│ │ │ │ - The PID of the process to be switched in │ │ │ │ +

prev_tid

│ │ │ │ + The TID of the process to be switched out │ │ │ │ +

prev_priority

│ │ │ │ + The priority of the process to be switched out │ │ │ │ +

prev_pid

│ │ │ │ + The PID of the process to be switched out │ │ │ │

Prev Up Next
probe::scheduler.cpu_on Home probe::scheduler.kthread_stop
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-scheduler-kthread-stop-return.html │ │ │ │ @@ -1,7 +1,7 @@ │ │ │ │ probe::scheduler.kthread_stop.return
probe::scheduler.kthread_stop.return
Prev Chapter 8. Scheduler Tapset Next

Name

probe::scheduler.kthread_stop.return — │ │ │ │ A kthread is stopped and gets the return value │ │ │ │ -

Synopsis

scheduler.kthread_stop.return

Values

name

│ │ │ │ - name of the probe point │ │ │ │ -

return_value

│ │ │ │ +

Synopsis

scheduler.kthread_stop.return

Values

return_value

│ │ │ │ return value after stopping the thread │ │ │ │ +

name

│ │ │ │ + name of the probe point │ │ │ │

Prev Up Next
probe::scheduler.kthread_stop Home probe::scheduler.migrate
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-scheduler-migrate.html │ │ │ │ @@ -1,15 +1,15 @@ │ │ │ │ probe::scheduler.migrate
probe::scheduler.migrate
Prev Chapter 8. Scheduler Tapset Next

Name

probe::scheduler.migrate — │ │ │ │ Task migrating across cpus │ │ │ │ -

Synopsis

scheduler.migrate

Values

priority

│ │ │ │ - priority of the task being migrated │ │ │ │ +

Synopsis

scheduler.migrate

Values

name

│ │ │ │ + name of the probe point │ │ │ │

task

│ │ │ │ the process that is being migrated │ │ │ │ -

cpu_to

│ │ │ │ - the destination cpu │ │ │ │ -

cpu_from

│ │ │ │ - the original cpu │ │ │ │ -

name

│ │ │ │ - name of the probe point │ │ │ │ +

priority

│ │ │ │ + priority of the task being migrated │ │ │ │

pid

│ │ │ │ PID of the task being migrated │ │ │ │ +

cpu_from

│ │ │ │ + the original cpu │ │ │ │ +

cpu_to

│ │ │ │ + the destination cpu │ │ │ │

Prev Up Next
probe::scheduler.kthread_stop.return Home probe::scheduler.process_exit
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-scheduler-process-exit.html │ │ │ │ @@ -1,9 +1,9 @@ │ │ │ │ probe::scheduler.process_exit
probe::scheduler.process_exit
Prev Chapter 8. Scheduler Tapset Next

Name

probe::scheduler.process_exit — │ │ │ │ Process exiting │ │ │ │ -

Synopsis

scheduler.process_exit

Values

pid

│ │ │ │ - PID of the process exiting │ │ │ │ +

Synopsis

scheduler.process_exit

Values

priority

│ │ │ │ + priority of the process exiting │ │ │ │

name

│ │ │ │ name of the probe point │ │ │ │ -

priority

│ │ │ │ - priority of the process exiting │ │ │ │ +

pid

│ │ │ │ + PID of the process exiting │ │ │ │

Prev Up Next
probe::scheduler.migrate Home probe::scheduler.process_fork
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-scheduler-process-fork.html │ │ │ │ @@ -1,9 +1,9 @@ │ │ │ │ probe::scheduler.process_fork
probe::scheduler.process_fork
Prev Chapter 8. Scheduler Tapset Next

Name

probe::scheduler.process_fork — │ │ │ │ Process forked │ │ │ │ -

Synopsis

scheduler.process_fork

Values

parent_pid

│ │ │ │ - PID of the parent process │ │ │ │ +

Synopsis

scheduler.process_fork

Values

name

│ │ │ │ + name of the probe point │ │ │ │

child_pid

│ │ │ │ PID of the child process │ │ │ │ -

name

│ │ │ │ - name of the probe point │ │ │ │ +

parent_pid

│ │ │ │ + PID of the parent process │ │ │ │

Prev Up Next
probe::scheduler.process_exit Home probe::scheduler.process_free
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-scheduler-process-free.html │ │ │ │ @@ -1,9 +1,9 @@ │ │ │ │ probe::scheduler.process_free
probe::scheduler.process_free
Prev Chapter 8. Scheduler Tapset Next

Name

probe::scheduler.process_free — │ │ │ │ Scheduler freeing a data structure for a process │ │ │ │ -

Synopsis

scheduler.process_free

Values

name

│ │ │ │ - name of the probe point │ │ │ │ -

pid

│ │ │ │ +

Synopsis

scheduler.process_free

Values

pid

│ │ │ │ PID of the process getting freed │ │ │ │

priority

│ │ │ │ priority of the process getting freed │ │ │ │ +

name

│ │ │ │ + name of the probe point │ │ │ │

Prev Up Next
probe::scheduler.process_fork Home probe::scheduler.process_wait
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-scheduler-signal-send.html │ │ │ │┄ Ordering differences only │ │ │ │ @@ -1,9 +1,9 @@ │ │ │ │ probe::scheduler.signal_send
probe::scheduler.signal_send
Prev Chapter 8. Scheduler Tapset Next

Name

probe::scheduler.signal_send — │ │ │ │ Sending a signal │ │ │ │

Synopsis

scheduler.signal_send

Values

signal_number

│ │ │ │ signal number │ │ │ │ -

name

│ │ │ │ - name of the probe point │ │ │ │

pid

│ │ │ │ pid of the process sending signal │ │ │ │ +

name

│ │ │ │ + name of the probe point │ │ │ │

Prev Up Next
probe::scheduler.process_wait Home probe::scheduler.tick
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-scheduler-tick.html │ │ │ │ @@ -1,9 +1,9 @@ │ │ │ │ probe::scheduler.tick
probe::scheduler.tick
Prev Chapter 8. Scheduler Tapset Next

Name

probe::scheduler.tick — │ │ │ │ Schedulers internal tick, a processes timeslice accounting is updated │ │ │ │ -

Synopsis

scheduler.tick

Values

name

│ │ │ │ - name of the probe point │ │ │ │ -

idle

│ │ │ │ +

Synopsis

scheduler.tick

Values

idle

│ │ │ │ boolean indicating whether current is the idle process │ │ │ │ +

name

│ │ │ │ + name of the probe point │ │ │ │

Context

│ │ │ │ The process whose accounting will be updated. │ │ │ │

Prev Up Next
probe::scheduler.signal_send Home probe::scheduler.wait_task
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-scheduler-wait-task.html │ │ │ │┄ Ordering differences only │ │ │ │ @@ -1,9 +1,9 @@ │ │ │ │ probe::scheduler.wait_task
probe::scheduler.wait_task
Prev Chapter 8. Scheduler Tapset Next

Name

probe::scheduler.wait_task — │ │ │ │ Waiting on a task to unschedule (become inactive) │ │ │ │

Synopsis

scheduler.wait_task

Values

name

│ │ │ │ name of the probe point │ │ │ │ -

task_pid

│ │ │ │ - PID of the task the scheduler is waiting on │ │ │ │

task_priority

│ │ │ │ priority of the task │ │ │ │ +

task_pid

│ │ │ │ + PID of the task the scheduler is waiting on │ │ │ │

Prev Up Next
probe::scheduler.tick Home probe::scheduler.wakeup
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-scheduler-wakeup-new.html │ │ │ │┄ Ordering differences only │ │ │ │ @@ -1,15 +1,15 @@ │ │ │ │ probe::scheduler.wakeup_new
probe::scheduler.wakeup_new
Prev Chapter 8. Scheduler Tapset Next

Name

probe::scheduler.wakeup_new — │ │ │ │ Newly created task is woken up for the first time │ │ │ │

Synopsis

scheduler.wakeup_new

Values

name

│ │ │ │ name of the probe point │ │ │ │

task_state

│ │ │ │ state of the task woken up │ │ │ │ +

task_cpu

│ │ │ │ + cpu of the task woken up │ │ │ │ +

task_tid

│ │ │ │ + TID of the new task woken up │ │ │ │

task_priority

│ │ │ │ priority of the new task │ │ │ │

task_pid

│ │ │ │ PID of the new task woken up │ │ │ │ -

task_tid

│ │ │ │ - TID of the new task woken up │ │ │ │ -

task_cpu

│ │ │ │ - cpu of the task woken up │ │ │ │

Prev Up Next
probe::scheduler.wakeup Home Chapter 9. IO Scheduler and block IO Tapset
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-scheduler-wakeup.html │ │ │ │ @@ -1,15 +1,15 @@ │ │ │ │ probe::scheduler.wakeup
probe::scheduler.wakeup
Prev Chapter 8. Scheduler Tapset Next

Name

probe::scheduler.wakeup — │ │ │ │ Task is woken up │ │ │ │ -

Synopsis

scheduler.wakeup

Values

task_cpu

│ │ │ │ - cpu of the task being woken up │ │ │ │ +

Synopsis

scheduler.wakeup

Values

task_tid

│ │ │ │ + tid of the task being woken up │ │ │ │

task_pid

│ │ │ │ PID of the task being woken up │ │ │ │ -

task_tid

│ │ │ │ - tid of the task being woken up │ │ │ │ -

task_state

│ │ │ │ - state of the task being woken up │ │ │ │

task_priority

│ │ │ │ priority of the task being woken up │ │ │ │ +

task_state

│ │ │ │ + state of the task being woken up │ │ │ │ +

task_cpu

│ │ │ │ + cpu of the task being woken up │ │ │ │

name

│ │ │ │ name of the probe point │ │ │ │

Prev Up Next
probe::scheduler.wait_task Home probe::scheduler.wakeup_new
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-scsi-iocompleted.html │ │ │ │ @@ -1,24 +1,24 @@ │ │ │ │ probe::scsi.iocompleted
probe::scsi.iocompleted
Prev Chapter 10. SCSI Tapset Next

Name

probe::scsi.iocompleted — │ │ │ │ SCSI mid-layer running the completion processing for block device I/O requests │ │ │ │ -

Synopsis

scsi.iocompleted

Values

req_addr

│ │ │ │ - The current struct request pointer, as a number │ │ │ │ -

device_state

│ │ │ │ - The current state of the device │ │ │ │ -

dev_id

│ │ │ │ - The scsi device id │ │ │ │ -

data_direction_str

│ │ │ │ - Data direction, as a string │ │ │ │ -

host_no

│ │ │ │ - The host number │ │ │ │ -

data_direction

│ │ │ │ +

Synopsis

scsi.iocompleted

Values

data_direction

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

goodbytes

│ │ │ │ The bytes completed │ │ │ │ -

device_state_str

│ │ │ │ - The current state of the device, as a string │ │ │ │

lun

│ │ │ │ The lun number │ │ │ │ +

req_addr

│ │ │ │ + The current struct request pointer, as a number │ │ │ │ +

host_no

│ │ │ │ + The host number │ │ │ │ +

device_state_str

│ │ │ │ + The current state of the device, as a string │ │ │ │ +

data_direction_str

│ │ │ │ + Data direction, as a string │ │ │ │ +

dev_id

│ │ │ │ + The scsi device id │ │ │ │ +

device_state

│ │ │ │ + The current state of the device │ │ │ │

channel

│ │ │ │ The channel number │ │ │ │

Prev Up Next
Chapter 10. SCSI Tapset Home probe::scsi.iodispatching
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-scsi-iodispatching.html │ │ │ │ @@ -1,27 +1,27 @@ │ │ │ │ probe::scsi.iodispatching
probe::scsi.iodispatching
Prev Chapter 10. SCSI Tapset Next

Name

probe::scsi.iodispatching — │ │ │ │ SCSI mid-layer dispatched low-level SCSI command │ │ │ │ -

Synopsis

scsi.iodispatching

Values

req_addr

│ │ │ │ - The current struct request pointer, as a number │ │ │ │ +

Synopsis

scsi.iodispatching

Values

dev_id

│ │ │ │ + The scsi device id │ │ │ │ +

request_bufflen

│ │ │ │ + The request buffer length │ │ │ │ +

data_direction_str

│ │ │ │ + Data direction, as a string │ │ │ │ +

channel

│ │ │ │ + The channel number │ │ │ │

device_state

│ │ │ │ The current state of the device │ │ │ │ -

dev_id

│ │ │ │ - The scsi device id │ │ │ │ +

request_buffer

│ │ │ │ + The request buffer address │ │ │ │

data_direction

│ │ │ │ The data_direction specifies whether this command is from/to the device │ │ │ │ 0 (DMA_BIDIRECTIONAL), 1 (DMA_TO_DEVICE), │ │ │ │ 2 (DMA_FROM_DEVICE), 3 (DMA_NONE) │ │ │ │ -

host_no

│ │ │ │ - The host number │ │ │ │ -

data_direction_str

│ │ │ │ - Data direction, as a string │ │ │ │ +

req_addr

│ │ │ │ + The current struct request pointer, as a number │ │ │ │

lun

│ │ │ │ The lun number │ │ │ │ +

host_no

│ │ │ │ + The host number │ │ │ │

device_state_str

│ │ │ │ The current state of the device, as a string │ │ │ │ -

request_bufflen

│ │ │ │ - The request buffer length │ │ │ │ -

channel

│ │ │ │ - The channel number │ │ │ │ -

request_buffer

│ │ │ │ - The request buffer address │ │ │ │

Prev Up Next
probe::scsi.iocompleted Home probe::scsi.iodone
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-scsi-iodone.html │ │ │ │ @@ -1,24 +1,24 @@ │ │ │ │ probe::scsi.iodone
probe::scsi.iodone
Prev Chapter 10. SCSI Tapset Next

Name

probe::scsi.iodone — │ │ │ │ SCSI command completed by low level driver and enqueued into the done queue. │ │ │ │ -

Synopsis

scsi.iodone

Values

scsi_timer_pending

│ │ │ │ +

Synopsis

scsi.iodone

Values

host_no

│ │ │ │ + The host number │ │ │ │ +

scsi_timer_pending

│ │ │ │ 1 if a timer is pending on this request │ │ │ │

device_state_str

│ │ │ │ The current state of the device, as a string │ │ │ │ +

data_direction

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

lun

│ │ │ │ The lun number │ │ │ │ -

channel

│ │ │ │ - The channel number │ │ │ │ -

device_state

│ │ │ │ - The current state of the device │ │ │ │

req_addr

│ │ │ │ The current struct request pointer, as a number │ │ │ │ -

dev_id

│ │ │ │ - The scsi device id │ │ │ │

data_direction_str

│ │ │ │ Data direction, as a string │ │ │ │ -

data_direction

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

host_no

│ │ │ │ - The host number │ │ │ │ +

dev_id

│ │ │ │ + The scsi device id │ │ │ │ +

device_state

│ │ │ │ + The current state of the device │ │ │ │ +

channel

│ │ │ │ + The channel number │ │ │ │

Prev Up Next
probe::scsi.iodispatching Home probe::scsi.ioentry
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-scsi-ioentry.html │ │ │ │ @@ -1,13 +1,13 @@ │ │ │ │ probe::scsi.ioentry
probe::scsi.ioentry
Prev Chapter 10. SCSI Tapset Next

Name

probe::scsi.ioentry — │ │ │ │ Prepares a SCSI mid-layer request │ │ │ │ -

Synopsis

scsi.ioentry

Values

disk_minor

│ │ │ │ - The minor number of the disk (-1 if no information) │ │ │ │ +

Synopsis

scsi.ioentry

Values

disk_major

│ │ │ │ + The major number of the disk (-1 if no information) │ │ │ │

device_state_str

│ │ │ │ The current state of the device, as a string │ │ │ │ -

disk_major

│ │ │ │ - The major number of the disk (-1 if no information) │ │ │ │ -

device_state

│ │ │ │ - The current state of the device │ │ │ │ +

disk_minor

│ │ │ │ + The minor number of the disk (-1 if no information) │ │ │ │

req_addr

│ │ │ │ The current struct request pointer, as a number │ │ │ │ +

device_state

│ │ │ │ + The current state of the device │ │ │ │

Prev Up Next
probe::scsi.iodone Home probe::scsi.ioexecute
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-scsi-ioexecute.html │ │ │ │ @@ -1,28 +1,28 @@ │ │ │ │ probe::scsi.ioexecute
probe::scsi.ioexecute
Prev Chapter 10. SCSI Tapset Next

Name

probe::scsi.ioexecute — │ │ │ │ Create mid-layer SCSI request and wait for the result │ │ │ │ -

Synopsis

scsi.ioexecute

Values

retries

│ │ │ │ - Number of times to retry request │ │ │ │ -

lun

│ │ │ │ - The lun number │ │ │ │ -

device_state_str

│ │ │ │ - The current state of the device, as a string │ │ │ │ -

request_bufflen

│ │ │ │ - The data buffer buffer length │ │ │ │ -

channel

│ │ │ │ - The channel number │ │ │ │ -

request_buffer

│ │ │ │ - The data buffer address │ │ │ │ +

Synopsis

scsi.ioexecute

Values

timeout

│ │ │ │ + Request timeout in seconds │ │ │ │

device_state

│ │ │ │ The current state of the device │ │ │ │ -

timeout

│ │ │ │ - Request timeout in seconds │ │ │ │ +

data_direction_str

│ │ │ │ + Data direction, as a string │ │ │ │

dev_id

│ │ │ │ The scsi device id │ │ │ │ +

request_buffer

│ │ │ │ + The data buffer address │ │ │ │ +

lun

│ │ │ │ + The lun number │ │ │ │ +

device_state_str

│ │ │ │ + The current state of the device, as a string │ │ │ │

host_no

│ │ │ │ The host number │ │ │ │ +

channel

│ │ │ │ + The channel number │ │ │ │ +

request_bufflen

│ │ │ │ + The data buffer buffer length │ │ │ │ +

retries

│ │ │ │ + Number of times to retry request │ │ │ │

data_direction

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

data_direction_str

│ │ │ │ - Data direction, as a string │ │ │ │

Prev Up Next
probe::scsi.ioentry Home probe::scsi.set_state
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-scsi-set-state.html │ │ │ │ @@ -1,19 +1,19 @@ │ │ │ │ probe::scsi.set_state
probe::scsi.set_state
Prev Chapter 10. SCSI Tapset Next

Name

probe::scsi.set_state — │ │ │ │ Order SCSI device state change │ │ │ │ -

Synopsis

scsi.set_state

Values

state_str

│ │ │ │ - The new state of the device, as a string │ │ │ │ -

lun

│ │ │ │ - The lun number │ │ │ │ +

Synopsis

scsi.set_state

Values

channel

│ │ │ │ + The channel number │ │ │ │

state

│ │ │ │ The new state of the device │ │ │ │ -

old_state

│ │ │ │ - The current state of the device │ │ │ │ +

dev_id

│ │ │ │ + The scsi device id │ │ │ │

old_state_str

│ │ │ │ The current state of the device, as a string │ │ │ │ -

channel

│ │ │ │ - The channel number │ │ │ │ +

old_state

│ │ │ │ + The current state of the device │ │ │ │ +

lun

│ │ │ │ + The lun number │ │ │ │

host_no

│ │ │ │ The host number │ │ │ │ -

dev_id

│ │ │ │ - The scsi device id │ │ │ │ +

state_str

│ │ │ │ + The new state of the device, as a string │ │ │ │

Prev Up Next
probe::scsi.ioexecute Home Chapter 11. TTY Tapset
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-signal-check-ignored.html │ │ │ │ @@ -1,11 +1,11 @@ │ │ │ │ probe::signal.check_ignored
probe::signal.check_ignored
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.check_ignored — │ │ │ │ Checking to see signal is ignored │ │ │ │ -

Synopsis

signal.check_ignored

Values

sig_name

│ │ │ │ - A string representation of the signal │ │ │ │ +

Synopsis

signal.check_ignored

Values

sig

│ │ │ │ + The number of the signal │ │ │ │

sig_pid

│ │ │ │ The PID of the process receiving the signal │ │ │ │ -

sig

│ │ │ │ - The number of the signal │ │ │ │

pid_name

│ │ │ │ Name of the process receiving the signal │ │ │ │ +

sig_name

│ │ │ │ + A string representation of the signal │ │ │ │

Prev Up Next
function::sigset_mask_str Home probe::signal.check_ignored.return
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-signal-checkperm.html │ │ │ │ @@ -1,19 +1,19 @@ │ │ │ │ probe::signal.checkperm
probe::signal.checkperm
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.checkperm — │ │ │ │ Check being performed on a sent signal │ │ │ │ -

Synopsis

signal.checkperm

Values

pid_name

│ │ │ │ - Name of the process receiving the signal │ │ │ │ +

Synopsis

signal.checkperm

Values

sig_name

│ │ │ │ + A string representation of the signal │ │ │ │

name

│ │ │ │ Name of the probe point │ │ │ │ -

sinfo

│ │ │ │ - The address of the siginfo structure │ │ │ │ -

sig_pid

│ │ │ │ - The PID of the process receiving the signal │ │ │ │ +

pid_name

│ │ │ │ + Name of the process receiving the signal │ │ │ │ +

task

│ │ │ │ + A task handle to the signal recipient │ │ │ │

sig

│ │ │ │ The number of the signal │ │ │ │ +

sinfo

│ │ │ │ + The address of the siginfo structure │ │ │ │

si_code

│ │ │ │ Indicates the signal type │ │ │ │ -

sig_name

│ │ │ │ - A string representation of the signal │ │ │ │ -

task

│ │ │ │ - A task handle to the signal recipient │ │ │ │ +

sig_pid

│ │ │ │ + The PID of the process receiving the signal │ │ │ │

Prev Up Next
probe::signal.check_ignored.return Home probe::signal.checkperm.return
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-signal-do-action.html │ │ │ │ @@ -1,19 +1,19 @@ │ │ │ │ probe::signal.do_action
probe::signal.do_action
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.do_action — │ │ │ │ Examining or changing a signal action │ │ │ │ -

Synopsis

signal.do_action

Values

sa_mask

│ │ │ │ +

Synopsis

signal.do_action

Values

sigact_addr

│ │ │ │ + The address of the new sigaction │ │ │ │ + struct associated with the signal │ │ │ │ +

sa_mask

│ │ │ │ The new mask of the signal │ │ │ │ +

sig

│ │ │ │ + The signal to be examined/changed │ │ │ │

sa_handler

│ │ │ │ The new handler of the signal │ │ │ │ +

oldsigact_addr

│ │ │ │ + The address of the old sigaction │ │ │ │ + struct associated with the signal │ │ │ │

name

│ │ │ │ Name of the probe point │ │ │ │ -

sigact_addr

│ │ │ │ - The address of the new sigaction │ │ │ │ - struct associated with the signal │ │ │ │

sig_name

│ │ │ │ A string representation of the signal │ │ │ │ -

oldsigact_addr

│ │ │ │ - The address of the old sigaction │ │ │ │ - struct associated with the signal │ │ │ │ -

sig

│ │ │ │ - The signal to be examined/changed │ │ │ │

Prev Up Next
probe::signal.checkperm.return Home probe::signal.do_action.return
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-signal-flush.html │ │ │ │ @@ -1,13 +1,13 @@ │ │ │ │ probe::signal.flush
probe::signal.flush
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.flush — │ │ │ │ Flushing all pending signals for a task │ │ │ │ -

Synopsis

signal.flush

Values

sig_pid

│ │ │ │ +

Synopsis

signal.flush

Values

name

│ │ │ │ + Name of the probe point │ │ │ │ +

sig_pid

│ │ │ │ The PID of the process associated with the task │ │ │ │ performing the flush │ │ │ │

task

│ │ │ │ The task handler of the process performing the flush │ │ │ │

pid_name

│ │ │ │ The name of the process associated with the task │ │ │ │ performing the flush │ │ │ │ -

name

│ │ │ │ - Name of the probe point │ │ │ │

Prev Up Next
probe::signal.do_action.return Home probe::signal.force_segv
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-signal-force-segv-return.html │ │ │ │ @@ -1,7 +1,7 @@ │ │ │ │ probe::signal.force_segv.return
probe::signal.force_segv.return
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.force_segv.return — │ │ │ │ Forcing send of SIGSEGV complete │ │ │ │ -

Synopsis

signal.force_segv.return

Values

name

│ │ │ │ - Name of the probe point │ │ │ │ -

retstr

│ │ │ │ +

Synopsis

signal.force_segv.return

Values

retstr

│ │ │ │ Return value as a string │ │ │ │ +

name

│ │ │ │ + Name of the probe point │ │ │ │

Prev Up Next
probe::signal.force_segv Home probe::signal.handle
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-signal-force-segv.html │ │ │ │ @@ -1,13 +1,13 @@ │ │ │ │ probe::signal.force_segv
probe::signal.force_segv
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.force_segv — │ │ │ │ Forcing send of SIGSEGV │ │ │ │ -

Synopsis

signal.force_segv

Values

sig_name

│ │ │ │ - A string representation of the signal │ │ │ │ +

Synopsis

signal.force_segv

Values

pid_name

│ │ │ │ + Name of the process receiving the signal │ │ │ │

sig

│ │ │ │ The number of the signal │ │ │ │

sig_pid

│ │ │ │ The PID of the process receiving the signal │ │ │ │ -

pid_name

│ │ │ │ - Name of the process receiving the signal │ │ │ │ +

sig_name

│ │ │ │ + A string representation of the signal │ │ │ │

name

│ │ │ │ Name of the probe point │ │ │ │

Prev Up Next
probe::signal.flush Home probe::signal.force_segv.return
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-signal-handle.html │ │ │ │ @@ -1,24 +1,24 @@ │ │ │ │ probe::signal.handle
probe::signal.handle
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.handle — │ │ │ │ Signal handler being invoked │ │ │ │ -

Synopsis

signal.handle

Values

sig

│ │ │ │ +

Synopsis

signal.handle

Values

ka_addr

│ │ │ │ + The address of the k_sigaction table │ │ │ │ + associated with the signal │ │ │ │ +

sig

│ │ │ │ The signal number that invoked the signal handler │ │ │ │ +

sinfo

│ │ │ │ + The address of the siginfo table │ │ │ │ +

regs

│ │ │ │ + The address of the kernel-mode stack area (deprecated in │ │ │ │ + SystemTap 2.1) │ │ │ │ +

name

│ │ │ │ + Name of the probe point │ │ │ │

sig_code

│ │ │ │ The si_code value of the siginfo signal │ │ │ │ +

sig_name

│ │ │ │ + A string representation of the signal │ │ │ │

oldset_addr

│ │ │ │ The address of the bitmask array of blocked signals │ │ │ │ (deprecated in SystemTap 2.1) │ │ │ │ -

sig_name

│ │ │ │ - A string representation of the signal │ │ │ │ -

ka_addr

│ │ │ │ - The address of the k_sigaction table │ │ │ │ - associated with the signal │ │ │ │

sig_mode

│ │ │ │ Indicates whether the signal was a user-mode or kernel-mode signal │ │ │ │ -

regs

│ │ │ │ - The address of the kernel-mode stack area (deprecated in │ │ │ │ - SystemTap 2.1) │ │ │ │ -

name

│ │ │ │ - Name of the probe point │ │ │ │ -

sinfo

│ │ │ │ - The address of the siginfo table │ │ │ │

Prev Up Next
probe::signal.force_segv.return Home probe::signal.handle.return
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-signal-pending-return.html │ │ │ │ @@ -1,7 +1,7 @@ │ │ │ │ probe::signal.pending.return
probe::signal.pending.return
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.pending.return — │ │ │ │ Examination of pending signal completed │ │ │ │ -

Synopsis

signal.pending.return

Values

retstr

│ │ │ │ - Return value as a string │ │ │ │ -

name

│ │ │ │ +

Synopsis

signal.pending.return

Values

name

│ │ │ │ Name of the probe point │ │ │ │ +

retstr

│ │ │ │ + Return value as a string │ │ │ │

Prev Up Next
probe::signal.pending Home probe::signal.procmask
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-signal-pending.html │ │ │ │ @@ -1,14 +1,14 @@ │ │ │ │ probe::signal.pending
probe::signal.pending
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.pending — │ │ │ │ Examining pending signal │ │ │ │ -

Synopsis

signal.pending

Values

name

│ │ │ │ - Name of the probe point │ │ │ │ +

Synopsis

signal.pending

Values

sigset_size

│ │ │ │ + The size of the user-space signal set │ │ │ │

sigset_add

│ │ │ │ The address of the user-space signal set │ │ │ │ (sigset_t) │ │ │ │ -

sigset_size

│ │ │ │ - The size of the user-space signal set │ │ │ │ +

name

│ │ │ │ + Name of the probe point │ │ │ │

Description

│ │ │ │ This probe is used to examine a set of signals pending for delivery │ │ │ │ to a specific thread. This normally occurs when the │ │ │ │ do_sigpending kernel function is executed. │ │ │ │

Prev Up Next
probe::signal.handle.return Home probe::signal.pending.return
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-signal-procmask-return.html │ │ │ │ @@ -1,7 +1,7 @@ │ │ │ │ probe::signal.procmask.return
probe::signal.procmask.return
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.procmask.return — │ │ │ │ Examining or changing blocked signals completed │ │ │ │ -

Synopsis

signal.procmask.return

Values

retstr

│ │ │ │ - Return value as a string │ │ │ │ -

name

│ │ │ │ +

Synopsis

signal.procmask.return

Values

name

│ │ │ │ Name of the probe point │ │ │ │ +

retstr

│ │ │ │ + Return value as a string │ │ │ │

Prev Up Next
probe::signal.procmask Home probe::signal.send
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-signal-procmask.html │ │ │ │ @@ -1,19 +1,19 @@ │ │ │ │ probe::signal.procmask
probe::signal.procmask
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.procmask — │ │ │ │ Examining or changing blocked signals │ │ │ │ -

Synopsis

signal.procmask

Values

how

│ │ │ │ - Indicates how to change the blocked signals; possible values are │ │ │ │ - SIG_BLOCK=0 (for blocking signals), │ │ │ │ - SIG_UNBLOCK=1 (for unblocking signals), and │ │ │ │ - SIG_SETMASK=2 for setting the signal mask. │ │ │ │ +

Synopsis

signal.procmask

Values

sigset_addr

│ │ │ │ + The address of the signal set (sigset_t) │ │ │ │ + to be implemented │ │ │ │

sigset

│ │ │ │ The actual value to be set for sigset_t │ │ │ │ (correct?) │ │ │ │

name

│ │ │ │ Name of the probe point │ │ │ │

oldsigset_addr

│ │ │ │ The old address of the signal set │ │ │ │ (sigset_t) │ │ │ │ -

sigset_addr

│ │ │ │ - The address of the signal set (sigset_t) │ │ │ │ - to be implemented │ │ │ │ +

how

│ │ │ │ + Indicates how to change the blocked signals; possible values are │ │ │ │ + SIG_BLOCK=0 (for blocking signals), │ │ │ │ + SIG_UNBLOCK=1 (for unblocking signals), and │ │ │ │ + SIG_SETMASK=2 for setting the signal mask. │ │ │ │

Prev Up Next
probe::signal.pending.return Home probe::signal.procmask.return
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-signal-send-return.html │ │ │ │ @@ -1,17 +1,17 @@ │ │ │ │ probe::signal.send.return
probe::signal.send.return
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.send.return — │ │ │ │ Signal being sent to a process completed (deprecated in SystemTap 2.1) │ │ │ │ -

Synopsis

signal.send.return

Values

shared

│ │ │ │ +

Synopsis

signal.send.return

Values

send2queue

│ │ │ │ + Indicates whether the sent signal was sent to an existing sigqueue │ │ │ │ +

shared

│ │ │ │ Indicates whether the sent signal is shared by the thread group. │ │ │ │

retstr

│ │ │ │ The return value to either __group_send_sig_info, specific_send_sig_info, or send_sigqueue │ │ │ │

name

│ │ │ │ The name of the function used to send out the signal │ │ │ │ -

send2queue

│ │ │ │ - Indicates whether the sent signal was sent to an existing sigqueue │ │ │ │

Context

│ │ │ │ The signal's sender. (correct?) │ │ │ │

Description

│ │ │ │ Possible __group_send_sig_info and │ │ │ │ specific_send_sig_info return values are as follows; │ │ │ │

│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-signal-send-sig-queue.html │ │ │ │ @@ -1,15 +1,15 @@ │ │ │ │ probe::signal.send_sig_queue

probe::signal.send_sig_queue
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.send_sig_queue — │ │ │ │ Queuing a signal to a process │ │ │ │ -

Synopsis

signal.send_sig_queue

Values

sigqueue_addr

│ │ │ │ - The address of the signal queue │ │ │ │ +

Synopsis

signal.send_sig_queue

Values

sig_pid

│ │ │ │ + The PID of the process to which the signal is queued │ │ │ │

sig

│ │ │ │ The queued signal │ │ │ │ -

sig_pid

│ │ │ │ - The PID of the process to which the signal is queued │ │ │ │ -

sig_name

│ │ │ │ - A string representation of the signal │ │ │ │ +

sigqueue_addr

│ │ │ │ + The address of the signal queue │ │ │ │

pid_name

│ │ │ │ Name of the process to which the signal is queued │ │ │ │

name

│ │ │ │ Name of the probe point │ │ │ │ +

sig_name

│ │ │ │ + A string representation of the signal │ │ │ │

Prev Up Next
probe::signal.send.return Home probe::signal.send_sig_queue.return
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-signal-send.html │ │ │ │ @@ -1,26 +1,26 @@ │ │ │ │ probe::signal.send
probe::signal.send
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.send — │ │ │ │ Signal being sent to a process │ │ │ │ -

Synopsis

signal.send

Values

name

│ │ │ │ - The name of the function used to send out the signal │ │ │ │ -

pid_name

│ │ │ │ - The name of the signal recipient │ │ │ │ -

shared

│ │ │ │ - Indicates whether the signal is shared by the thread group │ │ │ │ +

Synopsis

signal.send

Values

task

│ │ │ │ + A task handle to the signal recipient │ │ │ │

sinfo

│ │ │ │ The address of siginfo struct │ │ │ │ -

send2queue

│ │ │ │ - Indicates whether the signal is sent to an existing │ │ │ │ - sigqueue (deprecated in SystemTap 2.1) │ │ │ │

sig

│ │ │ │ The number of the signal │ │ │ │ -

sig_pid

│ │ │ │ - The PID of the process receiving the signal │ │ │ │

si_code

│ │ │ │ Indicates the signal type │ │ │ │ -

task

│ │ │ │ - A task handle to the signal recipient │ │ │ │ +

sig_pid

│ │ │ │ + The PID of the process receiving the signal │ │ │ │ +

pid_name

│ │ │ │ + The name of the signal recipient │ │ │ │

sig_name

│ │ │ │ A string representation of the signal │ │ │ │ +

name

│ │ │ │ + The name of the function used to send out the signal │ │ │ │ +

send2queue

│ │ │ │ + Indicates whether the signal is sent to an existing │ │ │ │ + sigqueue (deprecated in SystemTap 2.1) │ │ │ │ +

shared

│ │ │ │ + Indicates whether the signal is shared by the thread group │ │ │ │

Context

│ │ │ │ The signal's sender. │ │ │ │

Prev Up Next
probe::signal.procmask.return Home probe::signal.send.return
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-signal-sys-tgkill.html │ │ │ │ @@ -1,21 +1,21 @@ │ │ │ │ probe::signal.sys_tgkill
probe::signal.sys_tgkill
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.sys_tgkill — │ │ │ │ Sending kill signal to a thread group │ │ │ │ -

Synopsis

signal.sys_tgkill

Values

sig_pid

│ │ │ │ - The PID of the thread receiving the kill signal │ │ │ │ +

Synopsis

signal.sys_tgkill

Values

sig_name

│ │ │ │ + A string representation of the signal │ │ │ │ +

name

│ │ │ │ + Name of the probe point │ │ │ │ +

tgid

│ │ │ │ + The thread group ID of the thread receiving the kill signal │ │ │ │

sig

│ │ │ │ The specific kill signal sent to the process │ │ │ │ -

sig_name

│ │ │ │ - A string representation of the signal │ │ │ │

task

│ │ │ │ A task handle to the signal recipient │ │ │ │ +

sig_pid

│ │ │ │ + The PID of the thread receiving the kill signal │ │ │ │

pid_name

│ │ │ │ The name of the signal recipient │ │ │ │ -

name

│ │ │ │ - Name of the probe point │ │ │ │ -

tgid

│ │ │ │ - The thread group ID of the thread receiving the kill signal │ │ │ │

Description

│ │ │ │ The tgkill call is similar to tkill, │ │ │ │ except that it also allows the caller to specify the thread group ID of │ │ │ │ the thread to be signalled. This protects against TID reuse. │ │ │ │

Prev Up Next
probe::signal.send_sig_queue.return Home probe::signal.sys_tgkill.return
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-signal-sys-tkill.html │ │ │ │ @@ -1,20 +1,20 @@ │ │ │ │ probe::signal.sys_tkill
probe::signal.sys_tkill
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.sys_tkill — │ │ │ │ Sending a kill signal to a thread │ │ │ │ -

Synopsis

signal.sys_tkill

Values

name

│ │ │ │ +

Synopsis

signal.sys_tkill

Values

sig_name

│ │ │ │ + A string representation of the signal │ │ │ │ +

name

│ │ │ │ Name of the probe point │ │ │ │ -

pid_name

│ │ │ │ - The name of the signal recipient │ │ │ │

sig

│ │ │ │ The specific signal sent to the process │ │ │ │ -

sig_pid

│ │ │ │ - The PID of the process receiving the kill signal │ │ │ │

task

│ │ │ │ A task handle to the signal recipient │ │ │ │ -

sig_name

│ │ │ │ - A string representation of the signal │ │ │ │ +

sig_pid

│ │ │ │ + The PID of the process receiving the kill signal │ │ │ │ +

pid_name

│ │ │ │ + The name of the signal recipient │ │ │ │

Description

│ │ │ │ The tkill call is analogous to kill(2), │ │ │ │ except that it also allows a process within a specific thread group to │ │ │ │ be targeted. Such processes are targeted through their unique │ │ │ │ thread IDs (TID). │ │ │ │

Prev Up Next
probe::signal.sys_tgkill.return Home probe::signal.syskill
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-signal-syskill.html │ │ │ │┄ Ordering differences only │ │ │ │ @@ -1,15 +1,15 @@ │ │ │ │ probe::signal.syskill
probe::signal.syskill
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.syskill — │ │ │ │ Sending kill signal to a process │ │ │ │

Synopsis

signal.syskill

Values

sig

│ │ │ │ The specific signal sent to the process │ │ │ │ -

sig_pid

│ │ │ │ - The PID of the process receiving the signal │ │ │ │ -

sig_name

│ │ │ │ - A string representation of the signal │ │ │ │

task

│ │ │ │ A task handle to the signal recipient │ │ │ │ +

sig_pid

│ │ │ │ + The PID of the process receiving the signal │ │ │ │

pid_name

│ │ │ │ The name of the signal recipient │ │ │ │ +

sig_name

│ │ │ │ + A string representation of the signal │ │ │ │

name

│ │ │ │ Name of the probe point │ │ │ │

Prev Up Next
probe::signal.sys_tkill Home probe::signal.syskill.return
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-signal-wakeup.html │ │ │ │ @@ -1,15 +1,15 @@ │ │ │ │ probe::signal.wakeup
probe::signal.wakeup
Prev Chapter 17. Signal Tapset Next

Name

probe::signal.wakeup — │ │ │ │ Sleeping process being wakened for signal │ │ │ │ -

Synopsis

signal.wakeup

Values

sig_pid

│ │ │ │ - The PID of the process to wake │ │ │ │ +

Synopsis

signal.wakeup

Values

state_mask

│ │ │ │ + A string representation indicating the mask │ │ │ │ + of task states to wake. Possible values are │ │ │ │ + TASK_INTERRUPTIBLE, TASK_STOPPED, │ │ │ │ + TASK_TRACED, TASK_WAKEKILL, and TASK_INTERRUPTIBLE. │ │ │ │

resume

│ │ │ │ Indicates whether to wake up a task in a │ │ │ │ STOPPED or TRACED state │ │ │ │

pid_name

│ │ │ │ Name of the process to wake │ │ │ │ -

state_mask

│ │ │ │ - A string representation indicating the mask │ │ │ │ - of task states to wake. Possible values are │ │ │ │ - TASK_INTERRUPTIBLE, TASK_STOPPED, │ │ │ │ - TASK_TRACED, TASK_WAKEKILL, and TASK_INTERRUPTIBLE. │ │ │ │ +

sig_pid

│ │ │ │ + The PID of the process to wake │ │ │ │

Prev Up Next
probe::signal.systkill.return Home Chapter 18. Errno Tapset
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-socket-aio-read-return.html │ │ │ │ @@ -1,24 +1,24 @@ │ │ │ │ probe::socket.aio_read.return
probe::socket.aio_read.return
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.aio_read.return — │ │ │ │ Conclusion of message received via sock_aio_read │ │ │ │ -

Synopsis

socket.aio_read.return

Values

name

│ │ │ │ - Name of this probe │ │ │ │ -

family

│ │ │ │ - Protocol family value │ │ │ │ -

success

│ │ │ │ +

Synopsis

socket.aio_read.return

Values

success

│ │ │ │ Was receive successful? (1 = yes, 0 = no) │ │ │ │ -

size

│ │ │ │ - Size of message received (in bytes) or error code if success = 0 │ │ │ │ -

state

│ │ │ │ - Socket state value │ │ │ │

type

│ │ │ │ Socket type value │ │ │ │ -

flags

│ │ │ │ - Socket flags value │ │ │ │ +

name

│ │ │ │ + Name of this probe │ │ │ │ +

state

│ │ │ │ + Socket state value │ │ │ │ +

size

│ │ │ │ + Size of message received (in bytes) or error code if success = 0 │ │ │ │

protocol

│ │ │ │ Protocol value │ │ │ │ +

flags

│ │ │ │ + Socket flags value │ │ │ │ +

family

│ │ │ │ + Protocol family value │ │ │ │

Context

│ │ │ │ The message receiver. │ │ │ │

Description

│ │ │ │ Fires at the conclusion of receiving a message on a socket │ │ │ │ via the sock_aio_read function │ │ │ │

Prev Up Next
probe::socket.aio_read Home probe::socket.aio_write
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-socket-aio-read.html │ │ │ │ @@ -1,22 +1,22 @@ │ │ │ │ probe::socket.aio_read
probe::socket.aio_read
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.aio_read — │ │ │ │ Receiving message via sock_aio_read │ │ │ │ -

Synopsis

socket.aio_read

Values

name

│ │ │ │ - Name of this probe │ │ │ │ -

family

│ │ │ │ - Protocol family value │ │ │ │ +

Synopsis

socket.aio_read

Values

protocol

│ │ │ │ + Protocol value │ │ │ │

size

│ │ │ │ Message size in bytes │ │ │ │ -

state

│ │ │ │ - Socket state value │ │ │ │ +

family

│ │ │ │ + Protocol family value │ │ │ │

flags

│ │ │ │ Socket flags value │ │ │ │ -

protocol

│ │ │ │ - Protocol value │ │ │ │ +

state

│ │ │ │ + Socket state value │ │ │ │

type

│ │ │ │ Socket type value │ │ │ │ +

name

│ │ │ │ + Name of this probe │ │ │ │

Context

│ │ │ │ The message sender │ │ │ │

Description

│ │ │ │ Fires at the beginning of receiving a message on a socket │ │ │ │ via the sock_aio_read function │ │ │ │

Prev Up Next
function::sock_state_str2num Home probe::socket.aio_read.return
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-socket-aio-write-return.html │ │ │ │ @@ -1,24 +1,24 @@ │ │ │ │ probe::socket.aio_write.return
probe::socket.aio_write.return
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.aio_write.return — │ │ │ │ Conclusion of message send via sock_aio_write │ │ │ │ -

Synopsis

socket.aio_write.return

Values

type

│ │ │ │ +

Synopsis

socket.aio_write.return

Values

state

│ │ │ │ + Socket state value │ │ │ │ +

name

│ │ │ │ + Name of this probe │ │ │ │ +

type

│ │ │ │ Socket type value │ │ │ │ -

protocol

│ │ │ │ - Protocol value │ │ │ │ -

flags

│ │ │ │ - Socket flags value │ │ │ │

success

│ │ │ │ Was receive successful? (1 = yes, 0 = no) │ │ │ │ -

size

│ │ │ │ - Size of message received (in bytes) or error code if success = 0 │ │ │ │

family

│ │ │ │ Protocol family value │ │ │ │ -

name

│ │ │ │ - Name of this probe │ │ │ │ -

state

│ │ │ │ - Socket state value │ │ │ │ +

flags

│ │ │ │ + Socket flags value │ │ │ │ +

protocol

│ │ │ │ + Protocol value │ │ │ │ +

size

│ │ │ │ + Size of message received (in bytes) or error code if success = 0 │ │ │ │

Context

│ │ │ │ The message receiver. │ │ │ │

Description

│ │ │ │ Fires at the conclusion of sending a message on a socket │ │ │ │ via the sock_aio_write function │ │ │ │

Prev Up Next
probe::socket.aio_write Home probe::socket.close
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-socket-aio-write.html │ │ │ │ @@ -1,22 +1,22 @@ │ │ │ │ probe::socket.aio_write
probe::socket.aio_write
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.aio_write — │ │ │ │ Message send via sock_aio_write │ │ │ │ -

Synopsis

socket.aio_write

Values

flags

│ │ │ │ - Socket flags value │ │ │ │ -

protocol

│ │ │ │ - Protocol value │ │ │ │ +

Synopsis

socket.aio_write

Values

state

│ │ │ │ + Socket state value │ │ │ │

type

│ │ │ │ Socket type value │ │ │ │ -

state

│ │ │ │ - Socket state value │ │ │ │

name

│ │ │ │ Name of this probe │ │ │ │ -

family

│ │ │ │ - Protocol family value │ │ │ │ +

protocol

│ │ │ │ + Protocol value │ │ │ │

size

│ │ │ │ Message size in bytes │ │ │ │ +

family

│ │ │ │ + Protocol family value │ │ │ │ +

flags

│ │ │ │ + Socket flags value │ │ │ │

Context

│ │ │ │ The message sender │ │ │ │

Description

│ │ │ │ Fires at the beginning of sending a message on a socket │ │ │ │ via the sock_aio_write function │ │ │ │

Prev Up Next
probe::socket.aio_read.return Home probe::socket.aio_write.return
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-socket-close.html │ │ │ │ @@ -1,19 +1,19 @@ │ │ │ │ probe::socket.close
probe::socket.close
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.close — │ │ │ │ Close a socket │ │ │ │ -

Synopsis

socket.close

Values

name

│ │ │ │ - Name of this probe │ │ │ │ +

Synopsis

socket.close

Values

protocol

│ │ │ │ + Protocol value │ │ │ │ +

flags

│ │ │ │ + Socket flags value │ │ │ │

family

│ │ │ │ Protocol family value │ │ │ │ -

state

│ │ │ │ - Socket state value │ │ │ │ +

name

│ │ │ │ + Name of this probe │ │ │ │

type

│ │ │ │ Socket type value │ │ │ │ -

flags

│ │ │ │ - Socket flags value │ │ │ │ -

protocol

│ │ │ │ - Protocol value │ │ │ │ +

state

│ │ │ │ + Socket state value │ │ │ │

Context

│ │ │ │ The requester (user process or kernel) │ │ │ │

Description

│ │ │ │ Fires at the beginning of closing a socket. │ │ │ │

Prev Up Next
probe::socket.aio_write.return Home probe::socket.close.return
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-socket-create-return.html │ │ │ │ @@ -1,21 +1,21 @@ │ │ │ │ probe::socket.create.return
probe::socket.create.return
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.create.return — │ │ │ │ Return from Creation of a socket │ │ │ │ -

Synopsis

socket.create.return

Values

err

│ │ │ │ +

Synopsis

socket.create.return

Values

requester

│ │ │ │ + Requested by user process or the kernel (1 = kernel, 0 = user) │ │ │ │ +

success

│ │ │ │ + Was socket creation successful? (1 = yes, 0 = no) │ │ │ │ +

type

│ │ │ │ + Socket type value │ │ │ │ +

err

│ │ │ │ Error code if success == 0 │ │ │ │

name

│ │ │ │ Name of this probe │ │ │ │ -

family

│ │ │ │ - Protocol family value │ │ │ │ -

success

│ │ │ │ - Was socket creation successful? (1 = yes, 0 = no) │ │ │ │ -

requester

│ │ │ │ - Requested by user process or the kernel (1 = kernel, 0 = user) │ │ │ │

protocol

│ │ │ │ Protocol value │ │ │ │ -

type

│ │ │ │ - Socket type value │ │ │ │ +

family

│ │ │ │ + Protocol family value │ │ │ │

Context

│ │ │ │ The requester (user process or kernel) │ │ │ │

Description

│ │ │ │ Fires at the conclusion of creating a socket. │ │ │ │

Prev Up Next
probe::socket.create Home probe::socket.read_iter
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-socket-create.html │ │ │ │ @@ -1,17 +1,17 @@ │ │ │ │ probe::socket.create
probe::socket.create
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.create — │ │ │ │ Creation of a socket │ │ │ │ -

Synopsis

socket.create

Values

family

│ │ │ │ - Protocol family value │ │ │ │ +

Synopsis

socket.create

Values

requester

│ │ │ │ + Requested by user process or the kernel (1 = kernel, 0 = user) │ │ │ │

name

│ │ │ │ Name of this probe │ │ │ │ -

requester

│ │ │ │ - Requested by user process or the kernel (1 = kernel, 0 = user) │ │ │ │ -

protocol

│ │ │ │ - Protocol value │ │ │ │

type

│ │ │ │ Socket type value │ │ │ │ +

protocol

│ │ │ │ + Protocol value │ │ │ │ +

family

│ │ │ │ + Protocol family value │ │ │ │

Context

│ │ │ │ The requester (see requester variable) │ │ │ │

Description

│ │ │ │ Fires at the beginning of creating a socket. │ │ │ │

Prev Up Next
probe::socket.close.return Home probe::socket.create.return
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-socket-read-iter-return.html │ │ │ │ @@ -1,24 +1,24 @@ │ │ │ │ probe::socket.read_iter.return
probe::socket.read_iter.return
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.read_iter.return — │ │ │ │ Conclusion of message received via sock_read_iter │ │ │ │ -

Synopsis

socket.read_iter.return

Values

state

│ │ │ │ - Socket state value │ │ │ │ +

Synopsis

socket.read_iter.return

Values

type

│ │ │ │ + Socket type value │ │ │ │

name

│ │ │ │ Name of this probe │ │ │ │ +

state

│ │ │ │ + Socket state value │ │ │ │

success

│ │ │ │ Was receive successful? (1 = yes, 0 = no) │ │ │ │ -

size

│ │ │ │ - Size of message received (in bytes) or error code if success = 0 │ │ │ │ -

family

│ │ │ │ - Protocol family value │ │ │ │

flags

│ │ │ │ Socket flags value │ │ │ │ +

family

│ │ │ │ + Protocol family value │ │ │ │ +

size

│ │ │ │ + Size of message received (in bytes) or error code if success = 0 │ │ │ │

protocol

│ │ │ │ Protocol value │ │ │ │ -

type

│ │ │ │ - Socket type value │ │ │ │

Context

│ │ │ │ The message receiver. │ │ │ │

Description

│ │ │ │ Fires at the conclusion of receiving a message on a socket │ │ │ │ via the sock_read_iter function │ │ │ │

Prev Up Next
probe::socket.read_iter Home probe::socket.readv
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-socket-read-iter.html │ │ │ │ @@ -1,22 +1,22 @@ │ │ │ │ probe::socket.read_iter
probe::socket.read_iter
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.read_iter — │ │ │ │ Receiving message via sock_read_iter │ │ │ │ -

Synopsis

socket.read_iter

Values

type

│ │ │ │ - Socket type value │ │ │ │ -

flags

│ │ │ │ - Socket flags value │ │ │ │ -

protocol

│ │ │ │ +

Synopsis

socket.read_iter

Values

protocol

│ │ │ │ Protocol value │ │ │ │ -

name

│ │ │ │ - Name of this probe │ │ │ │ -

family

│ │ │ │ - Protocol family value │ │ │ │

size

│ │ │ │ Message size in bytes │ │ │ │ +

family

│ │ │ │ + Protocol family value │ │ │ │ +

flags

│ │ │ │ + Socket flags value │ │ │ │

state

│ │ │ │ Socket state value │ │ │ │ +

type

│ │ │ │ + Socket type value │ │ │ │ +

name

│ │ │ │ + Name of this probe │ │ │ │

Context

│ │ │ │ The message sender │ │ │ │

Description

│ │ │ │ Fires at the beginning of receiving a message on a socket │ │ │ │ via the sock_read_iter function │ │ │ │

Prev Up Next
probe::socket.create.return Home probe::socket.read_iter.return
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-socket-readv-return.html │ │ │ │ @@ -1,24 +1,24 @@ │ │ │ │ probe::socket.readv.return
probe::socket.readv.return
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.readv.return — │ │ │ │ Conclusion of receiving a message via sock_readv │ │ │ │ -

Synopsis

socket.readv.return

Values

type

│ │ │ │ - Socket type value │ │ │ │ -

protocol

│ │ │ │ - Protocol value │ │ │ │ -

flags

│ │ │ │ +

Synopsis

socket.readv.return

Values

flags

│ │ │ │ Socket flags value │ │ │ │ -

size

│ │ │ │ - Size of message received (in bytes) or error code if success = 0 │ │ │ │ -

success

│ │ │ │ - Was receive successful? (1 = yes, 0 = no) │ │ │ │

family

│ │ │ │ Protocol family value │ │ │ │ +

size

│ │ │ │ + Size of message received (in bytes) or error code if success = 0 │ │ │ │ +

protocol

│ │ │ │ + Protocol value │ │ │ │ +

type

│ │ │ │ + Socket type value │ │ │ │

name

│ │ │ │ Name of this probe │ │ │ │

state

│ │ │ │ Socket state value │ │ │ │ +

success

│ │ │ │ + Was receive successful? (1 = yes, 0 = no) │ │ │ │

Context

│ │ │ │ The message receiver. │ │ │ │

Description

│ │ │ │ Fires at the conclusion of receiving a message on a socket │ │ │ │ via the sock_readv function │ │ │ │

Prev Up Next
probe::socket.readv Home probe::socket.receive
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-socket-readv.html │ │ │ │ @@ -1,21 +1,21 @@ │ │ │ │ probe::socket.readv
probe::socket.readv
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.readv — │ │ │ │ Receiving a message via sock_readv │ │ │ │ -

Synopsis

socket.readv

Values

name

│ │ │ │ - Name of this probe │ │ │ │ -

family

│ │ │ │ +

Synopsis

socket.readv

Values

family

│ │ │ │ Protocol family value │ │ │ │ -

size

│ │ │ │ - Message size in bytes │ │ │ │ -

state

│ │ │ │ - Socket state value │ │ │ │

flags

│ │ │ │ Socket flags value │ │ │ │

protocol

│ │ │ │ Protocol value │ │ │ │ +

size

│ │ │ │ + Message size in bytes │ │ │ │ +

state

│ │ │ │ + Socket state value │ │ │ │ +

name

│ │ │ │ + Name of this probe │ │ │ │

type

│ │ │ │ Socket type value │ │ │ │

Context

│ │ │ │ The message sender │ │ │ │

Description

│ │ │ │ Fires at the beginning of receiving a message on a socket │ │ │ │ via the sock_readv function │ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-socket-receive.html │ │ │ │ @@ -1,21 +1,21 @@ │ │ │ │ probe::socket.receive

probe::socket.receive
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.receive — │ │ │ │ Message received on a socket. │ │ │ │ -

Synopsis

socket.receive

Values

type

│ │ │ │ - Socket type value │ │ │ │ +

Synopsis

socket.receive

Values

size

│ │ │ │ + Size of message received (in bytes) or error code if success = 0 │ │ │ │

protocol

│ │ │ │ Protocol value │ │ │ │

flags

│ │ │ │ Socket flags value │ │ │ │ -

state

│ │ │ │ - Socket state value │ │ │ │ -

success

│ │ │ │ - Was send successful? (1 = yes, 0 = no) │ │ │ │

family

│ │ │ │ Protocol family value │ │ │ │ -

size

│ │ │ │ - Size of message received (in bytes) or error code if success = 0 │ │ │ │ +

success

│ │ │ │ + Was send successful? (1 = yes, 0 = no) │ │ │ │

name

│ │ │ │ Name of this probe │ │ │ │ +

type

│ │ │ │ + Socket type value │ │ │ │ +

state

│ │ │ │ + Socket state value │ │ │ │

Context

│ │ │ │ The message receiver │ │ │ │

Prev Up Next
probe::socket.readv.return Home probe::socket.recvmsg
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-socket-recvmsg-return.html │ │ │ │ @@ -1,24 +1,24 @@ │ │ │ │ probe::socket.recvmsg.return
probe::socket.recvmsg.return
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.recvmsg.return — │ │ │ │ Return from Message being received on socket │ │ │ │ -

Synopsis

socket.recvmsg.return

Values

type

│ │ │ │ +

Synopsis

socket.recvmsg.return

Values

state

│ │ │ │ + Socket state value │ │ │ │ +

name

│ │ │ │ + Name of this probe │ │ │ │ +

type

│ │ │ │ Socket type value │ │ │ │ +

success

│ │ │ │ + Was receive successful? (1 = yes, 0 = no) │ │ │ │ +

family

│ │ │ │ + Protocol family value │ │ │ │

flags

│ │ │ │ Socket flags value │ │ │ │

protocol

│ │ │ │ Protocol value │ │ │ │ -

name

│ │ │ │ - Name of this probe │ │ │ │

size

│ │ │ │ Size of message received (in bytes) or error code if success = 0 │ │ │ │ -

success

│ │ │ │ - Was receive successful? (1 = yes, 0 = no) │ │ │ │ -

family

│ │ │ │ - Protocol family value │ │ │ │ -

state

│ │ │ │ - Socket state value │ │ │ │

Context

│ │ │ │ The message receiver. │ │ │ │

Description

│ │ │ │ Fires at the conclusion of receiving a message on a socket │ │ │ │ via the sock_recvmsg function. │ │ │ │

Prev Up Next
probe::socket.recvmsg Home probe::socket.send
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-socket-recvmsg.html │ │ │ │┄ Ordering differences only │ │ │ │ @@ -1,21 +1,21 @@ │ │ │ │ probe::socket.recvmsg
probe::socket.recvmsg
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.recvmsg — │ │ │ │ Message being received on socket │ │ │ │

Synopsis

socket.recvmsg

Values

name

│ │ │ │ Name of this probe │ │ │ │ -

size

│ │ │ │ - Message size in bytes │ │ │ │ -

family

│ │ │ │ - Protocol family value │ │ │ │ -

state

│ │ │ │ - Socket state value │ │ │ │

type

│ │ │ │ Socket type value │ │ │ │ +

state

│ │ │ │ + Socket state value │ │ │ │

flags

│ │ │ │ Socket flags value │ │ │ │ +

family

│ │ │ │ + Protocol family value │ │ │ │ +

size

│ │ │ │ + Message size in bytes │ │ │ │

protocol

│ │ │ │ Protocol value │ │ │ │

Context

│ │ │ │ The message receiver. │ │ │ │

Description

│ │ │ │ Fires at the beginning of receiving a message on a socket │ │ │ │ via the sock_recvmsg function │ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-socket-send.html │ │ │ │ @@ -1,21 +1,21 @@ │ │ │ │ probe::socket.send

probe::socket.send
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.send — │ │ │ │ Message sent on a socket. │ │ │ │ -

Synopsis

socket.send

Values

size

│ │ │ │ - Size of message sent (in bytes) or error code if success = 0 │ │ │ │ -

success

│ │ │ │ +

Synopsis

socket.send

Values

success

│ │ │ │ Was send successful? (1 = yes, 0 = no) │ │ │ │ -

family

│ │ │ │ - Protocol family value │ │ │ │ -

name

│ │ │ │ - Name of this probe │ │ │ │

state

│ │ │ │ Socket state value │ │ │ │ +

name

│ │ │ │ + Name of this probe │ │ │ │ +

type

│ │ │ │ + Socket type value │ │ │ │

protocol

│ │ │ │ Protocol value │ │ │ │ +

size

│ │ │ │ + Size of message sent (in bytes) or error code if success = 0 │ │ │ │ +

family

│ │ │ │ + Protocol family value │ │ │ │

flags

│ │ │ │ Socket flags value │ │ │ │ -

type

│ │ │ │ - Socket type value │ │ │ │

Context

│ │ │ │ The message sender │ │ │ │

Prev Up Next
probe::socket.recvmsg.return Home probe::socket.sendmsg
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-socket-sendmsg-return.html │ │ │ │ @@ -1,24 +1,24 @@ │ │ │ │ probe::socket.sendmsg.return
probe::socket.sendmsg.return
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.sendmsg.return — │ │ │ │ Return from socket.sendmsg. │ │ │ │ -

Synopsis

socket.sendmsg.return

Values

protocol

│ │ │ │ +

Synopsis

socket.sendmsg.return

Values

size

│ │ │ │ + Size of message sent (in bytes) or error code if success = 0 │ │ │ │ +

protocol

│ │ │ │ Protocol value │ │ │ │

flags

│ │ │ │ Socket flags value │ │ │ │ -

type

│ │ │ │ - Socket type value │ │ │ │ -

state

│ │ │ │ - Socket state value │ │ │ │ -

success

│ │ │ │ - Was send successful? (1 = yes, 0 = no) │ │ │ │ -

size

│ │ │ │ - Size of message sent (in bytes) or error code if success = 0 │ │ │ │

family

│ │ │ │ Protocol family value │ │ │ │ +

success

│ │ │ │ + Was send successful? (1 = yes, 0 = no) │ │ │ │

name

│ │ │ │ Name of this probe │ │ │ │ +

type

│ │ │ │ + Socket type value │ │ │ │ +

state

│ │ │ │ + Socket state value │ │ │ │

Context

│ │ │ │ The message sender. │ │ │ │

Description

│ │ │ │ Fires at the conclusion of sending a message on a socket │ │ │ │ via the sock_sendmsg function │ │ │ │

Prev Up Next
probe::socket.sendmsg Home probe::socket.write_iter
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-socket-sendmsg.html │ │ │ │ @@ -1,22 +1,22 @@ │ │ │ │ probe::socket.sendmsg
probe::socket.sendmsg
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.sendmsg — │ │ │ │ Message is currently being sent on a socket. │ │ │ │ -

Synopsis

socket.sendmsg

Values

state

│ │ │ │ +

Synopsis

socket.sendmsg

Values

name

│ │ │ │ + Name of this probe │ │ │ │ +

type

│ │ │ │ + Socket type value │ │ │ │ +

state

│ │ │ │ Socket state value │ │ │ │ -

size

│ │ │ │ - Message size in bytes │ │ │ │ +

flags

│ │ │ │ + Socket flags value │ │ │ │

family

│ │ │ │ Protocol family value │ │ │ │ -

name

│ │ │ │ - Name of this probe │ │ │ │ +

size

│ │ │ │ + Message size in bytes │ │ │ │

protocol

│ │ │ │ Protocol value │ │ │ │ -

flags

│ │ │ │ - Socket flags value │ │ │ │ -

type

│ │ │ │ - Socket type value │ │ │ │

Context

│ │ │ │ The message sender │ │ │ │

Description

│ │ │ │ Fires at the beginning of sending a message on a socket │ │ │ │ via the sock_sendmsg function │ │ │ │

Prev Up Next
probe::socket.send Home probe::socket.sendmsg.return
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-socket-write-iter-return.html │ │ │ │ @@ -1,24 +1,24 @@ │ │ │ │ probe::socket.write_iter.return
probe::socket.write_iter.return
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.write_iter.return — │ │ │ │ Conclusion of message send via sock_write_iter │ │ │ │ -

Synopsis

socket.write_iter.return

Values

state

│ │ │ │ +

Synopsis

socket.write_iter.return

Values

success

│ │ │ │ + Was receive successful? (1 = yes, 0 = no) │ │ │ │ +

state

│ │ │ │ Socket state value │ │ │ │ +

type

│ │ │ │ + Socket type value │ │ │ │

name

│ │ │ │ Name of this probe │ │ │ │ -

family

│ │ │ │ - Protocol family value │ │ │ │ -

success

│ │ │ │ - Was receive successful? (1 = yes, 0 = no) │ │ │ │ +

protocol

│ │ │ │ + Protocol value │ │ │ │

size

│ │ │ │ Size of message received (in bytes) or error code if success = 0 │ │ │ │ +

family

│ │ │ │ + Protocol family value │ │ │ │

flags

│ │ │ │ Socket flags value │ │ │ │ -

protocol

│ │ │ │ - Protocol value │ │ │ │ -

type

│ │ │ │ - Socket type value │ │ │ │

Context

│ │ │ │ The message receiver. │ │ │ │

Description

│ │ │ │ Fires at the conclusion of sending a message on a socket │ │ │ │ via the sock_write_iter function │ │ │ │

Prev Up Next
probe::socket.write_iter Home probe::socket.writev
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-socket-write-iter.html │ │ │ │┄ Ordering differences only │ │ │ │ @@ -1,21 +1,21 @@ │ │ │ │ probe::socket.write_iter
probe::socket.write_iter
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.write_iter — │ │ │ │ Message send via sock_write_iter │ │ │ │

Synopsis

socket.write_iter

Values

family

│ │ │ │ Protocol family value │ │ │ │ +

flags

│ │ │ │ + Socket flags value │ │ │ │ +

protocol

│ │ │ │ + Protocol value │ │ │ │

size

│ │ │ │ Message size in bytes │ │ │ │ -

name

│ │ │ │ - Name of this probe │ │ │ │

state

│ │ │ │ Socket state value │ │ │ │ -

protocol

│ │ │ │ - Protocol value │ │ │ │ -

flags

│ │ │ │ - Socket flags value │ │ │ │ +

name

│ │ │ │ + Name of this probe │ │ │ │

type

│ │ │ │ Socket type value │ │ │ │

Context

│ │ │ │ The message sender │ │ │ │

Description

│ │ │ │ Fires at the beginning of sending a message on a socket │ │ │ │ via the sock_write_iter function │ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-socket-writev-return.html │ │ │ │┄ Ordering differences only │ │ │ │ @@ -1,24 +1,24 @@ │ │ │ │ probe::socket.writev.return

probe::socket.writev.return
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.writev.return — │ │ │ │ Conclusion of message sent via socket_writev │ │ │ │

Synopsis

socket.writev.return

Values

protocol

│ │ │ │ Protocol value │ │ │ │ +

size

│ │ │ │ + Size of message sent (in bytes) or error code if success = 0 │ │ │ │ +

family

│ │ │ │ + Protocol family value │ │ │ │

flags

│ │ │ │ Socket flags value │ │ │ │ -

type

│ │ │ │ - Socket type value │ │ │ │

success

│ │ │ │ Was send successful? (1 = yes, 0 = no) │ │ │ │ -

family

│ │ │ │ - Protocol family value │ │ │ │ -

size

│ │ │ │ - Size of message sent (in bytes) or error code if success = 0 │ │ │ │ -

name

│ │ │ │ - Name of this probe │ │ │ │

state

│ │ │ │ Socket state value │ │ │ │ +

name

│ │ │ │ + Name of this probe │ │ │ │ +

type

│ │ │ │ + Socket type value │ │ │ │

Context

│ │ │ │ The message receiver. │ │ │ │

Description

│ │ │ │ Fires at the conclusion of sending a message on a socket │ │ │ │ via the sock_writev function │ │ │ │

Prev Up Next
probe::socket.writev Home Chapter 15. SNMP Information Tapset
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-socket-writev.html │ │ │ │ @@ -1,21 +1,21 @@ │ │ │ │ probe::socket.writev
probe::socket.writev
Prev Chapter 14. Socket Tapset Next

Name

probe::socket.writev — │ │ │ │ Message sent via socket_writev │ │ │ │ -

Synopsis

socket.writev

Values

type

│ │ │ │ - Socket type value │ │ │ │ -

protocol

│ │ │ │ - Protocol value │ │ │ │ -

flags

│ │ │ │ +

Synopsis

socket.writev

Values

flags

│ │ │ │ Socket flags value │ │ │ │ -

size

│ │ │ │ - Message size in bytes │ │ │ │

family

│ │ │ │ Protocol family value │ │ │ │ +

size

│ │ │ │ + Message size in bytes │ │ │ │ +

protocol

│ │ │ │ + Protocol value │ │ │ │

name

│ │ │ │ Name of this probe │ │ │ │ +

type

│ │ │ │ + Socket type value │ │ │ │

state

│ │ │ │ Socket state value │ │ │ │

Context

│ │ │ │ The message sender │ │ │ │

Description

│ │ │ │ Fires at the beginning of sending a message on a socket │ │ │ │ via the sock_writev function │ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-softirq-entry.html │ │ │ │┄ Ordering differences only │ │ │ │ @@ -1,11 +1,11 @@ │ │ │ │ probe::softirq.entry

probe::softirq.entry
Prev Chapter 12. Interrupt Request (IRQ) Tapset Next

Name

probe::softirq.entry — │ │ │ │ Execution of handler for a pending softirq starting │ │ │ │

Synopsis

softirq.entry

Values

action

│ │ │ │ pointer to softirq handler just about to execute │ │ │ │ -

vec

│ │ │ │ - softirq_action vector │ │ │ │ -

vec_nr

│ │ │ │ - softirq vector number │ │ │ │

h

│ │ │ │ struct softirq_action* for current pending softirq │ │ │ │ +

vec_nr

│ │ │ │ + softirq vector number │ │ │ │ +

vec

│ │ │ │ + softirq_action vector │ │ │ │

Prev Up Next
probe::irq_handler.exit Home probe::softirq.exit
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-softirq-exit.html │ │ │ │ @@ -1,11 +1,11 @@ │ │ │ │ probe::softirq.exit
probe::softirq.exit
Prev Chapter 12. Interrupt Request (IRQ) Tapset Next

Name

probe::softirq.exit — │ │ │ │ Execution of handler for a pending softirq completed │ │ │ │ -

Synopsis

softirq.exit

Values

h

│ │ │ │ - struct softirq_action* for just executed softirq │ │ │ │ -

vec_nr

│ │ │ │ +

Synopsis

softirq.exit

Values

vec_nr

│ │ │ │ softirq vector number │ │ │ │ -

vec

│ │ │ │ - softirq_action vector │ │ │ │

action

│ │ │ │ pointer to softirq handler that just finished execution │ │ │ │ +

h

│ │ │ │ + struct softirq_action* for just executed softirq │ │ │ │ +

vec

│ │ │ │ + softirq_action vector │ │ │ │

Prev Up Next
probe::softirq.entry Home probe::workqueue.create
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-stap-cache-add-mod.html │ │ │ │ @@ -1,10 +1,10 @@ │ │ │ │ probe::stap.cache_add_mod
probe::stap.cache_add_mod
Prev Chapter 30. SystemTap Translator Tapset Next

Name

probe::stap.cache_add_mod — │ │ │ │ Adding kernel instrumentation module to cache │ │ │ │ -

Synopsis

stap.cache_add_mod

Values

source_path

│ │ │ │ - the path the .ko file is coming from (incl filename) │ │ │ │ -

dest_path

│ │ │ │ +

Synopsis

stap.cache_add_mod

Values

dest_path

│ │ │ │ the path the .ko file is going to (incl filename) │ │ │ │ +

source_path

│ │ │ │ + the path the .ko file is coming from (incl filename) │ │ │ │

Description

│ │ │ │ Fires just before the file is actually moved. Note: if moving fails, │ │ │ │ cache_add_src and cache_add_nss will not fire. │ │ │ │

Prev Up Next
Chapter 30. SystemTap Translator Tapset Home probe::stap.cache_add_nss
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-stap-cache-add-nss.html │ │ │ │ @@ -1,11 +1,11 @@ │ │ │ │ probe::stap.cache_add_nss
probe::stap.cache_add_nss
Prev Chapter 30. SystemTap Translator Tapset Next

Name

probe::stap.cache_add_nss — │ │ │ │ Add NSS (Network Security Services) information to cache │ │ │ │ -

Synopsis

stap.cache_add_nss

Values

source_path

│ │ │ │ +

Synopsis

stap.cache_add_nss

Values

dest_path

│ │ │ │ the path the .sgn file is coming from (incl filename) │ │ │ │ -

dest_path

│ │ │ │ +

source_path

│ │ │ │ the path the .sgn file is coming from (incl filename) │ │ │ │

Description

│ │ │ │ Fires just before the file is actually moved. Note: stap must compiled │ │ │ │ with NSS support; if moving the kernel module fails, this probe will │ │ │ │ not fire. │ │ │ │

Prev Up Next
probe::stap.cache_add_mod Home probe::stap.cache_add_src
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-stap-system-spawn.html │ │ │ │ @@ -1,9 +1,9 @@ │ │ │ │ probe::stap.system.spawn
probe::stap.system.spawn
Prev Chapter 30. SystemTap Translator Tapset Next

Name

probe::stap.system.spawn — │ │ │ │ stap spawned new process │ │ │ │ -

Synopsis

stap.system.spawn

Values

ret

│ │ │ │ - the return value from posix_spawn │ │ │ │ -

pid

│ │ │ │ +

Synopsis

stap.system.spawn

Values

pid

│ │ │ │ the pid of the spawned process │ │ │ │ +

ret

│ │ │ │ + the return value from posix_spawn │ │ │ │

Description

│ │ │ │ Fires just after the call to posix_spawn. │ │ │ │

Prev Up Next
probe::stap.system.return Home probe::stapio.receive_control_message
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-clnt-bind-new-program.html │ │ │ │ @@ -1,17 +1,17 @@ │ │ │ │ probe::sunrpc.clnt.bind_new_program
probe::sunrpc.clnt.bind_new_program
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.clnt.bind_new_program — │ │ │ │ Bind a new RPC program to an existing client │ │ │ │ -

Synopsis

sunrpc.clnt.bind_new_program

Values

old_prog

│ │ │ │ - the number of old RPC program │ │ │ │ -

servername

│ │ │ │ +

Synopsis

sunrpc.clnt.bind_new_program

Values

servername

│ │ │ │ the server machine name │ │ │ │ -

old_progname

│ │ │ │ - the name of old RPC program │ │ │ │ -

progname

│ │ │ │ - the name of new RPC program │ │ │ │

old_vers

│ │ │ │ the version of old RPC program │ │ │ │ +

old_prog

│ │ │ │ + the number of old RPC program │ │ │ │ +

progname

│ │ │ │ + the name of new RPC program │ │ │ │ +

old_progname

│ │ │ │ + the name of old RPC program │ │ │ │

prog

│ │ │ │ the number of new RPC program │ │ │ │

vers

│ │ │ │ the version of new RPC program │ │ │ │

Prev Up Next
probe::netfilter.ip.pre_routing Home probe::sunrpc.clnt.call_async
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-clnt-call-async.html │ │ │ │ @@ -1,25 +1,25 @@ │ │ │ │ probe::sunrpc.clnt.call_async
probe::sunrpc.clnt.call_async
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.clnt.call_async — │ │ │ │ Make an asynchronous RPC call │ │ │ │ -

Synopsis

sunrpc.clnt.call_async

Values

progname

│ │ │ │ - the RPC program name │ │ │ │ +

Synopsis

sunrpc.clnt.call_async

Values

flags

│ │ │ │ + flags │ │ │ │

vers

│ │ │ │ the RPC program version number │ │ │ │ -

xid

│ │ │ │ - current transmission id │ │ │ │ +

prot

│ │ │ │ + the IP protocol number │ │ │ │

port

│ │ │ │ the port number │ │ │ │ -

prog

│ │ │ │ - the RPC program number │ │ │ │ -

flags

│ │ │ │ - flags │ │ │ │ -

dead

│ │ │ │ - whether this client is abandoned │ │ │ │ -

procname

│ │ │ │ - the procedure name in this RPC call │ │ │ │

servername

│ │ │ │ the server machine name │ │ │ │ -

prot

│ │ │ │ - the IP protocol number │ │ │ │

proc

│ │ │ │ the procedure number in this RPC call │ │ │ │ +

dead

│ │ │ │ + whether this client is abandoned │ │ │ │ +

procname

│ │ │ │ + the procedure name in this RPC call │ │ │ │ +

progname

│ │ │ │ + the RPC program name │ │ │ │ +

xid

│ │ │ │ + current transmission id │ │ │ │ +

prog

│ │ │ │ + the RPC program number │ │ │ │

Prev Up Next
probe::sunrpc.clnt.bind_new_program Home probe::sunrpc.clnt.call_sync
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-clnt-call-sync.html │ │ │ │ @@ -1,25 +1,25 @@ │ │ │ │ probe::sunrpc.clnt.call_sync
probe::sunrpc.clnt.call_sync
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.clnt.call_sync — │ │ │ │ Make a synchronous RPC call │ │ │ │ -

Synopsis

sunrpc.clnt.call_sync

Values

servername

│ │ │ │ - the server machine name │ │ │ │ +

Synopsis

sunrpc.clnt.call_sync

Values

dead

│ │ │ │ + whether this client is abandoned │ │ │ │

procname

│ │ │ │ the procedure name in this RPC call │ │ │ │ -

dead

│ │ │ │ - whether this client is abandoned │ │ │ │

proc

│ │ │ │ the procedure number in this RPC call │ │ │ │ -

prot

│ │ │ │ - the IP protocol number │ │ │ │ -

progname

│ │ │ │ - the RPC program name │ │ │ │

port

│ │ │ │ the port number │ │ │ │ +

servername

│ │ │ │ + the server machine name │ │ │ │ +

prog

│ │ │ │ + the RPC program number │ │ │ │

xid

│ │ │ │ current transmission id │ │ │ │ -

vers

│ │ │ │ - the RPC program version number │ │ │ │ +

progname

│ │ │ │ + the RPC program name │ │ │ │

flags

│ │ │ │ flags │ │ │ │ -

prog

│ │ │ │ - the RPC program number │ │ │ │ +

prot

│ │ │ │ + the IP protocol number │ │ │ │ +

vers

│ │ │ │ + the RPC program version number │ │ │ │

Prev Up Next
probe::sunrpc.clnt.call_async Home probe::sunrpc.clnt.clone_client
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-clnt-clone-client.html │ │ │ │ @@ -1,17 +1,17 @@ │ │ │ │ probe::sunrpc.clnt.clone_client
probe::sunrpc.clnt.clone_client
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.clnt.clone_client — │ │ │ │ Clone an RPC client structure │ │ │ │ -

Synopsis

sunrpc.clnt.clone_client

Values

servername

│ │ │ │ - the server machine name │ │ │ │ +

Synopsis

sunrpc.clnt.clone_client

Values

prot

│ │ │ │ + the IP protocol number │ │ │ │ +

vers

│ │ │ │ + the RPC program version number │ │ │ │ +

prog

│ │ │ │ + the RPC program number │ │ │ │

progname

│ │ │ │ the RPC program name │ │ │ │ +

servername

│ │ │ │ + the server machine name │ │ │ │

authflavor

│ │ │ │ the authentication flavor │ │ │ │ -

prot

│ │ │ │ - the IP protocol number │ │ │ │

port

│ │ │ │ the port number │ │ │ │ -

vers

│ │ │ │ - the RPC program version number │ │ │ │ -

prog

│ │ │ │ - the RPC program number │ │ │ │

Prev Up Next
probe::sunrpc.clnt.call_sync Home probe::sunrpc.clnt.create_client
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-clnt-create-client.html │ │ │ │ @@ -1,17 +1,17 @@ │ │ │ │ probe::sunrpc.clnt.create_client
probe::sunrpc.clnt.create_client
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.clnt.create_client — │ │ │ │ Create an RPC client │ │ │ │ -

Synopsis

sunrpc.clnt.create_client

Values

progname

│ │ │ │ - the RPC program name │ │ │ │ +

Synopsis

sunrpc.clnt.create_client

Values

port

│ │ │ │ + the port number │ │ │ │

authflavor

│ │ │ │ the authentication flavor │ │ │ │

servername

│ │ │ │ the server machine name │ │ │ │

prog

│ │ │ │ the RPC program number │ │ │ │

vers

│ │ │ │ the RPC program version number │ │ │ │

prot

│ │ │ │ the IP protocol number │ │ │ │ -

port

│ │ │ │ - the port number │ │ │ │ +

progname

│ │ │ │ + the RPC program name │ │ │ │

Prev Up Next
probe::sunrpc.clnt.clone_client Home probe::sunrpc.clnt.restart_call
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-clnt-restart-call.html │ │ │ │ @@ -1,17 +1,17 @@ │ │ │ │ probe::sunrpc.clnt.restart_call
probe::sunrpc.clnt.restart_call
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.clnt.restart_call — │ │ │ │ Restart an asynchronous RPC call │ │ │ │ -

Synopsis

sunrpc.clnt.restart_call

Values

servername

│ │ │ │ +

Synopsis

sunrpc.clnt.restart_call

Values

tk_runstate

│ │ │ │ + the task run status │ │ │ │ +

tk_pid

│ │ │ │ + the debugging aid of task │ │ │ │ +

servername

│ │ │ │ the server machine name │ │ │ │

tk_flags

│ │ │ │ the task flags │ │ │ │

tk_priority

│ │ │ │ the task priority │ │ │ │ -

tk_runstate

│ │ │ │ - the task run status │ │ │ │ -

prog

│ │ │ │ - the RPC program number │ │ │ │

xid

│ │ │ │ the transmission id │ │ │ │ -

tk_pid

│ │ │ │ - the debugging aid of task │ │ │ │ +

prog

│ │ │ │ + the RPC program number │ │ │ │

Prev Up Next
probe::sunrpc.clnt.create_client Home probe::sunrpc.clnt.shutdown_client
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-clnt-shutdown-client.html │ │ │ │ @@ -1,39 +1,39 @@ │ │ │ │ probe::sunrpc.clnt.shutdown_client
probe::sunrpc.clnt.shutdown_client
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.clnt.shutdown_client — │ │ │ │ Shutdown an RPC client │ │ │ │ -

Synopsis

sunrpc.clnt.shutdown_client

Values

prog

│ │ │ │ - the RPC program number │ │ │ │ -

om_execute

│ │ │ │ - the RPC execution jiffies │ │ │ │ -

vers

│ │ │ │ - the RPC program version number │ │ │ │ -

port

│ │ │ │ - the port number │ │ │ │ -

om_queue

│ │ │ │ - the jiffies queued for xmit │ │ │ │ -

progname

│ │ │ │ - the RPC program name │ │ │ │ -

om_bytes_recv

│ │ │ │ - the count of bytes in │ │ │ │ +

Synopsis

sunrpc.clnt.shutdown_client

Values

clones

│ │ │ │ + the number of clones │ │ │ │

om_ops

│ │ │ │ the count of operations │ │ │ │ -

om_ntrans

│ │ │ │ - the count of RPC transmissions │ │ │ │ -

netreconn

│ │ │ │ - the count of reconnections │ │ │ │ +

authflavor

│ │ │ │ + the authentication flavor │ │ │ │ +

prot

│ │ │ │ + the IP protocol number │ │ │ │ +

om_bytes_recv

│ │ │ │ + the count of bytes in │ │ │ │

tasks

│ │ │ │ the number of references │ │ │ │ +

vers

│ │ │ │ + the RPC program version number │ │ │ │

rpccnt

│ │ │ │ the count of RPC calls │ │ │ │ -

prot

│ │ │ │ - the IP protocol number │ │ │ │ +

om_queue

│ │ │ │ + the jiffies queued for xmit │ │ │ │

om_rtt

│ │ │ │ the RPC RTT jiffies │ │ │ │ -

authflavor

│ │ │ │ - the authentication flavor │ │ │ │ -

clones

│ │ │ │ - the number of clones │ │ │ │ +

netreconn

│ │ │ │ + the count of reconnections │ │ │ │

om_bytes_sent

│ │ │ │ the count of bytes out │ │ │ │

servername

│ │ │ │ the server machine name │ │ │ │ +

port

│ │ │ │ + the port number │ │ │ │ +

prog

│ │ │ │ + the RPC program number │ │ │ │ +

om_execute

│ │ │ │ + the RPC execution jiffies │ │ │ │ +

om_ntrans

│ │ │ │ + the count of RPC transmissions │ │ │ │ +

progname

│ │ │ │ + the RPC program name │ │ │ │

Prev Up Next
probe::sunrpc.clnt.restart_call Home probe::sunrpc.sched.delay
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-sched-delay.html │ │ │ │┄ Ordering differences only │ │ │ │ @@ -1,17 +1,17 @@ │ │ │ │ probe::sunrpc.sched.delay
probe::sunrpc.sched.delay
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.sched.delay — │ │ │ │ Delay an RPC task │ │ │ │

Synopsis

sunrpc.sched.delay

Values

delay

│ │ │ │ the time delayed │ │ │ │ +

prot

│ │ │ │ + the IP protocol in the RPC call │ │ │ │

vers

│ │ │ │ the program version in the RPC call │ │ │ │ -

xid

│ │ │ │ - the transmission id in the RPC call │ │ │ │

tk_pid

│ │ │ │ the debugging id of the task │ │ │ │ -

prog

│ │ │ │ - the program number in the RPC call │ │ │ │ -

prot

│ │ │ │ - the IP protocol in the RPC call │ │ │ │

tk_flags

│ │ │ │ the flags of the task │ │ │ │ +

prog

│ │ │ │ + the program number in the RPC call │ │ │ │ +

xid

│ │ │ │ + the transmission id in the RPC call │ │ │ │

Prev Up Next
probe::sunrpc.clnt.shutdown_client Home probe::sunrpc.sched.execute
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-sched-execute.html │ │ │ │ @@ -1,15 +1,15 @@ │ │ │ │ probe::sunrpc.sched.execute
probe::sunrpc.sched.execute
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.sched.execute — │ │ │ │ Execute the RPC `scheduler' │ │ │ │ -

Synopsis

sunrpc.sched.execute

Values

tk_flags

│ │ │ │ +

Synopsis

sunrpc.sched.execute

Values

tk_pid

│ │ │ │ + the debugging id of the task │ │ │ │ +

tk_flags

│ │ │ │ the flags of the task │ │ │ │ -

prot

│ │ │ │ - the IP protocol in the RPC call │ │ │ │ +

xid

│ │ │ │ + the transmission id in the RPC call │ │ │ │

prog

│ │ │ │ the program number in the RPC call │ │ │ │ -

tk_pid

│ │ │ │ - the debugging id of the task │ │ │ │ +

prot

│ │ │ │ + the IP protocol in the RPC call │ │ │ │

vers

│ │ │ │ the program version in the RPC call │ │ │ │ -

xid

│ │ │ │ - the transmission id in the RPC call │ │ │ │

Prev Up Next
probe::sunrpc.sched.delay Home probe::sunrpc.sched.new_task
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-sched-new-task.html │ │ │ │ @@ -1,13 +1,13 @@ │ │ │ │ probe::sunrpc.sched.new_task
probe::sunrpc.sched.new_task
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.sched.new_task — │ │ │ │ Create new task for the specified client │ │ │ │ -

Synopsis

sunrpc.sched.new_task

Values

tk_flags

│ │ │ │ - the flags of the task │ │ │ │ +

Synopsis

sunrpc.sched.new_task

Values

vers

│ │ │ │ + the program version in the RPC call │ │ │ │

prot

│ │ │ │ the IP protocol in the RPC call │ │ │ │

prog

│ │ │ │ the program number in the RPC call │ │ │ │

xid

│ │ │ │ the transmission id in the RPC call │ │ │ │ -

vers

│ │ │ │ - the program version in the RPC call │ │ │ │ +

tk_flags

│ │ │ │ + the flags of the task │ │ │ │

Prev Up Next
probe::sunrpc.sched.execute Home probe::sunrpc.sched.release_task
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-sched-release-task.html │ │ │ │┄ Ordering differences only │ │ │ │ @@ -1,16 +1,16 @@ │ │ │ │ probe::sunrpc.sched.release_task
probe::sunrpc.sched.release_task
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.sched.release_task — │ │ │ │ Release all resources associated with a task │ │ │ │

Synopsis

sunrpc.sched.release_task

Values

prot

│ │ │ │ the IP protocol in the RPC call │ │ │ │ -

tk_flags

│ │ │ │ - the flags of the task │ │ │ │

vers

│ │ │ │ the program version in the RPC call │ │ │ │

xid

│ │ │ │ the transmission id in the RPC call │ │ │ │

prog

│ │ │ │ the program number in the RPC call │ │ │ │ +

tk_flags

│ │ │ │ + the flags of the task │ │ │ │

Description

│ │ │ │ rpc_release_task function might not be found for a particular kernel. │ │ │ │ So, if we can't find it, just return '-1' for everything. │ │ │ │

Prev Up Next
probe::sunrpc.sched.new_task Home probe::sunrpc.svc.create
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-svc-create.html │ │ │ │ @@ -1,11 +1,11 @@ │ │ │ │ probe::sunrpc.svc.create
probe::sunrpc.svc.create
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.svc.create — │ │ │ │ Create an RPC service │ │ │ │ -

Synopsis

sunrpc.svc.create

Values

pg_nvers

│ │ │ │ +

Synopsis

sunrpc.svc.create

Values

progname

│ │ │ │ + the name of the program │ │ │ │ +

pg_nvers

│ │ │ │ the number of supported versions │ │ │ │

bufsize

│ │ │ │ the buffer size │ │ │ │ -

progname

│ │ │ │ - the name of the program │ │ │ │

prog

│ │ │ │ the number of the program │ │ │ │

Prev Up Next
probe::sunrpc.sched.release_task Home probe::sunrpc.svc.destroy
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-svc-destroy.html │ │ │ │ @@ -1,21 +1,21 @@ │ │ │ │ probe::sunrpc.svc.destroy
probe::sunrpc.svc.destroy
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.svc.destroy — │ │ │ │ Destroy an RPC service │ │ │ │ -

Synopsis

sunrpc.svc.destroy

Values

rpccnt

│ │ │ │ - the count of valid RPC requests │ │ │ │ -

sv_name

│ │ │ │ +

Synopsis

sunrpc.svc.destroy

Values

sv_name

│ │ │ │ the service name │ │ │ │ -

sv_prog

│ │ │ │ - the number of the program │ │ │ │ -

sv_nrthreads

│ │ │ │ - the number of concurrent threads │ │ │ │

rpcbadauth

│ │ │ │ the count of requests drooped for authentication failure │ │ │ │ +

netcnt

│ │ │ │ + the count of received RPC requests │ │ │ │ +

rpccnt

│ │ │ │ + the count of valid RPC requests │ │ │ │ +

sv_nrthreads

│ │ │ │ + the number of concurrent threads │ │ │ │

sv_progname

│ │ │ │ the name of the program │ │ │ │

nettcpconn

│ │ │ │ the count of accepted TCP connections │ │ │ │ +

sv_prog

│ │ │ │ + the number of the program │ │ │ │

rpcbadfmt

│ │ │ │ the count of requests dropped for bad formats │ │ │ │ -

netcnt

│ │ │ │ - the count of received RPC requests │ │ │ │

Prev Up Next
probe::sunrpc.svc.create Home probe::sunrpc.svc.drop
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-svc-drop.html │ │ │ │ @@ -1,17 +1,17 @@ │ │ │ │ probe::sunrpc.svc.drop
probe::sunrpc.svc.drop
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.svc.drop — │ │ │ │ Drop RPC request │ │ │ │ -

Synopsis

sunrpc.svc.drop

Values

rq_prot

│ │ │ │ - the IP protocol of the reqeust │ │ │ │ +

Synopsis

sunrpc.svc.drop

Values

rq_vers

│ │ │ │ + the program version in the request │ │ │ │

sv_name

│ │ │ │ the service name │ │ │ │ -

rq_xid

│ │ │ │ - the transmission id in the request │ │ │ │ +

peer_ip

│ │ │ │ + the peer address where the request is from │ │ │ │

rq_prog

│ │ │ │ the program number in the request │ │ │ │ +

rq_xid

│ │ │ │ + the transmission id in the request │ │ │ │ +

rq_prot

│ │ │ │ + the IP protocol of the reqeust │ │ │ │

rq_proc

│ │ │ │ the procedure number in the request │ │ │ │ -

peer_ip

│ │ │ │ - the peer address where the request is from │ │ │ │ -

rq_vers

│ │ │ │ - the program version in the request │ │ │ │

Prev Up Next
probe::sunrpc.svc.destroy Home probe::sunrpc.svc.process
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-svc-process.html │ │ │ │ @@ -1,21 +1,21 @@ │ │ │ │ probe::sunrpc.svc.process
probe::sunrpc.svc.process
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.svc.process — │ │ │ │ Process an RPC request │ │ │ │ -

Synopsis

sunrpc.svc.process

Values

sv_nrthreads

│ │ │ │ - the number of concurrent threads │ │ │ │ -

sv_name

│ │ │ │ - the service name │ │ │ │ -

sv_prog

│ │ │ │ - the number of the program │ │ │ │ -

rq_prot

│ │ │ │ +

Synopsis

sunrpc.svc.process

Values

rq_prot

│ │ │ │ the IP protocol of the reqeust │ │ │ │

rq_proc

│ │ │ │ the procedure number in the request │ │ │ │ +

sv_prog

│ │ │ │ + the number of the program │ │ │ │

rq_xid

│ │ │ │ the transmission id in the request │ │ │ │ -

rq_prog

│ │ │ │ - the program number in the request │ │ │ │

rq_vers

│ │ │ │ the program version in the request │ │ │ │

peer_ip

│ │ │ │ the peer address where the request is from │ │ │ │ +

rq_prog

│ │ │ │ + the program number in the request │ │ │ │ +

sv_nrthreads

│ │ │ │ + the number of concurrent threads │ │ │ │ +

sv_name

│ │ │ │ + the service name │ │ │ │

Prev Up Next
probe::sunrpc.svc.drop Home probe::sunrpc.svc.recv
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-svc-recv.html │ │ │ │ @@ -1,11 +1,11 @@ │ │ │ │ probe::sunrpc.svc.recv
probe::sunrpc.svc.recv
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.svc.recv — │ │ │ │ Listen for the next RPC request on any socket │ │ │ │ -

Synopsis

sunrpc.svc.recv

Values

timeout

│ │ │ │ - the timeout of waiting for data │ │ │ │ -

sv_prog

│ │ │ │ - the number of the program │ │ │ │ -

sv_name

│ │ │ │ +

Synopsis

sunrpc.svc.recv

Values

sv_name

│ │ │ │ the service name │ │ │ │ +

timeout

│ │ │ │ + the timeout of waiting for data │ │ │ │

sv_nrthreads

│ │ │ │ the number of concurrent threads │ │ │ │ +

sv_prog

│ │ │ │ + the number of the program │ │ │ │

Prev Up Next
probe::sunrpc.svc.process Home probe::sunrpc.svc.register
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-svc-register.html │ │ │ │ @@ -1,15 +1,15 @@ │ │ │ │ probe::sunrpc.svc.register
probe::sunrpc.svc.register
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.svc.register — │ │ │ │ Register an RPC service with the local portmapper │ │ │ │ -

Synopsis

sunrpc.svc.register

Values

prot

│ │ │ │ - the IP protocol number │ │ │ │ -

sv_name

│ │ │ │ - the service name │ │ │ │ -

prog

│ │ │ │ +

Synopsis

sunrpc.svc.register

Values

prog

│ │ │ │ the number of the program │ │ │ │ -

port

│ │ │ │ - the port number │ │ │ │

progname

│ │ │ │ the name of the program │ │ │ │ +

port

│ │ │ │ + the port number │ │ │ │ +

sv_name

│ │ │ │ + the service name │ │ │ │ +

prot

│ │ │ │ + the IP protocol number │ │ │ │

Description

│ │ │ │ If proto and port are both 0, then unregister a service. │ │ │ │

Prev Up Next
probe::sunrpc.svc.recv Home probe::sunrpc.svc.send
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-sunrpc-svc-send.html │ │ │ │ @@ -1,17 +1,17 @@ │ │ │ │ probe::sunrpc.svc.send
probe::sunrpc.svc.send
Prev Chapter 13. Networking Tapset Next

Name

probe::sunrpc.svc.send — │ │ │ │ Return reply to RPC client │ │ │ │ -

Synopsis

sunrpc.svc.send

Values

rq_vers

│ │ │ │ - the program version in the request │ │ │ │ -

peer_ip

│ │ │ │ +

Synopsis

sunrpc.svc.send

Values

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_proc

│ │ │ │ - the procedure number in the request │ │ │ │ -

rq_prot

│ │ │ │ - the IP protocol of the reqeust │ │ │ │

sv_name

│ │ │ │ the service name │ │ │ │ +

rq_vers

│ │ │ │ + the program version in the request │ │ │ │ +

rq_prot

│ │ │ │ + the IP protocol of the reqeust │ │ │ │ +

rq_proc

│ │ │ │ + the procedure number in the request │ │ │ │ +

rq_xid

│ │ │ │ + the transmission id in the request │ │ │ │

Prev Up Next
probe::sunrpc.svc.register Home probe::tcp.disconnect
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-syscall-any-return.html │ │ │ │ @@ -1,15 +1,15 @@ │ │ │ │ probe::syscall_any.return
probe::syscall_any.return
Prev Chapter 36. Syscall Any Tapset Next

Name

probe::syscall_any.return — │ │ │ │ Record exit from a syscall │ │ │ │ -

Synopsis

syscall_any.return

Values

retval

│ │ │ │ - return value of the syscall │ │ │ │ -

syscall_nr

│ │ │ │ +

Synopsis

syscall_any.return

Values

syscall_nr

│ │ │ │ number of the syscall │ │ │ │

name

│ │ │ │ name of the syscall │ │ │ │ +

retval

│ │ │ │ + return value of the syscall │ │ │ │

Context

│ │ │ │ The process performing the syscall │ │ │ │

Description

│ │ │ │ The syscall_any.return probe point is designed to be a low overhead │ │ │ │ that monitors all the syscalls returns via a kernel tracepoint. │ │ │ │ Because of the breadth of syscalls it monitors it provides │ │ │ │ no information about the syscall arguments, argstr string │ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-syscall-any.html │ │ │ │ @@ -1,13 +1,13 @@ │ │ │ │ probe::syscall_any

probe::syscall_any
Prev Chapter 36. Syscall Any Tapset Next

Name

probe::syscall_any — │ │ │ │ Record entry into a syscall │ │ │ │ -

Synopsis

syscall_any

Values

syscall_nr

│ │ │ │ - number of the syscall │ │ │ │ -

name

│ │ │ │ +

Synopsis

syscall_any

Values

name

│ │ │ │ name of the syscall │ │ │ │ +

syscall_nr

│ │ │ │ + number of the syscall │ │ │ │

Context

│ │ │ │ The process performing the syscall │ │ │ │

Description

│ │ │ │ The syscall_any probe point is designed to be a low overhead │ │ │ │ that monitors all the syscalls entered via a kernel tracepoint. │ │ │ │ Because of the breadth of syscalls it monitors it provides │ │ │ │ no information about the syscall arguments or argstr string │ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-tcp-disconnect-return.html │ │ │ │ @@ -1,9 +1,9 @@ │ │ │ │ probe::tcp.disconnect.return

probe::tcp.disconnect.return
Prev Chapter 13. Networking Tapset Next

Name

probe::tcp.disconnect.return — │ │ │ │ TCP socket disconnection complete │ │ │ │ -

Synopsis

tcp.disconnect.return

Values

ret

│ │ │ │ - Error code (0: no error) │ │ │ │ -

name

│ │ │ │ +

Synopsis

tcp.disconnect.return

Values

name

│ │ │ │ Name of this probe │ │ │ │ +

ret

│ │ │ │ + Error code (0: no error) │ │ │ │

Context

│ │ │ │ The process which disconnects tcp │ │ │ │

Prev Up Next
probe::tcp.disconnect Home probe::tcp.receive
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-tcp-disconnect.html │ │ │ │ @@ -1,21 +1,21 @@ │ │ │ │ probe::tcp.disconnect
probe::tcp.disconnect
Prev Chapter 13. Networking Tapset Next

Name

probe::tcp.disconnect — │ │ │ │ TCP socket disconnection │ │ │ │ -

Synopsis

tcp.disconnect

Values

saddr

│ │ │ │ - A string representing the source IP address │ │ │ │ -

dport

│ │ │ │ - TCP destination port │ │ │ │ +

Synopsis

tcp.disconnect

Values

family

│ │ │ │ + IP address family │ │ │ │

flags

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

daddr

│ │ │ │ + A string representing the destination IP address │ │ │ │

sport

│ │ │ │ TCP source port │ │ │ │ +

saddr

│ │ │ │ + A string representing the source IP address │ │ │ │

name

│ │ │ │ Name of this probe │ │ │ │ -

family

│ │ │ │ - IP address family │ │ │ │ -

daddr

│ │ │ │ - A string representing the destination IP address │ │ │ │

sock

│ │ │ │ Network socket │ │ │ │ +

dport

│ │ │ │ + TCP destination port │ │ │ │

Context

│ │ │ │ The process which disconnects tcp │ │ │ │

Prev Up Next
probe::sunrpc.svc.send Home probe::tcp.disconnect.return
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-tcp-receive.html │ │ │ │ @@ -1,31 +1,31 @@ │ │ │ │ probe::tcp.receive
probe::tcp.receive
Prev Chapter 13. Networking Tapset Next

Name

probe::tcp.receive — │ │ │ │ Called when a TCP packet is received │ │ │ │ -

Synopsis

tcp.receive

Values

sport

│ │ │ │ - TCP source port │ │ │ │ -

syn

│ │ │ │ - TCP SYN flag │ │ │ │ +

Synopsis

tcp.receive

Values

psh

│ │ │ │ + TCP PSH flag │ │ │ │ +

iphdr

│ │ │ │ + IP header address │ │ │ │ +

dport

│ │ │ │ + TCP destination port │ │ │ │ +

fin

│ │ │ │ + TCP FIN flag │ │ │ │

ack

│ │ │ │ TCP ACK flag │ │ │ │ -

rst

│ │ │ │ - TCP RST flag │ │ │ │

urg

│ │ │ │ TCP URG flag │ │ │ │ -

saddr

│ │ │ │ - A string representing the source IP address │ │ │ │ -

fin

│ │ │ │ - TCP FIN flag │ │ │ │ -

psh

│ │ │ │ - TCP PSH flag │ │ │ │ -

iphdr

│ │ │ │ - IP header address │ │ │ │

family

│ │ │ │ IP address family │ │ │ │ -

daddr

│ │ │ │ - A string representing the destination IP address │ │ │ │ -

name

│ │ │ │ - Name of the probe point │ │ │ │ -

dport

│ │ │ │ - TCP destination port │ │ │ │

protocol

│ │ │ │ Packet protocol from driver │ │ │ │ +

name

│ │ │ │ + Name of the probe point │ │ │ │ +

saddr

│ │ │ │ + A string representing the source IP address │ │ │ │ +

sport

│ │ │ │ + TCP source port │ │ │ │ +

syn

│ │ │ │ + TCP SYN flag │ │ │ │ +

rst

│ │ │ │ + TCP RST flag │ │ │ │ +

daddr

│ │ │ │ + A string representing the destination IP address │ │ │ │

Prev Up Next
probe::tcp.disconnect.return Home probe::tcp.recvmsg
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-tcp-recvmsg-return.html │ │ │ │ @@ -1,19 +1,19 @@ │ │ │ │ probe::tcp.recvmsg.return
probe::tcp.recvmsg.return
Prev Chapter 13. Networking Tapset Next

Name

probe::tcp.recvmsg.return — │ │ │ │ Receiving TCP message complete │ │ │ │ -

Synopsis

tcp.recvmsg.return

Values

dport

│ │ │ │ - TCP destination port │ │ │ │ -

size

│ │ │ │ - Number of bytes received or error code if an error occurred. │ │ │ │ -

saddr

│ │ │ │ +

Synopsis

tcp.recvmsg.return

Values

saddr

│ │ │ │ A string representing the source IP address │ │ │ │ -

daddr

│ │ │ │ - A string representing the destination IP address │ │ │ │ -

family

│ │ │ │ - IP address family │ │ │ │

name

│ │ │ │ Name of this probe │ │ │ │ +

dport

│ │ │ │ + TCP destination port │ │ │ │ +

family

│ │ │ │ + IP address family │ │ │ │ +

daddr

│ │ │ │ + A string representing the destination IP address │ │ │ │

sport

│ │ │ │ TCP source port │ │ │ │ +

size

│ │ │ │ + Number of bytes received or error code if an error occurred. │ │ │ │

Context

│ │ │ │ The process which receives a tcp message │ │ │ │

Prev Up Next
probe::tcp.recvmsg Home probe::tcp.sendmsg
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-tcp-recvmsg.html │ │ │ │ @@ -1,21 +1,21 @@ │ │ │ │ probe::tcp.recvmsg
probe::tcp.recvmsg
Prev Chapter 13. Networking Tapset Next

Name

probe::tcp.recvmsg — │ │ │ │ Receiving TCP message │ │ │ │ -

Synopsis

tcp.recvmsg

Values

size

│ │ │ │ - Number of bytes to be received │ │ │ │ -

dport

│ │ │ │ - TCP destination port │ │ │ │ +

Synopsis

tcp.recvmsg

Values

sock

│ │ │ │ + Network socket │ │ │ │ +

name

│ │ │ │ + Name of this probe │ │ │ │

saddr

│ │ │ │ A string representing the source IP address │ │ │ │ -

sock

│ │ │ │ - Network socket │ │ │ │ +

dport

│ │ │ │ + TCP destination port │ │ │ │

daddr

│ │ │ │ A string representing the destination IP address │ │ │ │

family

│ │ │ │ IP address family │ │ │ │ -

name

│ │ │ │ - Name of this probe │ │ │ │ +

size

│ │ │ │ + Number of bytes to be received │ │ │ │

sport

│ │ │ │ TCP source port │ │ │ │

Context

│ │ │ │ The process which receives a tcp message │ │ │ │

Prev Up Next
probe::tcp.receive Home probe::tcp.recvmsg.return
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-tcp-sendmsg-return.html │ │ │ │ @@ -1,9 +1,9 @@ │ │ │ │ probe::tcp.sendmsg.return
probe::tcp.sendmsg.return
Prev Chapter 13. Networking Tapset Next

Name

probe::tcp.sendmsg.return — │ │ │ │ Sending TCP message is done │ │ │ │ -

Synopsis

tcp.sendmsg.return

Values

name

│ │ │ │ - Name of this probe │ │ │ │ -

size

│ │ │ │ +

Synopsis

tcp.sendmsg.return

Values

size

│ │ │ │ Number of bytes sent or error code if an error occurred. │ │ │ │ +

name

│ │ │ │ + Name of this probe │ │ │ │

Context

│ │ │ │ The process which sends a tcp message │ │ │ │

Prev Up Next
probe::tcp.sendmsg Home probe::tcp.setsockopt
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-tcp-sendmsg.html │ │ │ │ @@ -1,13 +1,13 @@ │ │ │ │ probe::tcp.sendmsg
probe::tcp.sendmsg
Prev Chapter 13. Networking Tapset Next

Name

probe::tcp.sendmsg — │ │ │ │ Sending a tcp message │ │ │ │ -

Synopsis

tcp.sendmsg

Values

name

│ │ │ │ +

Synopsis

tcp.sendmsg

Values

sock

│ │ │ │ + Network socket │ │ │ │ +

name

│ │ │ │ Name of this probe │ │ │ │

family

│ │ │ │ IP address family │ │ │ │

size

│ │ │ │ Number of bytes to send │ │ │ │ -

sock

│ │ │ │ - Network socket │ │ │ │

Context

│ │ │ │ The process which sends a tcp message │ │ │ │

Prev Up Next
probe::tcp.recvmsg.return Home probe::tcp.sendmsg.return
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-tcp-setsockopt-return.html │ │ │ │ @@ -1,9 +1,9 @@ │ │ │ │ probe::tcp.setsockopt.return
probe::tcp.setsockopt.return
Prev Chapter 13. Networking Tapset Next

Name

probe::tcp.setsockopt.return — │ │ │ │ Return from setsockopt │ │ │ │ -

Synopsis

tcp.setsockopt.return

Values

ret

│ │ │ │ - Error code (0: no error) │ │ │ │ -

name

│ │ │ │ +

Synopsis

tcp.setsockopt.return

Values

name

│ │ │ │ Name of this probe │ │ │ │ +

ret

│ │ │ │ + Error code (0: no error) │ │ │ │

Context

│ │ │ │ The process which calls setsockopt │ │ │ │

Prev Up Next
probe::tcp.setsockopt Home probe::udp.disconnect
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-tcp-setsockopt.html │ │ │ │┄ Ordering differences only │ │ │ │ @@ -1,19 +1,19 @@ │ │ │ │ probe::tcp.setsockopt
probe::tcp.setsockopt
Prev Chapter 13. Networking Tapset Next

Name

probe::tcp.setsockopt — │ │ │ │ Call to setsockopt │ │ │ │

Synopsis

tcp.setsockopt

Values

level

│ │ │ │ The level at which the socket options will be manipulated │ │ │ │ -

optstr

│ │ │ │ - Resolves optname to a human-readable format │ │ │ │

optlen

│ │ │ │ Used to access values for setsockopt │ │ │ │ -

name

│ │ │ │ - Name of this probe │ │ │ │

family

│ │ │ │ IP address family │ │ │ │ -

optname

│ │ │ │ - TCP socket options (e.g. TCP_NODELAY, TCP_MAXSEG, etc) │ │ │ │

sock

│ │ │ │ Network socket │ │ │ │ +

name

│ │ │ │ + Name of this probe │ │ │ │ +

optstr

│ │ │ │ + Resolves optname to a human-readable format │ │ │ │ +

optname

│ │ │ │ + TCP socket options (e.g. TCP_NODELAY, TCP_MAXSEG, etc) │ │ │ │

Context

│ │ │ │ The process which calls setsockopt │ │ │ │

Prev Up Next
probe::tcp.sendmsg.return Home probe::tcp.setsockopt.return
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-tcpmib-ActiveOpens.html │ │ │ │ @@ -1,12 +1,12 @@ │ │ │ │ probe::tcpmib.ActiveOpens
probe::tcpmib.ActiveOpens
Prev Chapter 15. SNMP Information Tapset Next

Name

probe::tcpmib.ActiveOpens — │ │ │ │ Count an active opening of a socket │ │ │ │ -

Synopsis

tcpmib.ActiveOpens

Values

sk

│ │ │ │ - pointer to the struct sock being acted on │ │ │ │ -

op

│ │ │ │ +

Synopsis

tcpmib.ActiveOpens

Values

op

│ │ │ │ value to be added to the counter (default value of 1) │ │ │ │ +

sk

│ │ │ │ + pointer to the struct sock being acted on │ │ │ │

Description

│ │ │ │ The packet pointed to by skb is filtered by the function │ │ │ │ tcpmib_filter_key. If the packet passes the filter is is │ │ │ │ counted in the global ActiveOpens (equivalent to SNMP's MIB │ │ │ │ TCP_MIB_ACTIVEOPENS) │ │ │ │

Prev Up Next
probe::linuxmib.TCPMemoryPressures Home probe::tcpmib.AttemptFails
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-tcpmib-EstabResets.html │ │ │ │ @@ -1,12 +1,12 @@ │ │ │ │ probe::tcpmib.EstabResets
probe::tcpmib.EstabResets
Prev Chapter 15. SNMP Information Tapset Next

Name

probe::tcpmib.EstabResets — │ │ │ │ Count the reset of a socket │ │ │ │ -

Synopsis

tcpmib.EstabResets

Values

op

│ │ │ │ - value to be added to the counter (default value of 1) │ │ │ │ -

sk

│ │ │ │ +

Synopsis

tcpmib.EstabResets

Values

sk

│ │ │ │ pointer to the struct sock being acted on │ │ │ │ +

op

│ │ │ │ + value to be added to the counter (default value of 1) │ │ │ │

Description

│ │ │ │ The packet pointed to by skb is filtered by the function │ │ │ │ tcpmib_filter_key. If the packet passes the filter is is │ │ │ │ counted in the global EstabResets (equivalent to SNMP's MIB │ │ │ │ TCP_MIB_ESTABRESETS) │ │ │ │

Prev Up Next
probe::tcpmib.CurrEstab Home probe::tcpmib.InSegs
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-tcpmib-InSegs.html │ │ │ │ @@ -1,13 +1,13 @@ │ │ │ │ probe::tcpmib.InSegs
probe::tcpmib.InSegs
Prev Chapter 15. SNMP Information Tapset Next

Name

probe::tcpmib.InSegs — │ │ │ │ Count an incoming tcp segment │ │ │ │ -

Synopsis

tcpmib.InSegs

Values

op

│ │ │ │ - value to be added to the counter (default value of 1) │ │ │ │ -

sk

│ │ │ │ +

Synopsis

tcpmib.InSegs

Values

sk

│ │ │ │ pointer to the struct sock being acted on │ │ │ │ +

op

│ │ │ │ + value to be added to the counter (default value of 1) │ │ │ │

Description

│ │ │ │ The packet pointed to by skb is filtered by the function │ │ │ │ tcpmib_filter_key (or ipmib_filter_key for tcp v4). │ │ │ │ If the packet passes the filter is is │ │ │ │ counted in the global InSegs (equivalent to SNMP's MIB │ │ │ │ TCP_MIB_INSEGS) │ │ │ │

Prev Up Next
probe::tcpmib.EstabResets Home probe::tcpmib.OutRsts
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-tcpmib-PassiveOpens.html │ │ │ │ @@ -1,12 +1,12 @@ │ │ │ │ probe::tcpmib.PassiveOpens
probe::tcpmib.PassiveOpens
Prev Chapter 15. SNMP Information Tapset Next

Name

probe::tcpmib.PassiveOpens — │ │ │ │ Count the passive creation of a socket │ │ │ │ -

Synopsis

tcpmib.PassiveOpens

Values

op

│ │ │ │ - value to be added to the counter (default value of 1) │ │ │ │ -

sk

│ │ │ │ +

Synopsis

tcpmib.PassiveOpens

Values

sk

│ │ │ │ pointer to the struct sock being acted on │ │ │ │ +

op

│ │ │ │ + value to be added to the counter (default value of 1) │ │ │ │

Description

│ │ │ │ The packet pointed to by skb is filtered by the function │ │ │ │ tcpmib_filter_key. If the packet passes the filter is is │ │ │ │ counted in the global PassiveOpens (equivalent to SNMP's MIB │ │ │ │ TCP_MIB_PASSIVEOPENS) │ │ │ │

Prev Up Next
probe::tcpmib.OutSegs Home probe::tcpmib.RetransSegs
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-tty-init.html │ │ │ │ @@ -1,9 +1,9 @@ │ │ │ │ probe::tty.init
probe::tty.init
Prev Chapter 11. TTY Tapset Next

Name

probe::tty.init — │ │ │ │ Called when a tty is being initalized │ │ │ │ -

Synopsis

tty.init

Values

driver_name

│ │ │ │ - the driver name │ │ │ │ -

module

│ │ │ │ +

Synopsis

tty.init

Values

module

│ │ │ │ the module name │ │ │ │ +

driver_name

│ │ │ │ + the driver name │ │ │ │

name

│ │ │ │ the driver .dev_name name │ │ │ │

Prev Up Next
Chapter 11. TTY Tapset Home probe::tty.ioctl
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-tty-ioctl.html │ │ │ │ @@ -1,9 +1,9 @@ │ │ │ │ probe::tty.ioctl
probe::tty.ioctl
Prev Chapter 11. TTY Tapset Next

Name

probe::tty.ioctl — │ │ │ │ called when a ioctl is request to the tty │ │ │ │ -

Synopsis

tty.ioctl

Values

cmd

│ │ │ │ +

Synopsis

tty.ioctl

Values

name

│ │ │ │ + the file name │ │ │ │ +

cmd

│ │ │ │ the ioctl command │ │ │ │

arg

│ │ │ │ the ioctl argument │ │ │ │ -

name

│ │ │ │ - the file name │ │ │ │

Prev Up Next
probe::tty.init Home probe::tty.open
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-tty-open.html │ │ │ │ @@ -1,15 +1,15 @@ │ │ │ │ probe::tty.open
probe::tty.open
Prev Chapter 11. TTY Tapset Next

Name

probe::tty.open — │ │ │ │ Called when a tty is opened │ │ │ │ -

Synopsis

tty.open

Values

inode_state

│ │ │ │ - the inode state │ │ │ │ -

file_name

│ │ │ │ - the file name │ │ │ │ -

file_flags

│ │ │ │ - the file flags │ │ │ │ +

Synopsis

tty.open

Values

file_mode

│ │ │ │ + the file mode │ │ │ │

inode_flags

│ │ │ │ the inode flags │ │ │ │

inode_number

│ │ │ │ the inode number │ │ │ │ -

file_mode

│ │ │ │ - the file mode │ │ │ │ +

inode_state

│ │ │ │ + the inode state │ │ │ │ +

file_flags

│ │ │ │ + the file flags │ │ │ │ +

file_name

│ │ │ │ + the file name │ │ │ │

Prev Up Next
probe::tty.ioctl Home probe::tty.poll
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-tty-poll.html │ │ │ │ @@ -1,7 +1,7 @@ │ │ │ │ probe::tty.poll
probe::tty.poll
Prev Chapter 11. TTY Tapset Next

Name

probe::tty.poll — │ │ │ │ Called when a tty device is being polled │ │ │ │ -

Synopsis

tty.poll

Values

file_name

│ │ │ │ - the tty file name │ │ │ │ -

wait_key

│ │ │ │ +

Synopsis

tty.poll

Values

wait_key

│ │ │ │ the wait queue key │ │ │ │ +

file_name

│ │ │ │ + the tty file name │ │ │ │

Prev Up Next
probe::tty.open Home probe::tty.read
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-tty-read.html │ │ │ │ @@ -1,11 +1,11 @@ │ │ │ │ probe::tty.read
probe::tty.read
Prev Chapter 11. TTY Tapset Next

Name

probe::tty.read — │ │ │ │ called when a tty line will be read │ │ │ │ -

Synopsis

tty.read

Values

nr

│ │ │ │ - The amount of characters to be read │ │ │ │ -

driver_name

│ │ │ │ +

Synopsis

tty.read

Values

driver_name

│ │ │ │ the driver name │ │ │ │

file_name

│ │ │ │ the file name lreated to the tty │ │ │ │

buffer

│ │ │ │ the buffer that will receive the characters │ │ │ │ +

nr

│ │ │ │ + The amount of characters to be read │ │ │ │

Prev Up Next
probe::tty.poll Home probe::tty.receive
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-tty-receive.html │ │ │ │ @@ -1,17 +1,17 @@ │ │ │ │ probe::tty.receive
probe::tty.receive
Prev Chapter 11. TTY Tapset Next

Name

probe::tty.receive — │ │ │ │ called when a tty receives a message │ │ │ │ -

Synopsis

tty.receive

Values

driver_name

│ │ │ │ - the driver name │ │ │ │ -

index

│ │ │ │ +

Synopsis

tty.receive

Values

index

│ │ │ │ The tty Index │ │ │ │ -

id

│ │ │ │ - the tty id │ │ │ │

count

│ │ │ │ The amount of characters received │ │ │ │ -

name

│ │ │ │ - the name of the module file │ │ │ │

fp

│ │ │ │ The flag buffer │ │ │ │

cp

│ │ │ │ the buffer that was received │ │ │ │ +

id

│ │ │ │ + the tty id │ │ │ │ +

driver_name

│ │ │ │ + the driver name │ │ │ │ +

name

│ │ │ │ + the name of the module file │ │ │ │

Prev Up Next
probe::tty.read Home probe::tty.register
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-tty-register.html │ │ │ │ @@ -1,11 +1,11 @@ │ │ │ │ probe::tty.register
probe::tty.register
Prev Chapter 11. TTY Tapset Next

Name

probe::tty.register — │ │ │ │ Called when a tty device is registred │ │ │ │ -

Synopsis

tty.register

Values

name

│ │ │ │ - the driver .dev_name name │ │ │ │ -

module

│ │ │ │ +

Synopsis

tty.register

Values

module

│ │ │ │ the module name │ │ │ │ -

driver_name

│ │ │ │ - the driver name │ │ │ │

index

│ │ │ │ the tty index requested │ │ │ │ +

driver_name

│ │ │ │ + the driver name │ │ │ │ +

name

│ │ │ │ + the driver .dev_name name │ │ │ │

Prev Up Next
probe::tty.receive Home probe::tty.release
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-tty-release.html │ │ │ │ @@ -1,15 +1,15 @@ │ │ │ │ probe::tty.release
probe::tty.release
Prev Chapter 11. TTY Tapset Next

Name

probe::tty.release — │ │ │ │ Called when the tty is closed │ │ │ │ -

Synopsis

tty.release

Values

file_mode

│ │ │ │ - the file mode │ │ │ │ +

Synopsis

tty.release

Values

inode_flags

│ │ │ │ + the inode flags │ │ │ │

inode_number

│ │ │ │ the inode number │ │ │ │ -

inode_flags

│ │ │ │ - the inode flags │ │ │ │ -

file_name

│ │ │ │ - the file name │ │ │ │

inode_state

│ │ │ │ the inode state │ │ │ │ +

file_mode

│ │ │ │ + the file mode │ │ │ │ +

file_name

│ │ │ │ + the file name │ │ │ │

file_flags

│ │ │ │ the file flags │ │ │ │

Prev Up Next
probe::tty.register Home probe::tty.resize
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-tty-resize.html │ │ │ │┄ Ordering differences only │ │ │ │ @@ -1,21 +1,21 @@ │ │ │ │ probe::tty.resize
probe::tty.resize
Prev Chapter 11. TTY Tapset Next

Name

probe::tty.resize — │ │ │ │ Called when a terminal resize happens │ │ │ │

Synopsis

tty.resize

Values

new_col

│ │ │ │ the new col value │ │ │ │ -

old_ypixel

│ │ │ │ - the old ypixel │ │ │ │ -

name

│ │ │ │ - the tty name │ │ │ │ -

new_row

│ │ │ │ - the new row value │ │ │ │ -

new_xpixel

│ │ │ │ - the new xpixel value │ │ │ │

old_xpixel

│ │ │ │ the old xpixel │ │ │ │

old_row

│ │ │ │ the old row value │ │ │ │ +

name

│ │ │ │ + the tty name │ │ │ │ +

old_ypixel

│ │ │ │ + the old ypixel │ │ │ │ +

new_row

│ │ │ │ + the new row value │ │ │ │

new_ypixel

│ │ │ │ the new ypixel value │ │ │ │

old_col

│ │ │ │ the old col value │ │ │ │ +

new_xpixel

│ │ │ │ + the new xpixel value │ │ │ │

Prev Up Next
probe::tty.release Home probe::tty.unregister
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-tty-unregister.html │ │ │ │ @@ -1,11 +1,11 @@ │ │ │ │ probe::tty.unregister
probe::tty.unregister
Prev Chapter 11. TTY Tapset Next

Name

probe::tty.unregister — │ │ │ │ Called when a tty device is being unregistered │ │ │ │ -

Synopsis

tty.unregister

Values

name

│ │ │ │ - the driver .dev_name name │ │ │ │ -

module

│ │ │ │ +

Synopsis

tty.unregister

Values

module

│ │ │ │ the module name │ │ │ │ -

driver_name

│ │ │ │ - the driver name │ │ │ │

index

│ │ │ │ the tty index requested │ │ │ │ +

driver_name

│ │ │ │ + the driver name │ │ │ │ +

name

│ │ │ │ + the driver .dev_name name │ │ │ │

Prev Up Next
probe::tty.resize Home probe::tty.write
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-tty-write.html │ │ │ │┄ Ordering differences only │ │ │ │ @@ -1,11 +1,11 @@ │ │ │ │ probe::tty.write
probe::tty.write
Prev Chapter 11. TTY Tapset Next

Name

probe::tty.write — │ │ │ │ write to the tty line │ │ │ │

Synopsis

tty.write

Values

driver_name

│ │ │ │ the driver name │ │ │ │ +

buffer

│ │ │ │ + the buffer that will be written │ │ │ │

nr

│ │ │ │ The amount of characters │ │ │ │

file_name

│ │ │ │ the file name lreated to the tty │ │ │ │ -

buffer

│ │ │ │ - the buffer that will be written │ │ │ │

Prev Up Next
probe::tty.unregister Home Chapter 12. Interrupt Request (IRQ) Tapset
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-udp-disconnect-return.html │ │ │ │ @@ -1,19 +1,19 @@ │ │ │ │ probe::udp.disconnect.return
probe::udp.disconnect.return
Prev Chapter 13. Networking Tapset Next

Name

probe::udp.disconnect.return — │ │ │ │ UDP has been disconnected successfully │ │ │ │ -

Synopsis

udp.disconnect.return

Values

name

│ │ │ │ - The name of this probe │ │ │ │ +

Synopsis

udp.disconnect.return

Values

sport

│ │ │ │ + UDP source port │ │ │ │

dport

│ │ │ │ UDP destination port │ │ │ │ -

sport

│ │ │ │ - UDP source port │ │ │ │ +

ret

│ │ │ │ + Error code (0: no error) │ │ │ │

family

│ │ │ │ IP address family │ │ │ │

daddr

│ │ │ │ A string representing the destination IP address │ │ │ │

saddr

│ │ │ │ A string representing the source IP address │ │ │ │ -

ret

│ │ │ │ - Error code (0: no error) │ │ │ │ +

name

│ │ │ │ + The name of this probe │ │ │ │

Context

│ │ │ │ The process which requested a UDP disconnection │ │ │ │

Prev Up Next
probe::udp.disconnect Home probe::udp.recvmsg
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-udp-disconnect.html │ │ │ │ @@ -1,21 +1,21 @@ │ │ │ │ probe::udp.disconnect
probe::udp.disconnect
Prev Chapter 13. Networking Tapset Next

Name

probe::udp.disconnect — │ │ │ │ Fires when a process requests for a UDP disconnection │ │ │ │ -

Synopsis

udp.disconnect

Values

saddr

│ │ │ │ - A string representing the source IP address │ │ │ │ -

name

│ │ │ │ - The name of this probe │ │ │ │ -

daddr

│ │ │ │ - A string representing the destination IP address │ │ │ │ -

sport

│ │ │ │ - UDP source port │ │ │ │ +

Synopsis

udp.disconnect

Values

family

│ │ │ │ + IP address family │ │ │ │ +

flags

│ │ │ │ + Flags (e.g. FIN, etc) │ │ │ │

dport

│ │ │ │ UDP destination port │ │ │ │ +

sport

│ │ │ │ + UDP source port │ │ │ │

sock

│ │ │ │ Network socket used by the process │ │ │ │ -

flags

│ │ │ │ - Flags (e.g. FIN, etc) │ │ │ │ -

family

│ │ │ │ - IP address family │ │ │ │ +

name

│ │ │ │ + The name of this probe │ │ │ │ +

saddr

│ │ │ │ + A string representing the source IP address │ │ │ │ +

daddr

│ │ │ │ + A string representing the destination IP address │ │ │ │

Context

│ │ │ │ The process which requests a UDP disconnection │ │ │ │

Prev Up Next
probe::tcp.setsockopt.return Home probe::udp.disconnect.return
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-udp-recvmsg-return.html │ │ │ │ @@ -1,19 +1,19 @@ │ │ │ │ probe::udp.recvmsg.return
probe::udp.recvmsg.return
Prev Chapter 13. Networking Tapset Next

Name

probe::udp.recvmsg.return — │ │ │ │ Fires whenever an attempt to receive a UDP message received is completed │ │ │ │ -

Synopsis

udp.recvmsg.return

Values

daddr

│ │ │ │ - A string representing the destination IP address │ │ │ │ -

name

│ │ │ │ - The name of this probe │ │ │ │ -

saddr

│ │ │ │ - A string representing the source IP address │ │ │ │ +

Synopsis

udp.recvmsg.return

Values

size

│ │ │ │ + Number of bytes received by the process │ │ │ │

family

│ │ │ │ IP address family │ │ │ │ -

size

│ │ │ │ - Number of bytes received by the process │ │ │ │

dport

│ │ │ │ UDP destination port │ │ │ │

sport

│ │ │ │ UDP source port │ │ │ │ +

name

│ │ │ │ + The name of this probe │ │ │ │ +

saddr

│ │ │ │ + A string representing the source IP address │ │ │ │ +

daddr

│ │ │ │ + A string representing the destination IP address │ │ │ │

Context

│ │ │ │ The process which received a UDP message │ │ │ │

Prev Up Next
probe::udp.recvmsg Home probe::udp.sendmsg
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-udp-recvmsg.html │ │ │ │ @@ -1,21 +1,21 @@ │ │ │ │ probe::udp.recvmsg
probe::udp.recvmsg
Prev Chapter 13. Networking Tapset Next

Name

probe::udp.recvmsg — │ │ │ │ Fires whenever a UDP message is received │ │ │ │ -

Synopsis

udp.recvmsg

Values

dport

│ │ │ │ - UDP destination port │ │ │ │ -

sport

│ │ │ │ +

Synopsis

udp.recvmsg

Values

sport

│ │ │ │ UDP source port │ │ │ │ +

dport

│ │ │ │ + UDP destination port │ │ │ │

family

│ │ │ │ IP address family │ │ │ │ -

sock

│ │ │ │ - Network socket used by the process │ │ │ │

size

│ │ │ │ Number of bytes received by the process │ │ │ │

daddr

│ │ │ │ A string representing the destination IP address │ │ │ │ -

name

│ │ │ │ - The name of this probe │ │ │ │

saddr

│ │ │ │ A string representing the source IP address │ │ │ │ +

name

│ │ │ │ + The name of this probe │ │ │ │ +

sock

│ │ │ │ + Network socket used by the process │ │ │ │

Context

│ │ │ │ The process which received a UDP message │ │ │ │

Prev Up Next
probe::udp.disconnect.return Home probe::udp.recvmsg.return
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-udp-sendmsg.html │ │ │ │ @@ -1,21 +1,21 @@ │ │ │ │ probe::udp.sendmsg
probe::udp.sendmsg
Prev Chapter 13. Networking Tapset Next

Name

probe::udp.sendmsg — │ │ │ │ Fires whenever a process sends a UDP message │ │ │ │ -

Synopsis

udp.sendmsg

Values

daddr

│ │ │ │ +

Synopsis

udp.sendmsg

Values

name

│ │ │ │ + The name of this probe │ │ │ │ +

sock

│ │ │ │ + Network socket used by the process │ │ │ │ +

daddr

│ │ │ │ A string representing the destination IP address │ │ │ │

saddr

│ │ │ │ A string representing the source IP address │ │ │ │ -

name

│ │ │ │ - The name of this probe │ │ │ │

family

│ │ │ │ IP address family │ │ │ │ -

sock

│ │ │ │ - Network socket used by the process │ │ │ │ -

size

│ │ │ │ - Number of bytes sent by the process │ │ │ │ -

dport

│ │ │ │ - UDP destination port │ │ │ │

sport

│ │ │ │ UDP source port │ │ │ │ +

dport

│ │ │ │ + UDP destination port │ │ │ │ +

size

│ │ │ │ + Number of bytes sent by the process │ │ │ │

Context

│ │ │ │ The process which sent a UDP message │ │ │ │

Prev Up Next
probe::udp.recvmsg.return Home probe::udp.sendmsg.return
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-vm-brk.html │ │ │ │ @@ -1,11 +1,11 @@ │ │ │ │ probe::vm.brk
probe::vm.brk
Prev Chapter 6. Memory Tapset Next

Name

probe::vm.brk — │ │ │ │ Fires when a brk is requested (i.e. the heap will be resized) │ │ │ │ -

Synopsis

vm.brk

Values

length

│ │ │ │ - the length of the memory segment │ │ │ │ -

address

│ │ │ │ +

Synopsis

vm.brk

Values

address

│ │ │ │ the requested address │ │ │ │ +

length

│ │ │ │ + the length of the memory segment │ │ │ │

name

│ │ │ │ name of the probe point │ │ │ │

Context

│ │ │ │ The process calling brk. │ │ │ │

Prev Up Next
function::vm_fault_contains Home probe::vm.kfree
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-vm-kfree.html │ │ │ │ @@ -1,11 +1,11 @@ │ │ │ │ probe::vm.kfree
probe::vm.kfree
Prev Chapter 6. Memory Tapset Next

Name

probe::vm.kfree — │ │ │ │ Fires when kfree is requested │ │ │ │ -

Synopsis

vm.kfree

Values

name

│ │ │ │ - name of the probe point │ │ │ │ -

caller_function

│ │ │ │ - name of the caller function. │ │ │ │ -

call_site

│ │ │ │ +

Synopsis

vm.kfree

Values

call_site

│ │ │ │ address of the function calling this kmemory function │ │ │ │

ptr

│ │ │ │ pointer to the kmemory allocated which is returned by kmalloc │ │ │ │ +

caller_function

│ │ │ │ + name of the caller function. │ │ │ │ +

name

│ │ │ │ + name of the probe point │ │ │ │

Prev Up Next
probe::vm.brk Home probe::vm.kmalloc
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-vm-kmalloc-node.html │ │ │ │ @@ -1,19 +1,19 @@ │ │ │ │ probe::vm.kmalloc_node
probe::vm.kmalloc_node
Prev Chapter 6. Memory Tapset Next

Name

probe::vm.kmalloc_node — │ │ │ │ Fires when kmalloc_node is requested │ │ │ │ -

Synopsis

vm.kmalloc_node

Values

ptr

│ │ │ │ - pointer to the kmemory allocated │ │ │ │ +

Synopsis

vm.kmalloc_node

Values

bytes_req

│ │ │ │ + requested Bytes │ │ │ │

gfp_flag_name

│ │ │ │ type of kmemory to allocate(in string format) │ │ │ │

name

│ │ │ │ name of the probe point │ │ │ │ -

gfp_flags

│ │ │ │ - type of kmemory to allocate │ │ │ │

caller_function

│ │ │ │ name of the caller function │ │ │ │ +

gfp_flags

│ │ │ │ + type of kmemory to allocate │ │ │ │ +

ptr

│ │ │ │ + pointer to the kmemory allocated │ │ │ │

call_site

│ │ │ │ address of the function caling this kmemory function │ │ │ │ -

bytes_req

│ │ │ │ - requested Bytes │ │ │ │

bytes_alloc

│ │ │ │ allocated Bytes │ │ │ │

Prev Up Next
probe::vm.kmalloc Home probe::vm.kmem_cache_alloc
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-vm-kmalloc.html │ │ │ │ @@ -1,19 +1,19 @@ │ │ │ │ probe::vm.kmalloc
probe::vm.kmalloc
Prev Chapter 6. Memory Tapset Next

Name

probe::vm.kmalloc — │ │ │ │ Fires when kmalloc is requested │ │ │ │ -

Synopsis

vm.kmalloc

Values

caller_function

│ │ │ │ - name of the caller function │ │ │ │ -

gfp_flags

│ │ │ │ +

Synopsis

vm.kmalloc

Values

gfp_flags

│ │ │ │ type of kmemory to allocate │ │ │ │ +

caller_function

│ │ │ │ + name of the caller function │ │ │ │

name

│ │ │ │ name of the probe point │ │ │ │

bytes_alloc

│ │ │ │ allocated Bytes │ │ │ │ -

bytes_req

│ │ │ │ - requested Bytes │ │ │ │

call_site

│ │ │ │ address of the kmemory function │ │ │ │

ptr

│ │ │ │ pointer to the kmemory allocated │ │ │ │ +

bytes_req

│ │ │ │ + requested Bytes │ │ │ │

gfp_flag_name

│ │ │ │ type of kmemory to allocate (in String format) │ │ │ │

Prev Up Next
probe::vm.kfree Home probe::vm.kmalloc_node
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-vm-kmem-cache-alloc-node.html │ │ │ │ @@ -1,19 +1,19 @@ │ │ │ │ probe::vm.kmem_cache_alloc_node
probe::vm.kmem_cache_alloc_node
Prev Chapter 6. Memory Tapset Next

Name

probe::vm.kmem_cache_alloc_node — │ │ │ │ Fires when kmem_cache_alloc_node is requested │ │ │ │ -

Synopsis

vm.kmem_cache_alloc_node

Values

gfp_flag_name

│ │ │ │ - type of kmemory to allocate(in string format) │ │ │ │ +

Synopsis

vm.kmem_cache_alloc_node

Values

name

│ │ │ │ + name of the probe point │ │ │ │ +

caller_function

│ │ │ │ + name of the caller function │ │ │ │ +

gfp_flags

│ │ │ │ + type of kmemory to allocate │ │ │ │

ptr

│ │ │ │ pointer to the kmemory allocated │ │ │ │

call_site

│ │ │ │ address of the function calling this kmemory function │ │ │ │

bytes_alloc

│ │ │ │ allocated Bytes │ │ │ │

bytes_req

│ │ │ │ requested Bytes │ │ │ │ -

gfp_flags

│ │ │ │ - type of kmemory to allocate │ │ │ │ -

name

│ │ │ │ - name of the probe point │ │ │ │ -

caller_function

│ │ │ │ - name of the caller function │ │ │ │ +

gfp_flag_name

│ │ │ │ + type of kmemory to allocate(in string format) │ │ │ │

Prev Up Next
probe::vm.kmem_cache_alloc Home probe::vm.kmem_cache_free
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-vm-kmem-cache-alloc.html │ │ │ │ @@ -1,19 +1,19 @@ │ │ │ │ probe::vm.kmem_cache_alloc
probe::vm.kmem_cache_alloc
Prev Chapter 6. Memory Tapset Next

Name

probe::vm.kmem_cache_alloc — │ │ │ │ Fires when kmem_cache_alloc is requested │ │ │ │ -

Synopsis

vm.kmem_cache_alloc

Values

gfp_flag_name

│ │ │ │ - type of kmemory to allocate(in string format) │ │ │ │ -

ptr

│ │ │ │ +

Synopsis

vm.kmem_cache_alloc

Values

ptr

│ │ │ │ pointer to the kmemory allocated │ │ │ │ -

bytes_req

│ │ │ │ - requested Bytes │ │ │ │ -

bytes_alloc

│ │ │ │ - allocated Bytes │ │ │ │

call_site

│ │ │ │ address of the function calling this kmemory function. │ │ │ │ -

caller_function

│ │ │ │ - name of the caller function. │ │ │ │ +

bytes_alloc

│ │ │ │ + allocated Bytes │ │ │ │

name

│ │ │ │ name of the probe point │ │ │ │ +

caller_function

│ │ │ │ + name of the caller function. │ │ │ │

gfp_flags

│ │ │ │ type of kmemory to allocate │ │ │ │ +

gfp_flag_name

│ │ │ │ + type of kmemory to allocate(in string format) │ │ │ │ +

bytes_req

│ │ │ │ + requested Bytes │ │ │ │

Prev Up Next
probe::vm.kmalloc_node Home probe::vm.kmem_cache_alloc_node
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-vm-kmem-cache-free.html │ │ │ │ @@ -1,11 +1,11 @@ │ │ │ │ probe::vm.kmem_cache_free
probe::vm.kmem_cache_free
Prev Chapter 6. Memory Tapset Next

Name

probe::vm.kmem_cache_free — │ │ │ │ Fires when kmem_cache_free is requested │ │ │ │ -

Synopsis

vm.kmem_cache_free

Values

caller_function

│ │ │ │ - Name of the caller function. │ │ │ │ -

name

│ │ │ │ - Name of the probe point │ │ │ │ +

Synopsis

vm.kmem_cache_free

Values

ptr

│ │ │ │ + Pointer to the kmemory allocated which is returned by kmem_cache │ │ │ │

call_site

│ │ │ │ Address of the function calling this kmemory function │ │ │ │ -

ptr

│ │ │ │ - Pointer to the kmemory allocated which is returned by kmem_cache │ │ │ │ +

name

│ │ │ │ + Name of the probe point │ │ │ │ +

caller_function

│ │ │ │ + Name of the caller function. │ │ │ │

Prev Up Next
probe::vm.kmem_cache_alloc_node Home probe::vm.mmap
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-vm-mmap.html │ │ │ │ @@ -1,11 +1,11 @@ │ │ │ │ probe::vm.mmap
probe::vm.mmap
Prev Chapter 6. Memory Tapset Next

Name

probe::vm.mmap — │ │ │ │ Fires when an mmap is requested │ │ │ │ -

Synopsis

vm.mmap

Values

name

│ │ │ │ - name of the probe point │ │ │ │ -

length

│ │ │ │ +

Synopsis

vm.mmap

Values

length

│ │ │ │ the length of the memory segment │ │ │ │

address

│ │ │ │ the requested address │ │ │ │ +

name

│ │ │ │ + name of the probe point │ │ │ │

Context

│ │ │ │ The process calling mmap. │ │ │ │

Prev Up Next
probe::vm.kmem_cache_free Home probe::vm.munmap
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-vm-munmap.html │ │ │ │ @@ -1,11 +1,11 @@ │ │ │ │ probe::vm.munmap
probe::vm.munmap
Prev Chapter 6. Memory Tapset Next

Name

probe::vm.munmap — │ │ │ │ Fires when an munmap is requested │ │ │ │ -

Synopsis

vm.munmap

Values

name

│ │ │ │ - name of the probe point │ │ │ │ +

Synopsis

vm.munmap

Values

address

│ │ │ │ + the requested address │ │ │ │

length

│ │ │ │ the length of the memory segment │ │ │ │ -

address

│ │ │ │ - the requested address │ │ │ │ +

name

│ │ │ │ + name of the probe point │ │ │ │

Context

│ │ │ │ The process calling munmap. │ │ │ │

Prev Up Next
probe::vm.mmap Home probe::vm.oom_kill
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-vm-oom-kill.html │ │ │ │ @@ -1,10 +1,10 @@ │ │ │ │ probe::vm.oom_kill
probe::vm.oom_kill
Prev Chapter 6. Memory Tapset Next

Name

probe::vm.oom_kill — │ │ │ │ Fires when a thread is selected for termination by the OOM killer │ │ │ │ -

Synopsis

vm.oom_kill

Values

task

│ │ │ │ - the task being killed │ │ │ │ -

name

│ │ │ │ +

Synopsis

vm.oom_kill

Values

name

│ │ │ │ name of the probe point │ │ │ │ +

task

│ │ │ │ + the task being killed │ │ │ │

Context

│ │ │ │ The process that tried to consume excessive memory, and thus │ │ │ │ triggered the OOM. │ │ │ │

Prev Up Next
probe::vm.munmap Home probe::vm.pagefault
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-vm-pagefault-return.html │ │ │ │ @@ -1,11 +1,11 @@ │ │ │ │ probe::vm.pagefault.return
probe::vm.pagefault.return
Prev Chapter 6. Memory Tapset Next

Name

probe::vm.pagefault.return — │ │ │ │ Indicates what type of fault occurred │ │ │ │ -

Synopsis

vm.pagefault.return

Values

name

│ │ │ │ - name of the probe point │ │ │ │ -

fault_type

│ │ │ │ +

Synopsis

vm.pagefault.return

Values

fault_type

│ │ │ │ returns either │ │ │ │ 0 (VM_FAULT_OOM) for out of memory faults, │ │ │ │ 2 (VM_FAULT_MINOR) for minor faults, 3 (VM_FAULT_MAJOR) for │ │ │ │ major faults, or 1 (VM_FAULT_SIGBUS) if the fault was neither OOM, minor fault, │ │ │ │ nor major fault. │ │ │ │ +

name

│ │ │ │ + name of the probe point │ │ │ │

Prev Up Next
probe::vm.pagefault Home probe::vm.write_shared
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-vm-pagefault.html │ │ │ │┄ Ordering differences only │ │ │ │ @@ -1,12 +1,12 @@ │ │ │ │ probe::vm.pagefault
probe::vm.pagefault
Prev Chapter 6. Memory Tapset Next

Name

probe::vm.pagefault — │ │ │ │ Records that a page fault occurred │ │ │ │

Synopsis

vm.pagefault

Values

address

│ │ │ │ the address of the faulting memory access; i.e. the address that caused the page fault │ │ │ │ -

name

│ │ │ │ - name of the probe point │ │ │ │

write_access

│ │ │ │ indicates whether this was a write or read access; 1 indicates a write, │ │ │ │ while 0 indicates a read │ │ │ │ +

name

│ │ │ │ + name of the probe point │ │ │ │

Context

│ │ │ │ The process which triggered the fault │ │ │ │

Prev Up Next
probe::vm.oom_kill Home probe::vm.pagefault.return
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-vm-write-shared-copy.html │ │ │ │ @@ -1,15 +1,15 @@ │ │ │ │ probe::vm.write_shared_copy
probe::vm.write_shared_copy
Prev Chapter 6. Memory Tapset Next

Name

probe::vm.write_shared_copy — │ │ │ │ Page copy for shared page write │ │ │ │ -

Synopsis

vm.write_shared_copy

Values

name

│ │ │ │ - Name of the probe point │ │ │ │ -

zero

│ │ │ │ +

Synopsis

vm.write_shared_copy

Values

zero

│ │ │ │ boolean indicating whether it is a zero page │ │ │ │ (can do a clear instead of a copy) │ │ │ │

address

│ │ │ │ The address of the shared write │ │ │ │ +

name

│ │ │ │ + Name of the probe point │ │ │ │

Context

│ │ │ │ The process attempting the write. │ │ │ │

Description

│ │ │ │ Fires when a write to a shared page requires a page copy. This is │ │ │ │ always preceded by a vm.write_shared. │ │ │ │

Prev Up Next
probe::vm.write_shared Home Chapter 7. Task Time Tapset
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-workqueue-create.html │ │ │ │ @@ -1,7 +1,7 @@ │ │ │ │ probe::workqueue.create
probe::workqueue.create
Prev Chapter 12. Interrupt Request (IRQ) Tapset Next

Name

probe::workqueue.create — │ │ │ │ Creating a new workqueue │ │ │ │ -

Synopsis

workqueue.create

Values

wq_thread

│ │ │ │ - task_struct of the workqueue thread │ │ │ │ -

cpu

│ │ │ │ +

Synopsis

workqueue.create

Values

cpu

│ │ │ │ cpu for which the worker thread is created │ │ │ │ +

wq_thread

│ │ │ │ + task_struct of the workqueue thread │ │ │ │

Prev Up Next
probe::softirq.exit Home probe::workqueue.destroy
│ │ │ ├── ./usr/share/doc/systemtap-doc/tapsets/API-workqueue-insert.html │ │ │ │ @@ -1,9 +1,9 @@ │ │ │ │ probe::workqueue.insert
probe::workqueue.insert
Prev Chapter 12. Interrupt Request (IRQ) Tapset Next

Name

probe::workqueue.insert — │ │ │ │ Queuing work on a workqueue │ │ │ │ -

Synopsis

workqueue.insert

Values

wq_thread

│ │ │ │ - task_struct of the workqueue thread │ │ │ │ +

Synopsis

workqueue.insert

Values

work_func

│ │ │ │ + pointer to handler function │ │ │ │

work

│ │ │ │ work_struct* being queued │ │ │ │ -

work_func

│ │ │ │ - pointer to handler function │ │ │ │ +

wq_thread

│ │ │ │ + task_struct of the workqueue thread │ │ │ │

Prev Up Next
probe::workqueue.execute Home Chapter 13. Networking Tapset