Blame view

kernel/linux-rt-4.4.41/samples/pktgen/functions.sh 2.89 KB
5113f6f70   김현기   kernel add
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
  #
  # Common functions used by pktgen scripts
  #  - Depending on bash 3 (or higher) syntax
  #
  # Author: Jesper Dangaaard Brouer
  # License: GPL
  
  ## -- General shell logging cmds --
  function err() {
      local exitcode=$1
      shift
      echo "ERROR: $@" >&2
      exit $exitcode
  }
  
  function warn() {
      echo "WARN : $@" >&2
  }
  
  function info() {
      if [[ -n "$VERBOSE" ]]; then
  	echo "INFO : $@" >&2
      fi
  }
  
  ## -- Pktgen proc config commands -- ##
  export PROC_DIR=/proc/net/pktgen
  #
  # Three different shell functions for configuring the different
  # components of pktgen:
  #   pg_ctrl(), pg_thread() and pg_set().
  #
  # These functions correspond to pktgens different components.
  # * pg_ctrl()   control "pgctrl" (/proc/net/pktgen/pgctrl)
  # * pg_thread() control the kernel threads and binding to devices
  # * pg_set()    control setup of individual devices
  function pg_ctrl() {
      local proc_file="pgctrl"
      proc_cmd ${proc_file} "$@"
  }
  
  function pg_thread() {
      local thread=$1
      local proc_file="kpktgend_${thread}"
      shift
      proc_cmd ${proc_file} "$@"
  }
  
  function pg_set() {
      local dev=$1
      local proc_file="$dev"
      shift
      proc_cmd ${proc_file} "$@"
  }
  
  # More generic replacement for pgset(), that does not depend on global
  # variable for proc file.
  function proc_cmd() {
      local result
      local proc_file=$1
      # after shift, the remaining args are contained in $@
      shift
      local proc_ctrl=${PROC_DIR}/$proc_file
      if [[ ! -e "$proc_ctrl" ]]; then
  	err 3 "proc file:$proc_ctrl does not exists (dev added to thread?)"
      else
  	if [[ ! -w "$proc_ctrl" ]]; then
  	    err 4 "proc file:$proc_ctrl not writable, not root?!"
  	fi
      fi
  
      if [[ "$DEBUG" == "yes" ]]; then
  	echo "cmd: $@ > $proc_ctrl"
      fi
      # Quoting of "$@" is important for space expansion
      echo "$@" > "$proc_ctrl"
      local status=$?
  
      result=$(grep "Result: OK:" $proc_ctrl)
      # Due to pgctrl, cannot use exit code $? from grep
      if [[ "$result" == "" ]]; then
  	grep "Result:" $proc_ctrl >&2
      fi
      if (( $status != 0 )); then
  	err 5 "Write error($status) occurred cmd: \"$@ > $proc_ctrl\""
      fi
  }
  
  # Old obsolete "pgset" function, with slightly improved err handling
  function pgset() {
      local result
  
      if [[ "$DEBUG" == "yes" ]]; then
  	echo "cmd: $1 > $PGDEV"
      fi
      echo $1 > $PGDEV
      local status=$?
  
      result=`cat $PGDEV | fgrep "Result: OK:"`
      if [[ "$result" == "" ]]; then
           cat $PGDEV | fgrep Result:
      fi
      if (( $status != 0 )); then
  	err 5 "Write error($status) occurred cmd: \"$1 > $PGDEV\""
      fi
  }
  
  ## -- General shell tricks --
  
  function root_check_run_with_sudo() {
      # Trick so, program can be run as normal user, will just use "sudo"
      #  call as root_check_run_as_sudo "$@"
      if [ "$EUID" -ne 0 ]; then
  	if [ -x $0 ]; then # Directly executable use sudo
  	    info "Not root, running with sudo"
              sudo "$0" "$@"
              exit $?
  	fi
  	err 4 "cannot perform sudo run of $0"
      fi
  }