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
Benchmark --protect-lib runtime #1519
Comments
Original Redmine Comment See: This adds t_noprot_lib which is the same as t_prot_lib but without --protect-lib. These can be run against each other with or without tracing. For reference, on my system I see:
Note:
|
Original Redmine Comment Not sure if you are proposing to merge this...
With those feel free to merge (if you want to). |
Original Redmine Comment Yeah, sorry. The intent is to push this. I'm sure we'll want to evolve the benchmarking over time, but focusing on the I/O copy overhead (which is what this demonstrates) seems like a good place to start. Re: tabs, they snuck in because I was using this for Verilog formatting:
Squashed and pushed. |
Original Redmine Comment In 4.022. (& thanks for all your work in this release) |
Author Name: Todd Strader (@toddstrader)
Original Redmine Issue: 1519 from https://www.veripool.org
Original Assignee: Todd Strader (@toddstrader)
There's obviously overhead in shuttling data back and forth with --dpi-protect. We should use some large-ish design (maybe a processor) and --dpi-protect a part of it and compare runtimes. This will help us judge future performance enhancements to see if we're going in the right direction. Also, we can plug this whole thing into verilator_ext_tests.
The text was updated successfully, but these errors were encountered: