Lines Matching full:will
114 specifying one value without a comma will set both parms to that\n\
115 value, specifying a value with a leading comma will set just the second\n\
116 parm, a value with a trailing comma will set just the first. To set\n\
142 /* This routine will create a data (listen) socket with the apropriate */
148 /* and type will be either SOCK_STREAM or SOCK_DGRAM */
183 /* that the socket buffers be altered, we will try to find-out what */
185 /* we will set the values to -1 to indicate that. */
244 /* send-size greater than our send window. this will insure that we */
246 /* of the transport. This buffer will be malloc'd after we have found */
247 /* the size of the local senc socket buffer. We will want to deal */
329 /* size is not available, we will set the send size to 4KB - no */
359 /* calibrate the cpu(s). We will perform this task within the tests */
361 /* calibrate_local_cpu will return rather quickly as it will have */
362 /* nothing to do. If local_cpu_rate is zero, then we will go through */
372 /* not specify any of the parameters, they will be passed as 0, which */
373 /* will indicate to the remote that no changes beyond the system's */
374 /* default should be used. Alignment is the exception, it will */
375 /* default to 1, which will be no alignment alterations. */
404 /* The response from the remote will contain all of the relevant */
405 /* socket parameters for this test type. We will put them back into */
407 /* remote will have calibrated CPU if necessary, and will have done */
408 /* all the needed set-up we will have calibrated the cpu locally */
409 /* before sending the request, and will grab the counter value right */
410 /* after the connect returns. The remote will grab the counter right */
461 /* The cpu_start routine will grab the current time and possibly */
468 /* controlled by time, the byte count check will always return false. */
469 /* When the test is controlled by byte count, the time test will */
471 /* expression will go false and we will stop sending data. */
484 /* them cleanly into the cache. The clean ones will follow any dirty */
519 /* of the bufferspace, so we will mod the number of messages sent */
538 /* this call will always give us the elapsed time for the test, and */
539 /* will also store-away the necessaries for cpu utilization */
546 /* Get the statistics from the remote end. The remote will have */
548 /* wasn't supposed to care, it will return obvious values. */
615 /* has specified zero-level verbosity, we will just print the */
617 /* user has requested verbosity level 1, he will get the basic */
619 /* of greater than 1, we will display a veritable plethora of */
675 /* moment, I do not wish to figure-out all the formatting, so I will */
680 /* The user wanted to know it all, so we will give it to him. */
681 /* This information will include as much as we can find about */
749 /* socket size defaults are to be used, then the initiator will have */
750 /* sent us 0's. If the socket sizes cannot be changed, then we will */
753 /* reason, we will drop back ten yards and punt. */
799 /* once the socket has been created, we will set the response values */
900 /* then we must call the calibrate routine, which will return the max */
902 /* something went wrong with the calibration, we will return a -1 to */
925 /* Let's just punt. The remote will be given some information */
930 /* Now it's time to start receiving data on the connection. We will */
935 /* The loop will exit when the sender does a shutdown, which will */
941 /* them cleanly into the cache. The clean ones will follow any dirty */
983 /* The loop now exits due to zero bytes received. we will have */
1165 /* calibrate the cpu(s). We will perform this task within the tests */
1167 /* calibrate_local_cpu will return rather quickly as it will have */
1168 /* nothing to do. If local_cpu_rate is zero, then we will go through */
1178 /* not specify any of the parameters, they will be passed as 0, which */
1179 /* will indicate to the remote that no changes beyond the system's */
1180 /* default should be used. Alignment is the exception, it will */
1181 /* default to 8, which will be no alignment alterations. */
1207 /* The response from the remote will contain all of the relevant */
1208 /* socket parameters for this test type. We will put them back into */
1210 /* remote will have calibrated CPU if necessary, and will have done */
1211 /* all the needed set-up we will have calibrated the cpu locally */
1212 /* before sending the request, and will grab the counter value right */
1213 /* after the connect returns. The remote will grab the counter right */
1266 /* The cpu_start routine will grab the current time and possibly */
1273 /* controlled by time, the byte count check will always return false. */
1274 /* When the test is controlled by byte count, the time test will */
1276 /* expression will go false and we will stop sending data. I think I */
1278 /* will not do that just yet... One other question is whether or not */
1283 /* the request will be sent at one shot. */
1346 /* this call will always give us the elapsed time for the test, and */
1347 /* will also store-away the necessaries for cpu utilization */
1352 /* Get the statistics from the remote end. The remote will have */
1354 /* wasn't supposed to care, it will return obvious values. */
1396 /* since calc_service demand is doing ms/Kunit we will */
1416 /* since calc_service demand is doing ms/Kunit we will */
1430 /* has specified zero-level verbosity, we will just print the */
1432 /* user has requested verbosity level 1, he will get the basic */
1434 /* of greater than 1, we will display a veritable plethora of */
1499 /* moment, I do not wish to figure-out all the formatting, so I will */
1504 /* The user wanted to know it all, so we will give it to him. */
1505 /* This information will include as much as we can find about */
1650 /* if the user supplied a cpu rate, this call will complete rather */
1651 /* quickly, otherwise, the cpu rate will be retured to us for */
1652 /* possible display. The Library will keep it's own copy of this data */
1653 /* for use elsewhere. We will only display it. (Does that make it */
1732 /* them cleanly into the cache. The clean ones will follow any dirty */
1783 /* This is a timed test, so the remote will be returning to us after */
1861 /* has specified zero-level verbosity, we will just print the */
1863 /* user has requested verbosity level 1, he will get the basic */
1865 /* of greater than 1, we will display a veritable plethora of */
1966 /* socket size defaults are to be used, then the initiator will have */
1967 /* sent us 0's. If the socket sizes cannot be changed, then we will */
1970 /* reason, we will drop back ten yards and punt. */
2028 /* once the socket has been created, we will set the response values */
2068 /* then we must call the calibrate routine, which will return the max */
2070 /* something went wrong with the calibration, we will return a -1 to */
2075 /* We will pass the rate into the calibration routine. If the */
2076 /* user did not specify one, it will be 0.0, and we will do a */
2077 /* "real" calibration. Otherwise, all it will really do is */
2094 /* Now it's time to start receiving data on the connection. We will */
2099 /* The loop will exit when the timer pops, or if we happen to recv a */
2150 /* We will count the "off" message that got us out of the loop */
2342 /* calibrate the cpu(s). We will perform this task within the tests */
2344 /* calibrate_local_cpu will return rather quickly as it will have */
2345 /* nothing to do. If local_cpu_rate is zero, then we will go through */
2348 /* local_cpu_rate will be set to -1. */
2357 /* not specify any of the parameters, they will be passed as 0, which */
2358 /* will indicate to the remote that no changes beyond the system's */
2359 /* default should be used. Alignment is the exception, it will */
2360 /* default to 8, which will be no alignment alterations. */
2386 /* The response from the remote will contain all of the relevant */
2387 /* socket parameters for this test type. We will put them back into */
2389 /* remote will have calibrated CPU if necessary, and will have done */
2390 /* all the needed set-up we will have calibrated the cpu locally */
2391 /* before sending the request, and will grab the counter value right */
2392 /* after the connect returns. The remote will grab the counter right */
2415 /* Connect up to the remote port on the data socket. This will set */
2455 /* The cpu_start routine will grab the current time and possibly */
2462 /* controlled by time, the byte count check will always return false. */
2463 /* When the test is controlled by byte count, the time test will */
2465 /* expression will go false and we will stop sending data. I think I */
2467 /* will not do that just yet... One other question is whether or not */
2487 /* receive the response. with DG we will get it all, or nothing */
2517 /* will not sleep if the time would be less than a */
2559 /* this call will always give us the elapsed time for the test, and */
2560 /* will also store-away the necessaries for cpu utilization */
2565 /* Get the statistics from the remote end. The remote will have */
2567 /* wasn't supposed to care, it will return obvious values. */
2606 /* since calc_service demand is doing ms/Kunit we will */
2626 /* since calc_service demand is doing ms/Kunit we will */
2640 /* has specified zero-level verbosity, we will just print the */
2642 /* user has requested verbosity level 1, he will get the basic */
2644 /* of greater than 1, we will display a veritable plethora of */
2711 /* moment, I do not wish to figure-out all the formatting, so I will */
2716 /* The user wanted to know it all, so we will give it to him. */
2717 /* This information will include as much as we can find about */
2777 /* socket size defaults are to be used, then the initiator will have */
2778 /* sent us 0's. If the socket sizes cannot be changed, then we will */
2781 /* reason, we will drop back ten yards and punt. */
2850 /* once the socket has been created, we will set the response values */
2891 /* then we must call the calibrate routine, which will return the max */
2893 /* something went wrong with the calibration, we will return a 0.0 to */
2910 /* Now it's time to start receiving data on the connection. We will */
3071 /* socket size defaults are to be used, then the initiator will have */
3072 /* sent us 0's. If the socket sizes cannot be changed, then we will */
3075 /* reason, we will drop back ten yards and punt. */
3139 /* once the socket has been created, we will set the response values */
3189 /* then we must call the calibrate routine, which will return the max */
3191 /* something went wrong with the calibration, we will return a 0.0 to */
3213 /* Let's just punt. The remote will be given some information */
3224 /* Now it's time to start receiving data on the connection. We will */
3229 /* The loop will exit when the sender does a shutdown, which will */
3393 /* the first will set both to that value. Specifying only the */
3394 /* second will leave the first untouched. To change only the */
