Home | History | Annotate | Download | only in netperf

Lines Matching full:some

38  /* at some point, I might want to go-in and see if I really need all */
482 /* we want to dirty some
483 /* we are about to send. we may also want to bring some number of */
485 /* ones into the cache. at some point, we might want to replace */
577 /* Of course, some of the information might be bogus because */
673 /* it would be a good thing to include information about some of the */
757 /* the actual error we encountered, rather than some bogus unexpected */
782 /* can put in OUR values !-) At some point, we may want to nail this */
797 /* create_unix_socket expects to find some things in the global */
912 /* before we send the response back to the initiator, pull some of */
925 /* Let's just punt. The remote will be given some information */
939 /* we want to dirty some number of consecutive integers in the buffer */
940 /* we are about to recv. we may also want to bring some number of */
1386 /* Of course, some of the information might be bogus because */
1497 /* it would be a good thing to include information about some of the */
1689 /* some of the returned socket buffer information for user display. */
1722 /* but we still need some sort of end of test trigger on the receive */
1730 /* we want to dirty some number of consecutive integers in the buffer */
1731 /* we are about to send. we may also want to bring some number of */
1770 /* call the sleep routine for some milliseconds, if our */
1974 /* the actual error we encountered, rather than some bogus unexpected */
2011 /* can put in OUR values !-) At some point, we may want to nail this */
2026 /* create_unix_socket expects to find some things in the global */
2087 /* before we send the response back to the initiator, pull some of */
2220 /* space for a maximally aligned, maximally sized message. At some */
2503 /* now we do some arithmatic on the two timevals */
2514 /* at this point, we may wish to sleep for some period of */
2596 /* Of course, some of the information might be bogus because */
2709 /* it would be a good thing to include information about some of the */
2785 /* the actual error we encountered, rather than some bogus unexpected */
2832 /* can put in OUR values !-) At some point, we may want to nail this */
2848 /* create_unix_socket expects to find some things in the global */
2902 /* before we send the response back to the initiator, pull some of */
3079 /* the actual error we encountered, rather than some bogus unexpected */
3106 /* at some point, these need to come to us from the remote system */
3122 /* can put in OUR values !-) At some point, we may want to nail this */
3137 /* create_unix_socket expects to find some things in the global */
3201 /* before we send the response back to the initiator, pull some of */
3213 /* Let's just punt. The remote will be given some information */
3405 /* pipes. at some point, there should be some error checking. */