Searched refs:around (Results 1 – 25 of 526) sorted by relevance
12345678910>>...22
| /trueos/usr.bin/tr/tests/ |
| HD | regress.06.out | 2 Take one down and pass it around - ?? bottles of beer on the wall. 4 Take one down and pass it around - ?? bottles of beer on the wall. 7 Take one down and pass it around - ? bottle of beer on the wall. 9 Take it down and pass it around - NO MORE bottles of beer on the wall!!!
|
| HD | regress2.in | 2 Take one down and pass it around - 99 bottles of beer on the wall. 4 Take one down and pass it around - 98 bottles of beer on the wall. 7 Take one down and pass it around - 1 bottle of beer on the wall. 9 Take it down and pass it around - NO MORE bottles of beer on the wall!!!
|
| /trueos/cddl/contrib/dtracetoolkit/Examples/ |
| HD | php_cputime_example.txt | 36 The exclusive subroutine on-CPU times show that func_a() spent around 74 41 The inclusive subroutine on-CPU times show that func_c() spent around 39 42 microseconds on-CPU, func_b() spent around 87 microseconds on-CPU and 43 func_a() spent around 210 microseconds. This inclusive time includes the time
|
| HD | sh_cputime_example.txt | 40 The exclusive function on-CPU times show that func_a() spent around 268.4 ms 44 The inclusive function on-CPU times show that func_c() spent around 1.3 45 seconds on-CPU, func_b() spent around 1.9 seconds, and func_a() spent around
|
| HD | sampleproc_example.txt | 58 The above sample was around 10 seconds long. During this time, there were 59 around 4000 samples (checking the COUNT column), this is due to
|
| HD | pl_cputime_example.txt | 33 The exclusive subroutine on-CPU times show that func_a() spent around 264.2 ms 37 The inclusive subroutine on-CPU times show that func_c() spent around 799.0 ms 38 on-CPU, func_b() spent around 1.3 seconds, and func_a() spent around 1.6
|
| HD | diskhits_example.txt | 50 Ok, so the file was read evently with each access around 32 to 63 Kb in size, 98 The difference is dramatic. This time only 29 Mb is read, leaving around
|
| HD | dvmstat_example.txt | 65 Now we run dvmstat on a tar command. Here we tar around 50Mb of files, 66 so the command takes around 20 seconds to complete,
|
| HD | js_cputime_example.txt | 54 spent around 83,000 microseconds on-CPU. This time excludes time spent in 57 The inclusive subroutine on-CPU times show that func_a spent around 0.5
|
| HD | tcpstat_example.txt | 21 We can see the TCP_in value rise to around 3 Mb/sec as the download occurs.
|
| HD | rb_cputime_example.txt | 67 spent around 0.4 seconds on-CPU. This time excludes time spent in other 70 The inclusive function on-CPU times show that func_a spent around 4.4
|
| HD | hotspot_example.txt | 5 around the 9000 to 10999 Mb range on the source disk (102,0), and was
|
| HD | cswstat_example.txt | 22 of context switches per second from around 270 to over 2000. The time
|
| HD | runocc_example.txt | 19 The run queue occupancy is around 85%, meaning most of the time there
|
| D | tcptop_snv_example.txt | 26 that the screen does not clear. Some traffic was captured, around 110 Kbytes
|
| /trueos/contrib/gcc/config/mips/ |
| HD | mips.opt | 86 Work around certain R4000 errata 90 Work around certain R4400 errata 94 Work around errata for early SB-1 revision 2 cores 98 Work around certain VR4120 errata 102 Work around VR4130 mflo/mfhi errata 106 Work around an early 4300 hardware bug
|
| /trueos/contrib/ntp/html/build/hints/ |
| HD | solaris.xtra.4023118 | 27 Ultra which was discovered to tick around 142,980,806 (+/- 10) times 30 Work around:
|
| /trueos/cddl/contrib/dtracetoolkit/Notes/ |
| HD | dtruss_notes.txt | 58 For every syscall, the elapsed time is around 10 us (microseconds) slower 63 Ok, so for the above output we can tell that each elapsed time is around 10 us 86 Now the time difference is around 40 us, and fairly consistant.
|
| /trueos/contrib/gcc/config/ |
| HD | t-darwin | 17 # Pass -fno-tree-dominator-opts to work around bug 26840. 32 # works around this by not having any temporary file names.
|
| /trueos/lib/libz/contrib/asm686/ |
| HD | README.686 | 10 PPro's speed traps. My own tests show a speedup of around 10-20% at 40 gcc's generated code had caught up with it sometime around gcc 2.95
|
| /trueos/contrib/binutils/gas/config/ |
| HD | tc-i386.h | 252 #define md_do_align(n, fill, len, max, around) \ argument 261 goto around; \
|
| /trueos/sys/ufs/ffs/ |
| HD | ffs_tables.c | 43 int around[9] = { variable
|
| /trueos/contrib/netbsd-tests/usr.bin/grep/ |
| HD | d_context_b.in | 2 Dave was a happy pig who wandered around the orchard eating
|
| /trueos/cddl/contrib/dtracetoolkit/Docs/ |
| HD | Faq | 102 around 10% of a CPU to do so. 106 going to hurt and there is no way around it. Scripts such as cputimes 107 and cpudists trace very frequent events, and can chew around 5% of
|
| /trueos/bin/sh/tests/expansion/ |
| HD | ifs2.0 | 9 # Add a character to work around command substitution's removal of
|
12345678910>>...22