Lines Matching full:will
135 specifying one value without a comma will set both parms to that\n\
136 value, specifying a value with a leading comma will set just the second\n\
137 parm, a value with a trailing comma will set just the first. To set\n\
379 /* send-size greater than our send window. this will insure that we */
381 /* of the transport. This buffer will be malloc'd after we have found */
382 /* the size of the local senc socket buffer. We will want to deal */
438 /* complete_addrinfos will either succede or exit the process */
458 /* (no confidence is the default) then we will only go though the */
488 /* size is not available, we will set the send size to 4KB - no */
524 /* calibrate the cpu(s). We will perform this task within the tests */
526 /* calibrate_local_cpu will return rather quickly as it will have */
527 /* nothing to do. If local_cpu_rate is zero, then we will go through */
537 /* not specify any of the parameters, they will be passed as 0, which */
538 /* will indicate to the remote that no changes beyond the system's */
539 /* default should be used. Alignment is the exception, it will */
540 /* default to 1, which will be no alignment alterations. */
578 /* The response from the remote will contain all of the relevant */
579 /* socket parameters for this test type. We will put them back into */
581 /* remote will have calibrated CPU if necessary, and will have done */
582 /* all the needed set-up we will have calibrated the cpu locally */
583 /* before sending the request, and will grab the counter value right*/
584 /* after the connect returns. The remote will grab the counter right*/
663 /* The cpu_start routine will grab the current time and possibly */
695 /* controlled by time, the byte count check will always return false. */
696 /* When the test is controlled by byte count, the time test will */
698 /* expression will go false and we will stop sending data. */
705 /* them cleanly into the cache. The clean ones will follow any dirty */
776 /* of the bufferspace, so we will mod the number of messages sent */
799 /* The test server will signal to us when it wants to shutdown.
815 /* this call will always give us the elapsed time for the test, and */
816 /* will also store-away the necessaries for cpu utilization */
827 /* Get the statistics from the remote end. The remote will have */
829 /* wasn't supposed to care, it will return obvious values. */
902 /* if debugging is on, calculate_confidence will print-out the */
918 /* will be making. so, we should extract what the calcuated values */
933 /* has specified zero-level verbosity, we will just print the */
935 /* user has requested verbosity level 1, he will get the basic */
937 /* of greater than 1, we will display a veritable plethora of */
1018 /* moment, I do not wish to figure-out all the formatting, so I will */
1023 /* The user wanted to know it all, so we will give it to him. */
1024 /* This information will include as much as we can find about */
1122 /* socket size defaults are to be used, then the initiator will have */
1123 /* sent us 0's. If the socket sizes cannot be changed, then we will */
1126 /* reason, we will drop back ten yards and punt. */
1156 /* once the socket has been created, we will set the response values */
1243 /* then we must call the calibrate routine, which will return the max */
1245 /* something went wrong with the calibration, we will return a -1 to */
1283 /* Let's just punt. The remote will be given some information */
1309 /* Now it's time to start receiving data on the connection. We will */
1314 /* The loop will exit when the sender does a shutdown, which will */
1320 /* them cleanly into the cache. The clean ones will follow any dirty */
1517 /* send-size greater than our send window. this will insure that we */
1519 /* of the transport. This buffer will be malloc'd after we have found */
1520 /* the size of the local senc socket buffer. We will want to deal */
1597 /* (no confidence is the default) then we will only go though the */
1618 /* size is not available, we will set the send size to 4KB - no */
1654 /* calibrate the cpu(s). We will perform this task within the tests */
1656 /* calibrate_local_cpu will return rather quickly as it will have */
1657 /* nothing to do. If local_cpu_rate is zero, then we will go through */
1667 /* not specify any of the parameters, they will be passed as 0, which */
1668 /* will indicate to the remote that no changes beyond the system's */
1669 /* default should be used. Alignment is the exception, it will */
1670 /* default to 1, which will be no alignment alterations. */
1708 /* The response from the remote will contain all of the relevant */
1709 /* socket parameters for this test type. We will put them back into */
1711 /* remote will have calibrated CPU if necessary, and will have done */
1712 /* all the needed set-up we will have calibrated the cpu locally */
1713 /* before sending the request, and will grab the counter value right*/
1714 /* after the connect returns. The remote will grab the counter right*/
1808 /* The cpu_start routine will grab the current time and possibly */
1840 /* controlled by time, the byte count check will always return false. */
1841 /* When the test is controlled by byte count, the time test will */
1843 /* expression will go false and we will stop sending data. */
1850 /* them cleanly into the cache. The clean ones will follow any dirty */
1928 /* of the bufferspace, so we will mod the number of messages sent */
1949 /* signal the server that we are all done writing, this will
1957 /* The test server will initiate closure of all associations
1966 * This means that anything comming in on that socket will be a shutdown.
1979 /* this call will always give us the elapsed time for the test, and */
1980 /* will also store-away the necessaries for cpu utilization */
1992 /* Get the statistics from the remote end. The remote will have */
1994 /* wasn't supposed to care, it will return obvious values. */
2067 /* if debugging is on, calculate_confidence will print-out the */
2083 /* will be making. so, we should extract what the calcuated values */
2098 /* has specified zero-level verbosity, we will just print the */
2100 /* user has requested verbosity level 1, he will get the basic */
2102 /* of greater than 1, we will display a veritable plethora of */
2183 /* moment, I do not wish to figure-out all the formatting, so I will */
2188 /* The user wanted to know it all, so we will give it to him. */
2189 /* This information will include as much as we can find about */
2285 /* socket size defaults are to be used, then the initiator will have */
2286 /* sent us 0's. If the socket sizes cannot be changed, then we will */
2289 /* reason, we will drop back ten yards and punt. */
2319 /* once the socket has been created, we will set the response values */
2413 /* then we must call the calibrate routine, which will return the max */
2415 /* something went wrong with the calibration, we will return a -1 to */
2451 /* Now it's time to start receiving data on the connection. We will */
2456 /* The loop will exit when the sender does a shutdown, which will */
2462 /* them cleanly into the cache. The clean ones will follow any dirty */
2532 * will close all associations on this socket
2678 /* complete_addrinfos will either succede or exit the process */
2701 /* (no confidence is the default) then we will only go though the */
2750 /* calibrate the cpu(s). We will perform this task within the tests */
2752 /* calibrate_local_cpu will return rather quickly as it will have */
2753 /* nothing to do. If local_cpu_rate is zero, then we will go through */
2763 /* not specify any of the parameters, they will be passed as 0, which */
2764 /* will indicate to the remote that no changes beyond the system's */
2765 /* default should be used. Alignment is the exception, it will */
2766 /* default to 8, which will be no alignment alterations. */
2797 /* The response from the remote will contain all of the relevant */
2798 /* socket parameters for this test type. We will put them back into */
2800 /* remote will have calibrated CPU if necessary, and will have done */
2801 /* all the needed set-up we will have calibrated the cpu locally */
2802 /* before sending the request, and will grab the counter value right*/
2803 /* after the connect returns. The remote will grab the counter right*/
2872 /* The cpu_start routine will grab the current time and possibly */
2896 /* controlled by time, the byte count check will always return false. */
2897 /* When the test is controlled by byte count, the time test will */
2899 /* expression will go false and we will stop sending data. I think I */
2901 /* will not do that just yet... One other question is whether or not */
2922 /* the request will be sent at one shot. */
3033 /* this call will always give us the elapsed time for the test, and */
3034 /* will also store-away the necessaries for cpu utilization */
3040 /* Get the statistics from the remote end. The remote will have */
3042 /* will return obvious values. */
3071 /* since calc_service demand is doing ms/Kunit we will */
3086 /* since calc_service demand is doing ms/Kunit we will */
3110 /* if debugging is on, calculate_confidence will print-out the */
3137 /* has specified zero-level verbosity, we will just print the */
3139 /* user has requested verbosity level 1, he will get the basic */
3141 /* of greater than 1, we will display a veritable plethora of */
3233 /* moment, I do not wish to figure-out all the formatting, so I will */
3240 /* The user wanted to know it all, so we will give it to him. */
3241 /* This information will include as much as we can find about */
3307 /* socket size defaults are to be used, then the initiator will have */
3308 /* sent us 0's. If the socket sizes cannot be changed, then we will */
3311 /* reason, we will drop back ten yards and punt. */
3366 /* once the socket has been created, we will set the response values */
3426 /* then we must call the calibrate routine, which will return the max */
3428 /* something went wrong with the calibration, we will return a 0.0 to */
3455 /* Let's just punt. The remote will be given some information */
3461 /* we do not need events on a 1-to-1 RR test. The test will finish
3487 /* Now it's time to start receiving data on the connection. We will */
3492 /* The loop will exit when we hit the end of the test time, or when */
3764 /* (no confidence is the default) then we will only go though the */
3801 /* calibrate the cpu(s). We will perform this task within the tests */
3803 /* calibrate_local_cpu will return rather quickly as it will have */
3804 /* nothing to do. If local_cpu_rate is zero, then we will go through */
3814 /* not specify any of the parameters, they will be passed as 0, which */
3815 /* will indicate to the remote that no changes beyond the system's */
3816 /* default should be used. Alignment is the exception, it will */
3817 /* default to 8, which will be no alignment alterations. */
3849 /* The response from the remote will contain all of the relevant */
3850 /* socket parameters for this test type. We will put them back into */
3852 /* remote will have calibrated CPU if necessary, and will have done */
3853 /* all the needed set-up we will have calibrated the cpu locally */
3854 /* before sending the request, and will grab the counter value right*/
3855 /* after the connect returns. The remote will grab the counter right*/
3934 /* The cpu_start routine will grab the current time and possibly */
3958 /* controlled by time, the byte count check will always return false. */
3959 /* When the test is controlled by byte count, the time test will */
3961 /* expression will go false and we will stop sending data. I think I */
3963 /* will not do that just yet... One other question is whether or not */
3987 /* the request will be sent at one shot. */
3994 * this will do for the fist take. vlad
4087 /* this call will always give us the elapsed time for the test, and */
4088 /* will also store-away the necessaries for cpu utilization */
4094 /* Get the statistics from the remote end. The remote will have */
4096 /* will return obvious values. */
4125 /* since calc_service demand is doing ms/Kunit we will */
4140 /* since calc_service demand is doing ms/Kunit we will */
4164 /* if debugging is on, calculate_confidence will print-out the */
4191 /* has specified zero-level verbosity, we will just print the */
4193 /* user has requested verbosity level 1, he will get the basic */
4195 /* of greater than 1, we will display a veritable plethora of */
4287 /* moment, I do not wish to figure-out all the formatting, so I will */
4294 /* The user wanted to know it all, so we will give it to him. */
4295 /* This information will include as much as we can find about */
4364 /* socket size defaults are to be used, then the initiator will have */
4365 /* sent us 0's. If the socket sizes cannot be changed, then we will */
4368 /* reason, we will drop back ten yards and punt. */
4416 /* once the socket has been created, we will set the response values */
4482 /* then we must call the calibrate routine, which will return the max */
4484 /* something went wrong with the calibration, we will return a 0.0 to */
4533 /* Now it's time to start receiving data on the connection. We will */
4538 /* The loop will exit when we hit the end of the test time, or when */
4562 * We can get away with this because the client will establish all
4564 * will not have EOR thus will we will not send a response untill
4723 /* the first will set both to that value. Specifying only the */
4724 /* second will leave the first untouched. To change only the */
4830 /* buffer. This will be the number of */
4838 /* we want to do copy avoidance and will set */
