search for: slat

Displaying 9 results from an estimated 9 matches for "slat".

Did you mean: slab
2012 Aug 10
1
virtio-scsi <-> vhost multi lun/adapter performance results with 3.6-rc0
...part -------------- randrw: (g=0): rw=randrw, bs=4K-4K/4K-4K, ioengine=libaio, iodepth=64 ... randrw: (g=0): rw=randrw, bs=4K-4K/4K-4K, ioengine=libaio, iodepth=64 Starting 8 processes randrw: (groupid=0, jobs=1): err= 0: pid=7155 read : io=384MB, bw=62,934KB/s, iops=15,733, runt= 6243msec slat (usec): min=4, max=11,681, avg=167.00, stdev=448.35 clat (usec): min=3, max=19,552, avg=2217.48, stdev=1367.27 bw (KB/s) : min= 0, max=70143, per=1.27%, avg=6362.85, stdev=19236.22 write: io=128MB, bw=21,046KB/s, iops=5,261, runt= 6243msec slat (usec): min=4, max=11,678, avg=164.7...
2012 Aug 10
1
virtio-scsi <-> vhost multi lun/adapter performance results with 3.6-rc0
...part -------------- randrw: (g=0): rw=randrw, bs=4K-4K/4K-4K, ioengine=libaio, iodepth=64 ... randrw: (g=0): rw=randrw, bs=4K-4K/4K-4K, ioengine=libaio, iodepth=64 Starting 8 processes randrw: (groupid=0, jobs=1): err= 0: pid=7155 read : io=384MB, bw=62,934KB/s, iops=15,733, runt= 6243msec slat (usec): min=4, max=11,681, avg=167.00, stdev=448.35 clat (usec): min=3, max=19,552, avg=2217.48, stdev=1367.27 bw (KB/s) : min= 0, max=70143, per=1.27%, avg=6362.85, stdev=19236.22 write: io=128MB, bw=21,046KB/s, iops=5,261, runt= 6243msec slat (usec): min=4, max=11,678, avg=164.7...
2017 Oct 10
2
small files performance
...fio-test: Laying out IO file(s) (1 file(s) / 256MB) Jobs: 14 (f=13): [m(5),_(1),m(8),f(1),_(1)] [33.9% done] [1000KB/440KB/0KB /s] [125/55/0 iops] [eta 01m:59s] fio-test: (groupid=0, jobs=16): err= 0: pid=2051: Tue Oct 10 16:51:46 2017 read : io=43392KB, bw=733103B/s, iops=89, runt= 60610msec slat (usec): min=14, max=1992.5K, avg=177873.67, stdev=382294.06 clat (usec): min=768, max=6016.8K, avg=1871390.57, stdev=1082220.06 lat (usec): min=872, max=6630.6K, avg=2049264.23, stdev=1158405.41 clat percentiles (msec): | 1.00th=[ 20], 5.00th=[ 208], 10.00th=[ 457], 20.00th=...
2017 Oct 10
0
small files performance
...ile(s) (1 file(s) / 256MB) > Jobs: 14 (f=13): [m(5),_(1),m(8),f(1),_(1)] [33.9% done] [1000KB/440KB/0KB > /s] [125/55/0 iops] [eta 01m:59s] > fio-test: (groupid=0, jobs=16): err= 0: pid=2051: Tue Oct 10 16:51:46 2017 > read : io=43392KB, bw=733103B/s, iops=89, runt= 60610msec > slat (usec): min=14, max=1992.5K, avg=177873.67, stdev=382294.06 > clat (usec): min=768, max=6016.8K, avg=1871390.57, stdev=1082220.06 > lat (usec): min=872, max=6630.6K, avg=2049264.23, stdev=1158405.41 > clat percentiles (msec): > | 1.00th=[ 20], 5.00th=[ 208], 10.00...
2011 Nov 01
2
Removal/selecting specific rows in a dataframe conditional on 2 columns
...uot;set" "month" "stratum" "NAFO" [7] "unit.area" "time" "dur.set" "distance" "operation" "mean.d" [13] "min.d" "max.d" "temp.d" "slat" "slong" "spp" [19] "number" "weight" "elat" "elong" Each survey unit generates one set record, denoted by a 5 in column "record.t". Each species identified in this particular survey unit generates...
2007 Jun 26
4
[LLVMdev] Live Intervals Question
...nt. It's marked dead here: 28 %AL<dead> = MOV8rr %reg1024<kill>, %EAX<imp-def> MOV8rr %mreg(2)<d> %reg1024 %mreg(17)<d> But it's really dead at the point right after the call. I think the range [30,31) is correct, as far as I understand the slat numbering scheme. EAX has the same range, which seems correct. I don't know what you mean when you say EAX should be marked dead. It is, as far as live interval analysis is concerned, because it has the correct live range. Do you mean that it should be listed as dead in the printout of the C...
2007 Jun 27
0
[LLVMdev] Live Intervals Question
...; > 28 %AL<dead> = MOV8rr %reg1024<kill>, %EAX<imp-def> > MOV8rr %mreg(2)<d> %reg1024 %mreg(17)<d> > > But it's really dead at the point right after the call. I think > the range > [30,31) is correct, as far as I understand the slat numbering scheme. > EAX has the same range, which seems correct. I don't know what you > mean when you say EAX should be marked dead. It is, as far as live > interval analysis is concerned, because it has the correct live range. > > Do you mean that it should be listed as dead...
2007 Jun 26
0
[LLVMdev] Live Intervals Question
...> A registers are last used at instruction 40 and EAX is not defined > again > until instruction 48, which is the last use of register 1027. The > move to > register 1026 is entirely unnecessary -- why is it even there? Move to r1026 is marked dead. This is the artifact of translating CopyFromReg (of the call result) of EAX. It's harmless. EAX,inf = [30,31:0)[34,42:1)[50,54:2) 0 at 30 1@? 2 at 50 RAX,inf = [34,50:0)[50,54:1) 0@? 1 at 50 %reg1026,0 = [42,43:0) 0 at 42 %reg1027,0 = [46,50:0) 0@? 40 %reg1026<dead> = MOV32rr %EAX<kill> MOV32rr %reg1026<...
2007 Jun 26
3
[LLVMdev] Live Intervals Question
For the x86-64 target, I tried compiling a simple hello world. I don't understand the live interval information. Here's the machine instructions as dumped by LiveIntervalAnalysis: ********** MACHINEINSTRS ********** file hello.c line 3 b: 0 FNSTCW16m <fi#0>, 1, %NOREG, 0 FNSTCW16m <fi#0> 1 %mreg(0) 0 4 MOV8mi <fi#0>, 1, %NOREG, 1, 2 MOV8mi <fi#0> 1 %mreg(0) 1 2 8