# @(#)07 1.5 src/bos/usr/sbin/mobte/mobte.cst, liveupdate, bos72D, d2015_47A0 11/9/15 09:40:25 # IBM_PROLOG_BEGIN_TAG # This is an automatically generated prolog. # # bos72L src/bos/usr/sbin/mobte/mobte.cst 1.7 # # Licensed Materials - Property of IBM # # Restricted Materials of IBM # # COPYRIGHT International Business Machines Corp. 2014,2017 # All Rights Reserved # # US Government Users Restricted Rights - Use, duplication or # disclosure restricted by GSA ADP Schedule Contract with IBM Corp. # # IBM_PROLOG_END_TAG # @(#)07 1.7 src/bos/usr/sbin/mobte/mobte.cst, liveupdate, bos72L, l2017_33A1 8/1/17 04:01:52 # # Data for the mobility time estimator. # # PART1 - CONSTANTS RELATED TO MOBILE WORKLOAD # These constants are valid for live update and WPAR mobility operations. # They determine how the duration of blackout time will be estimated. # FORMAT: # name:[1 | 2] # value1 value2 value3 # MEANING: # name:1 refers to values that are applicable on the departure (original) system. # name:2 refers to values that are applicable on the arrival (surrogate) system. # Blackout time components are computed for each logical partition as: # Time = (value1 + value2*X + value3*X*X) / Y # where X is a workload parameter, Y is a resource (scaling) parameter. # Unless stated otherwise, Y represents the system processing capacity (unit: Hz) # Time is summed over departure and arrival components. # w_mcr: amount of processing needed for mcr operation, independently of other # workload params. # X = 1 w_mcr:1 656000000 0 0 w_mcr:2 2220000000 0 0 # w_proc: amount of processing needed for checkpointing/restoring processes. # X = number of workload processes w_proc:1 0 20000000 2000 w_proc:2 0 20000000 3000 # w_mem: amount of processing (per page) needed for checkpointing/restoring # memory areas. # X = number of memory pages w_mem:1 0 14000 0 w_mem:2 0 4500 0 # w_th: amount of processing (per thread) needed for checkpointing/restoring threads. # X = number of workload threads w_th:1 0 6000000 0 w_th:2 0 500000 0 # w_fd: amount of processing needed for checkpointing/restoring regular files. # X = number of open (regular) file descriptors w_fd:1 0 2400000 0 w_fd:2 0 1600000 0 # w_sock: amount of processing needed for checkpointing/restoring sockets. # X = number of open socket file descriptors w_sock:1 0 1000000 0 w_sock:2 0 2000000 0 # w_mmap: amount of processing needed for checkpointing/restoring memory mapped areas. # X = number of mmaped pages. w_mmap:1 0 492 0 w_mmap:2 0 39 0 # w_shm: amount of processing needed for checkpointing/restoring shared memory areas. # X = number of shm attached pages. w_shm:1 0 6400 0 w_shm:2 0 100 0 # w_sem: amount of processing needed for checkpointing/restoring semaphoress. # X = number of semaphores. w_sem:1 0 10000 0 w_sem:2 0 10000 0 # w_msq: amount of processing needed for checkpointing/restoring message queues. # X = number of messages / number of message queues. w_msq:1 0 400000 500 w_msq:2 0 100000 50 # PART2 - CONSTANTS RELATED TO WPAR MOBILITY OPERATIONS # These constants are valid ONLY for WPAR mobility operations. They determine how # the global operation time will be estimated. There are also some rootvg_wpar # specific constants that affect blackout time. # FORMAT: # name:[1 | 2] # value1 value2 value3 # MEANING: # name:1 refers to values that are applicable on the departure system. # name:2 refers to values that are applicable on the arrival system. # Global or Blackout time components are computed for each logical partition as: # Time = (value1 + value2*X + value3*X*X) / Y # where X is a workload parameter, Y is a resource (scaling) parameter. # Unless stated otherwise, Y represents the system processing capacity (unit: Hz) # Time is summed over departure and arrival components. # lam_glob: amount of processing carried out during pre-mobility work. lam_glob:1 8900000000 0 0 lam_glob:2 31000000000 0 0 # lam_rgvio: constants related to the duration of rootvg operations # X: number of opened files # Y: io time per file lam_rvgio:1 50 3 0 lam_rvgio:2 500 0 0 #lam_rgvmob_b: amount of processing carried out by the rvgmob scripts during blackout d lam_rvgmob_b:1 9000000000 0 0 lam_rvgmob_b:2 25000000000 0 0 #lam_rgvmob_g: amount of processing carried out by the rvgmob scripts outside blackout lam_rvgmob_g:1 40000000000 0 0 lam_rvgmob_g:2 310000000000 0 0 # PART3 - CONSTANTS RELATED TO LIVE UPDATE OPERATIONS # These constants are valid ONLY for live update operations. Most of them determine how # the global operation time will be estimated. Constants with name suffixed as _b # affect blackout time. # FORMAT: # name:[1 | 2] # value1 value2 value3 # MEANING: # name:1 refers to values that are applicable on the original system. # name:2 refers to values that are applicable on the surrogate system. # Global or Blackout time components are computed for each logical partition as: # Time = (value1 + value2*X + value3*X*X) / Y # where X is a workload parameter, Y is a resource (scaling) parameter. # Time is summed over original and surrogate components. #lku_proc_b: amount of processing during the blackout needed for #lku specific mcr operations. lku_proc_b:1 6680000000 0 0 lku_proc_b:2 31700000000 0 0 #lku_proc_g: amount of processing during the lku pre-mobility work lku_proc_g:1 2500000000 0 0 lku_proc_g:2 4000000000 0 0 #lku_vgio_b: amount of IO operations during the lku blackout # X: 1 # Y: io time lku_vgio_b:1 262 0 0 lku_vgio_b:2 368 0 0 #lku_vgio_g: amount of IO operations during the lku pre-mobility work # X: 1 # Y: io time lku_vgio_g:1 45000 0 0 lku_vgio_g:2 45000 0 0 #lkuimp_b: amount of IO operations during the lku blackout needed by splitvg/importvg # X: 1 # Y: IO bandwith lku_imp_b:1 0 18000000 0 lku_imp_b:2 0 18000000 0 #lku_mvg: constants related to the duration of mirrorvg operations # X = mirrorvg data size (overall used physical partition size) # Y = rootvg I/O throughput lku_mvg:1 0 100000 0 lku_mvg:2 0 2200000 0 #lku_nvg: constants related to the duration of backup|restore operations # X = backup/restore data size # Y = rootvg I/O throughput lku_nvg_io:1 0 600000 0 lku_nvg_io:2 0 600000 0 #lku_nvg_pipe: constants related to the duration of backup|restore operations # X = backup/restore data size # Y = interprocess pipe throughput lku_nvg_pipe:1 0 400000 0 lku_nvg_pipe:2 0 400000 0 #various unaccounted for components: boot / fs creation time # X = 1 (unit: time (s)) lku_wait_hmc:2 0 185 0 lku_wait_pvc:2 0 545 0 # PART4 - CONSTANTS RELATED TO SYSTEM RESOURCES # These constants are valid for LVUPDATE or WPAR mobility operations. # FORMAT: # name:0 # value1 value2 value3 ... # MEANING: #veth: table of maximum virtual ethernet throughput for known system types. veth:0 PowerPC_POWER5 120000000 1200000 5000000 5000000 PowerPC_POWER6 180000000 2000000 6000000 6000000 PowerPC_POWER7 220000000 2200000 7000000 7000000 default 120000000 1200000 5000000 5000000 #smt: table of processing capacity scaling factors (100 = reference = power6,smt=2) # -1 indicate invalid typt/smt combination. # FORMAT # proc_type smt=1 smt=2 smt=4 smt=8 smt:0 PowerPC_POWER5 115 150 -1 -1 PowerPC_POWER6 65 100 -1 -1 PowerPC_POWER7 108 165 170 -1 PowerPC_POWER8 160 200 130 110 default 108 165 170 -1 #tfz: processing test specific to online mode estimations of live update operations. #c1 = reference time (unit: millisecond) #c2 = number of cycles tfz:0 620 17000000000 0 #gwlm: constants related to wlm cpu limits for the global environment for lam gwlm:0 3 2 #wwlm: constants related to wlm cpu limits for the wpars for lam wwlm:0 3 2