Lines Matching full:will
239 /* at it. the real structure will be forced to the same alignment as */
240 /* the type "double." this change will mean that pre-2.1 netperfs */
286 those which do not, we will assume that the page size is 8192
566 /* we know that in the message passing routines that ntohl will have */
631 /* we know that in the message passing routines htonl will */
633 /* that when this happens, the proper order will go out on the */
993 /* this routine will disable any running timer */
1012 /* this routine will enable the interval timer and set things up so */
1013 /* that for a timed test the test will end at the proper time. it */
1025 /* if -DWANT_INTERVALS was used, we will use the ticking of the itimer to */
1026 /* tell us when the test is over. while the user will be specifying */
1040 /* how many times will the timer pop before the test is over? */
1133 netperf commandline will provide a "proper" CPU identifier. raj
1152 /* this routine will conver the string into an unsigned integer. it */
1155 /* enters 32M, then the number will be converted to 32 * 1024 * 1024. */
1156 /* If they inter 32m, the number will be converted to 32 * 1000 * */
1189 will imply seconds, u will imply microseconds. in the future n
1190 will imply nanoseconds but for now it will be ignored. if there is
1191 no suffix or an unrecognized suffix, it will be assumed the user
1219 /* this routine will allocate a circular list of buffers for either */
1220 /* send or receive operations. each of these buffers will be aligned */
1222 /* ring will be controlled by the setting of send_width. the buffers */
1223 /* will be filled with data from the file specified in fill_file. if */
1224 /* fill_file is an empty string, the buffers will not be filled with */
1334 /* this routine will dirty the first dirty_count bytes of the
1336 will go N bytes at a time, the only question is how large should N
1381 /* this routine will allocate a circular list of buffers for either */
1382 /* send or receive operations. each of these buffers will be aligned */
1384 /* ring will be controlled by the setting of send_width. the buffers */
1385 /* will be filled with data from the file specified in fill_file. if */
1386 /* fill_file is an empty string, the buffers will not be filled with */
1518 /* this routine will construct a ring of sendfile_ring_elt structs
1519 that the routine sendfile_tcp_stream() will use to get parameters
1520 to its calls to sendfile(). It will setup the ring to point at the
1524 if there is no file specified in a global -F option, we will create
1544 /* if the user has not specified a file with the -F option, we will
1554 ass-u-me-ing that malloc will return something at least aligned
1571 exit. unless/until shown to be a problem we will
1657 wonder? until something better comes-up, I think we will just
1686 /* display the contents of the request array to the user. it will */
1717 /* display the content of the response array to the user. it will */
1750 are bytes. If the format calls for bits, it will use SI units (10^)
1751 if the format calls for bytes, it will use CS units (2^)... This
1756 will use "x" which will, by default, do absolutely
1914 /* first, we say that we will be sending no more data on the */
1925 /* will be "just" like the recv_response() code */
1928 /* (which should not be happening, that we will receive the whole */
1955 bind_to_specific_processor will bind the calling process to the
1997 value will not tell you if you are bound vs unbound. */
2004 included by <sched.h>. If they are not there we will just
2126 /* we will call htonl on each of the int that compose the message to */
2127 /* be sent. the server-half of the connection will call the ntohl */
2188 /* we will call htonl on each of the int that compose the message to */
2189 /* be sent. the other half of the connection will call the ntohl */
2247 /* receive the remote's request on the control socket. we will put */
2249 /* calling routine. hopefully, this will go most of the way to */
2251 /* we will just punt the entire situation. */
2341 receive the remote's response on the control socket. we will put the
2343 routine. hopefully, this will go most of the way to insuring
2344 intervendor interoperability. if there are any problems, we will just
2391 /* (which should not be happening, that we will receive the whole */
2530 knows what it will do on other stacks, but it might be
2551 /* Now, we will find-out what the size actually became, and report */
2552 /* that back to the user. If the call fails, we will just report a -1 */
2587 /* seems that Solaris 10 GA bits will not give a canonical name
2629 connection, that may or may not be a good thing, so we will let the
2761 local addresses will be handled within the while loop. I suppose
2768 local endpoint, and we will not worry about mixed family types
2769 - presumeably the stack or other transition mechanisms will be
2839 /* the outer while conditions will deal with the case when we
2901 /* information will then either be displayed locally, or returned to */
2956 /* At first release, this information will be the same as that which */
2985 /* At first release, this information will be the same as that which */
2988 /* non-portable. A request is sent to the remote side, which will */
3075 /* We will calculate the thruput in libfmt units/second */
3122 /* We will calculate the thruput in libfmt units/second */
3296 /* performance, the CPU utilization will be skewed. raj 4/95 */
3319 /* we know that calibration will last at least 40 seconds, so go to */
3320 /* sleep for that long so the 60 second select in recv_response will */
3393 This will allow any time to be recorded to within an accuracy of
3562 /*+*+ Rick; this will overflow after ~2000 seconds, is that
3694 /* structure should contain a DL_BIND_ACK, which will have a full */
3798 /* will assume that we do not have to worry about it just now. */
4161 /* desirec confidence in the results. it will print the achieved */
