-
Notifications
You must be signed in to change notification settings - Fork 136
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
Shared core functionality for messages #149
Conversation
CI MessageYour results will arrive shortly |
CI MessageError: ERROR: Failed to fetch results from nimbnode30 |
@onvm try it now |
@onvm can we pass this pktgen test? |
CI MessageYour results will arrive shortly |
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.
@onvm can we pass this pktgen test?
CI Message
Run successful see results:
✔️ PR submitted to develop branch
✔️ Pktgen performance check passed
✔️ Speed Test performance check passed
✔️ Linter passed
[Results from nimbnode17]
-
Median TX pps for Pktgen: 6361442
-
Performance rating - 106.02% (compared to 6000000 average)
-
Median TX pps for Speed Tester: 38118038
-
Performance rating - 108.91% (compared to 35000000 average)
Yay to CI! I tested on cloudlab and got 13422053pps for pktgen. 4573120 rx/tx for 2 speed testers together. I'll test the specific message functionality later, but basic performance looks solid |
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.
Overall I approve, see comment for Monday discussion
@onvm can we show dennis our new features? |
CI MessageYour results will arrive shortly |
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.
@onvm can we show dennis our new features?
CI Message
Run successful see results:
✔️ PR submitted to develop branch
❌ PR drops Pktgen performance below minimum requirement
✔️ Speed Test performance check passed
✔️ Linter passed
[Results from nimbnode17]
-
Median TX pps for Pktgen: 6313672
-
Performance rating - 63.14% (compared to 10000000 average)
-
Median TX pps for Speed Tester: 41629903
-
Performance rating - 111.01% (compared to 37500000 average)
@dennisafa pktgen from CI will work if you merge develop into this branch |
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.
Good stuff, lets change this as we discussed in the meeting(only do the sleep check once one level up)
@onvm perf? |
@onvm perf |
CI MessageYour results will arrive shortly |
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.
@onvm perf
CI Message
Run successful see results:
✔️ PR submitted to develop branch
❌ PR drops Pktgen performance below minimum requirement
✔️ Speed Test performance check passed
✔️ Linter passed
[Results from nimbnode17]
-
Median TX pps for Pktgen: 0
Performance rating - 0.00% (compared to 10000000 average) -
Median TX pps for Speed Tester: 40242712
Performance rating - 100.61% (compared to 40000000 average)
@onvm i believe in you |
CI MessageYour results will arrive shortly |
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.
@onvm i believe in you
CI Message
Run successful see results:
✔️ PR submitted to develop branch
❌ PR drops Pktgen performance below minimum requirement
✔️ Speed Test performance check passed
✔️ Linter passed
[Results from nimbnode17]
-
Median TX pps for Pktgen: 6445082
Performance rating - 64.45% (compared to 10000000 average) -
Median TX pps for Speed Tester: 40262852
Performance rating - 100.66% (compared to 40000000 average)
@onvm how's it goin pktgen |
CI MessageYour results will arrive shortly |
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.
@onvm how's it goin pktgen
CI Message
Run successful see results:
✔️ PR submitted to develop branch
❌ PR drops Pktgen performance below minimum requirement
✔️ Speed Test performance check passed
✔️ Linter passed
[Results from nimbnode17]
-
Median TX pps for Pktgen: 0
Performance rating - 0.00% (compared to 10000000 average) -
Median TX pps for Speed Tester: 40340438
Performance rating - 100.85% (compared to 40000000 average)
@onvm if you fail I'll catch you now! |
CI MessageYour results will arrive shortly |
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.
@onvm if you fail I'll catch you now!
CI Message
Run successful see results:
✔️ PR submitted to develop branch
❌ PR drops Pktgen performance below minimum requirement
✔️ Speed Test performance check passed
✔️ Linter passed
[Results from nimbnode17]
-
Median TX pps for Pktgen: 6354164
Performance rating - 63.54% (compared to 10000000 average) -
Median TX pps for Speed Tester: 40907748
Performance rating - 102.27% (compared to 40000000 average)
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.
@dennisafa I approve just add a macro for msg threshold and should be good to merge
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.
Cool will merge soon, although please add a reamde note here, nf wakes up either when packets or a message arrives.
@dennisafa just add the https://github.com/sdnfv/openNetVM/pull/151/files changes into this pr |
oops. got it. |
CI MessageYour results will arrive shortly |
CI MessageError: Failed to parse Speed Tester stats |
CI MessageYour results will arrive shortly |
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.
Testing
CI Message
Run successful see results:
✔️ PR submitted to develop branch
❌ PR drops Pktgen performance below minimum requirement
✔️ Speed Test performance check passed
✔️ MTCP performance check passed
✔️ Linter passed
[Results from nimbnode17]
-
Median TX pps for Pktgen: 6408064
Performance rating - 64.08% (compared to 10000000 average) -
Median TX pps for Speed Tester: 40242298
Performance rating - 100.61% (compared to 40000000 average) -
Median TX pps for mtcp: 0.236000
-
Performance rating - 102.61% (compared to 0.230000 average)
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.
Let's goooooooo! First successful mTCP CI run. I also have been testing on cloudlab, when I merged develop, and disabled flow table I got 14746136pps Pktgen, and 12895796pps with ft macro enabled, which is normal. Created a 4 speed tester chain with performance of ~17664647 pps tx on all 4, and got almost 52mil pps just running one speed_tester. Also, not a change request, just a question, was there a performance benefit to moving this code out of onvm_nflib_dequeue_packets
, or did it just make more logical sense? I ask this because there doesn't seem to be a whole lot changed, except for the condition definition.
awesome, im excited CI has mTCP results now. no real performance benefit,
just the fact that the semwait call is logically equivalent so having it in
both dequeue_messages and dequeue_packets would be extra
…On Thu, Jul 25, 2019 at 6:45 PM Kevin Deems ***@***.***> wrote:
***@***.**** approved this pull request.
Let's goooooooo! First successful mTCP CI run. I also have been testing on
cloudlab, when I merged develop, and disabled flow table I got 14746136pps
Pktgen, and 12895796pps with ft macro enabled, which is normal. Created a 4
speed tester chain with performance of ~17664647 pps tx on all 4, and got
almost 52mil pps just running one speed_tester. Also, not a change request,
just a question, was there a performance benefit to moving this code out of
onvm_nflib_dequeue_packets, or did it just make more logical sense? I ask
this because there doesn't seem to be a whole lot changed, except for the
condition definition.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#149?email_source=notifications&email_token=AH3EIZW6GDMOG5PBQUKBPTTQBIUJ7A5CNFSM4H3KRXKKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOB7UOMZY#pullrequestreview-266921575>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AH3EIZTUNKSZLJL325TGXLTQBIUJ7ANCNFSM4H3KRXKA>
.
|
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.
Noice
Adds functionality to sleep when no messages are enqueued onto an nf's message ring.
Summary:
This is functionality I implemented as part of the larger mTCP project, in which an NF constantly receives lots of messages. This works exactly the same way as sleeping on an empty packet ring.
Usage:
Run the manager with shared CPU enabled.
Merging notes:
TODO before merging :
Test Plan:
Tested by sending a large influx of messages to an NF running in shared cpu mode. Also tested with multiple NF's on the same core. Checked htop CPU usage to verify proper sleeping when no messages were being sent.
Review:
Review checklist:
Sanity checks, assigned to @koolzz @kevindweb
/onvm
and/examples
directoriesCode style, assigned to @koolzz @kevindweb
Code design, assigned to @koolzz @kevindweb
Performance, assigned to @koolzz @kevindweb
Documentation, assigned to @koolzz @kevindweb