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

dpdk: add warning in configuration phase and minor DPDK refactoring v1 #10387

Closed

Conversation

lukashino
Copy link
Contributor

Redmine ticket:
https://redmine.openinfosecfoundation.org/issues/6739

Describe changes:

  • SCEnters added
  • refactor code to smaller functions
  • rewrite log message to be more consistent
  • add a user warning n the change of RX/TX descriptors - on changes caused by the NIC adjustment

@suricata-qa
Copy link

Information:

ERROR: QA failed on SURI_TLPW2_autofp_suri_time.

field baseline test %
SURI_TLPW2_autofp_stats_chk
.uptime 101 111 109.9%

Pipeline 18389

@@ -1550,7 +1578,7 @@ static void *ParseDpdkConfigAndConfigureDevice(const char *iface)
if (retval < 0) { // handles both configure attempts
iconf->DerefFunc(iconf);
if (rte_eal_cleanup() != 0)
FatalError("EAL cleanup failed: %s", strerror(-retval));
FatalError("EAL cleanup failed (err: %s)", strerror(-retval));
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see this as an improvement. The old scheme is as clear, while being less verbose. Would rather unify on that. This also matches use of strerror(errno) elsewhere in the code

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same for the rest of the PR

Copy link
Member

@victorjulien victorjulien left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not agreeing with the output changes

@lukashino
Copy link
Contributor Author

continues in #10449

@lukashino lukashino closed this Feb 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants