Project

General

Profile

Feature #11030

Provide EventBuilder configuration parameter for number of MPI buffers per BoardReader

Added by Kurt Biery almost 4 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Additional Functionality
Target version:
Start date:
11/30/2015
Due date:
% Done:

0%

Estimated time:
Experiment:
-
Co-Assignees:
Duration:

Description

We recently saw problems in the DUNE 35-ton DAQ when we had the number of EventBuilder MPI buffers for receiving data from BoardReaders configured to be less than the total number of BoardReaders in use.

To help avoid this situation in the future, we would like the current EB receive buffer configuration parameter (mpi_buffer_count) to be gradually replaced by a new parameter that specifies the number of buffers per BoardReader (e.g. mpi_buffers_per_fragment, or mpi_buffers_per_data_source?). Typical values of this new parameter would be 1, 2, or 3, but this does not need to be strictly enforced in the code.

To support backward-compatibility, it would be great to support both the old- and new-style of specifying the number of MPI receive buffers in the EventBuilder configuration for some period of time. If both old- and new-style parameters are specified, the newer per-board-reader parameter should take precedence. It would be fine to print out a warning message if the older-style is being used to help remind users to upgrade their configuration files.

History

#1 Updated by Kurt Biery almost 4 years ago

  • Target version changed from v1_12_14 to artdaq Next Release

#2 Updated by Eric Flumerfelt almost 3 years ago

  • Category set to Additional Functionality
  • Status changed from New to Closed
  • Target version changed from artdaq Next Release to v2_00_00

This issue is obsolete as artdaq v2_00_00 lets each transfer link define the number of buffers. The default is 10 per link. There is no way anymore to specify the total number of buffers.



Also available in: Atom PDF