18%
30.01.2020
| %|Source code
------+----------+-------------+-------------+-------+-----------
1| 0| 0| 0| 0.00%|# md test code
2| 0| 0| 0| 0.00
18%
05.03.2014
:15:01 all 2.08 0.00 0.96 0.02 0.00 96.94
12:25:01 all 1.96 0.00 0.82 0.06 0.00 97.16
12:35:01 PM all 1.22 0.00 0.73 0.00 0.00
18%
20.03.2014
all 1.22 0.00 0.73 0.00 0.00 98.05
12:45:01 PM all 1.32 0.00 0.72 0.01 0.00 97.95
12:55:01 PM all 1.79 0.00 0.75 0
18%
15.08.2016
-> ../../devices/pci0000:00/0000:00:03.0/net/eth0
|---lo -> ../../devices/virtual/net/lo
The device is no longer listed in the default namespace.
Listing 3
Configuring Devices
$ ip link set eth1
17%
05.09.2011
can see how the arp cache poisoning works:
$ sudo nemesis arp -v -r -d eth0 -S 192.168.1.2 \
-D 192.168.1.133 -h 00:22:6E:71:04:BB -m 00:0C:29:B2:78:9E \
-H 00:22:6E:71:04:BB -M 00:0C:29:B2:78:9E
17%
12.02.2014
.py
CPU ALL: 1.0 %
CPU0 4.1%
CPU1 2.0%
CPU2 0.0%
CPU3 0.0%
CPU4 0.0%
CPU5 0.0%
CPU6 0.0%
CPU7 2.0%
CPU ALL:
user: 0.7% nice: 0.0%
system: 0.2% idle
17%
20.02.2012
time: 11.79 secs
Data transferred: 2.47 MB
Response time: 0.22 secs
Transaction rate: 35.79 trans/sec
Throughput: 0
17%
19.11.2019
Jobs: 1 (f=1): [w(1)][100.0%][w=654MiB/s][w=167k IOPS][eta 00m:00s]
test: (groupid=0, jobs=1): err= 0: pid=1225: Sat Oct 12 19:20:18 2019
write: IOPS=168k, BW=655MiB/s (687MB/s)(10.0GiB/15634msec); 0
17%
30.01.2020
=1): err= 0: pid=1634: Mon Oct 14 22:18:59 2019
write: IOPS=118k, BW=463MiB/s (485MB/s)(10.0GiB/22123msec); 0 zone resets
[ ... ]
Run status group 0 (all jobs):
WRITE: bw=463MiB/s (485MB/s), 463Mi
17%
27.08.2014
was the sequential write test using 1MB record sizes:
./iozone -i 0 -c -e -w -r 1024k -s 32g -t 2 -+n > iozone_write_1.out
To gather the block statistics, I ran ioprof in a different terminal window before I ran
