-
Notifications
You must be signed in to change notification settings - Fork 166
2322 scitag source destination #2359
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
Conversation
In the new SciTag specification, the content of the emitted firefly should always be created from the data sender point of view. For HTTP PUT: the srcIp is the client, dstIP is the server, sentBytes=socketReceivedBytes (~=fileSize), receivedBytes=socketSentBytes (~=0) For HTTP GET: the srcIP is the server, dstIP is the client, sentBytes=socketSentBytes(~=fileSize) receivedBytes=socketReceivedBytes(~=0) The distinction is therefore done via the pmark.appname CGI that is equal to "http-get" if the client request is a GET request or equal to "http-put" if not.
|
Here are the results of the tests. HTTP TPC PULL: Active server emits the firefly, Source port is passive server, destinationPort is activeServer, sent~=fileSize, received~=0 HTTP TPC PULL with HTTP TPC PUSH: HTTP PUT: HTTP GET: All good! |
abh3
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We've already tested this and it's OK. However, we need @amadio to figure out why Alpine build fails before we fully approve this.
|
This is fine to be merged, the Alpine problem is due to git issues on GitHub's side. I will rebase and push again to run the CI on Alpine, then merge. You don't need to do anything. Cheers, |
Includes @abh3 PMark implementation adaptation + HTTP + HTTP-TPC PMark modification