NUMA allocation with NP02ReadoutApplication and fake readers#284
Open
NUMA allocation with NP02ReadoutApplication and fake readers#284
Conversation
…erModules are used.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
If full description and testing details are included on a parent issue, please link to that here.
See issue # for details
Otherwise, please include a summary of the change and which issue is fixed (if any).
Include relevant motivation and context, including a target environment and dunedaq version if known.
Also list any dependencies that are required for this change.
Allow using NUMA allocation through the dpdk receivers when FDFakeReaderModules are used. Without this, latency buffers are assigned numa 0 by default and cant be changed, so this limits the scope of using the NP02 readout application on servers where typically we need to assign the latency buffers to two NUMA regions.
Can be tested by running
and searching the output for the assigned NUMA node for the latency buffers in each daq application. it should be assigned to 2 and 3 when using the following ehn1-daqconfigs branch (parallel PR):
https://gitlab.cern.ch/dune-daq/online/ehn1-daqconfigs/-/merge_requests/274
Type of change
Testing checklist
dbt-build --unittest)pytest -s minimal_system_quick_test.py)dunedaq_integtest_bundle.sh)python -m pytest)pre-commit run --all-files)unit test and integration tests should pass.
Further checks
dbt-build --lint, and/or see https://dune-daq-sw.readthedocs.io/en/latest/packages/styleguide/)(Indicate issue here: # (issue))