Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate the possible use of TCP_INFO instead of web100/web10g #141

Open
aaronmbr opened this issue Mar 31, 2015 · 4 comments
Open

Investigate the possible use of TCP_INFO instead of web100/web10g #141

aaronmbr opened this issue Mar 31, 2015 · 4 comments

Comments

@aaronmbr
Copy link
Contributor

Original issue 141 created by aaronmbr on 2014-03-25T08:59:43.000Z:

It would be interesting to see how much we could use with TCP_INFO instead of web100. i.e. if we wanted to release a version of NDT that didn’t require a web100 kernel, what stats could we still collect, and would that be useful? Presumably, this would require looking at how the web100 variables get used to calculate the various stats, and to see what would still be collectible using just the TCP_INFO stats.

@aaronmbr
Copy link
Contributor Author

Comment #1 originally posted by aaronmbr on 2014-06-11T11:32:14.000Z:

<empty>

@aaronmbr
Copy link
Contributor Author

Comment #2 originally posted by aaronmbr on 2014-06-25T08:36:12.000Z:

<empty>

@aaronmbr
Copy link
Contributor Author

Comment #3 originally posted by aaronmbr on 2014-07-02T11:16:36.000Z:

All collected information related to this ticket are on wiki page:
https://code.google.com/p/ndt/wiki/TCP_INFOvsWeb100Web10g

@aaronmbr
Copy link
Contributor Author

Comment #4 originally posted by aaronmbr on 2014-07-04T07:40:28.000Z:

<empty>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant