Skip to content

Conversation

@holke
Copy link
Collaborator

@holke holke commented Nov 26, 2025

Describe your changes here:

Related to #1985
The shared memory was often not initialized properly but we did not detect it.

I added an error code to t8_shmem_init following the convention of sc_shmem_init.
This actually caused many of our tests to fail giving more reason to this feature.
The errors are fixed with #1996 which should be merged first.

When the error code is met, we currently abort the program.

The reasoning is that shared memory should always be available to us, since it is part of MPI >=3.0

(This creates the new issue of requiring MPI 3.0 in our build system).

All these boxes must be checked by the AUTHOR before requesting review:

  • The PR is small enough to be reviewed easily. If not, consider splitting up the changes in multiple PRs.
  • The title starts with one of the following prefixes: Documentation:, Bugfix:, Feature:, Improvement: or Other:.
  • If the PR is related to an issue, make sure to link it.
  • The author made sure that, as a reviewer, he/she would check all boxes below.

All these boxes must be checked by the REVIEWERS before merging the pull request:

As a reviewer please read through all the code lines and make sure that the code is fully understood, bug free, well-documented and well-structured.

General

  • The reviewer executed the new code features at least once and checked the results manually.
  • The code follows the t8code coding guidelines.
  • New source/header files are properly added to the CMake files.
  • The code is well documented. In particular, all function declarations, structs/classes and their members have a proper doxygen documentation.
  • All new algorithms and data structures are sufficiently optimal in terms of memory and runtime (If this should be merged, but there is still potential for optimization, create a new issue).

Tests

  • The code is covered in an existing or new test case using Google Test.
  • The code coverage of the project (reported in the CI) should not decrease. If coverage is decreased, make sure that this is reasonable and acceptable.
  • Valgrind doesn't find any bugs in the new code. This script can be used to check for errors; see also this wiki article.

If the Pull request introduces code that is not covered by the github action (for example coupling with a new library):

  • Should this use case be added to the github action?
  • If not, does the specific use case compile and all tests pass (check manually).

Scripts and Wiki

  • If a new directory with source files is added, it must be covered by the script/find_all_source_files.scp to check the indentation of these files.
  • If this PR introduces a new feature, it must be covered in an example or tutorial and a Wiki article.

License

  • The author added a BSD statement to doc/ (or already has one).

@codecov
Copy link

codecov bot commented Nov 26, 2025

Codecov Report

❌ Patch coverage is 90.90909% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 77.05%. Comparing base (f74354f) to head (49e5eb7).
⚠️ Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
src/t8_cmesh/t8_cmesh_io/t8_cmesh_save.cxx 0.00% 1 Missing ⚠️
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1997   +/-   ##
=======================================
  Coverage   77.05%   77.05%           
=======================================
  Files         112      112           
  Lines       18959    18962    +3     
=======================================
+ Hits        14608    14611    +3     
  Misses       4351     4351           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Base automatically changed from feature-ignore_warnings_in_tests to main November 28, 2025 10:41
Comment on lines +66 to +74
#ifndef T8_ENABLE_MPI
// If we do not use MPI, there is nothing to do.
// We only have a single process.
return 1;
#endif
#ifndef SC_ENABLE_MPICOMMSHARED
SC_ABORT ("Trying to use shared memory but SC_ENABLE_MPICOMMSHARED is not set. This should not happen if you use MPI "
"v.3.0 or higher. Maybe related to https://github.com/DLR-AMR/t8code/pull/1996.");
#endif
Copy link
Member

Choose a reason for hiding this comment

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

Is this only the case when MPI is not linked or also when the number of ranks is 1?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

When the number of ranks is 1, but linked against MPI, it is save to use shared memory.
SC_ENABLE_MPICOMMSHARED will be defined and that case and this error will not occur.

* that concentrates all trees at one process. */
t8_shmem_init (sc_MPI_COMM_WORLD);
const int intranode_size = t8_shmem_init (sc_MPI_COMM_WORLD);
ASSERT_GT (intranode_size, 0) << "Could not initialize shared memory.";
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
ASSERT_GT (intranode_size, 0) << "Could not initialize shared memory.";
ASSERT_NE (intranode_size, 0) << "Could not initialize shared memory.";

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I feel more comfortable keeping GT, since >0 is a more restrictive condition then !=0.
If the intranode_size should be <0 then something went wrong and the memory was not initialized.

* that concentrates all trees at one process. */
t8_shmem_init (comm);
const int intranode_size = t8_shmem_init (comm);
ASSERT_GT (intranode_size, 0) << "Could not initialize shared memory.";
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
ASSERT_GT (intranode_size, 0) << "Could not initialize shared memory.";
ASSERT_NE (intranode_size, 0) << "Could not initialize shared memory.";

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

See comment above.

/* setup shared memory usage */
t8_shmem_init (comm);
const int intrasize_from_init = t8_shmem_init (comm);
ASSERT_GT (intrasize_from_init, 0) << "Error in t8_shmem_init. No intranode communicator set.";
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
ASSERT_GT (intrasize_from_init, 0) << "Error in t8_shmem_init. No intranode communicator set.";
ASSERT_NE (intrasize_from_init, 0) << "Error in t8_shmem_init. No intranode communicator set.";

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

See comment above.

/* setup shared memory usage */
t8_shmem_init (comm);
const int intranode_size = t8_shmem_init (comm);
ASSERT_GT (intranode_size, 0) << "Could not initialize shared memory.";
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
ASSERT_GT (intranode_size, 0) << "Could not initialize shared memory.";
ASSERT_NE (intranode_size, 0) << "Could not initialize shared memory.";

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

See comment above.

/* setup shared memory usage */
t8_shmem_init (comm);
const int intranode_size = t8_shmem_init (comm);
ASSERT_GT (intranode_size, 0) << "Could not initialize shared memory.";
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
ASSERT_GT (intranode_size, 0) << "Could not initialize shared memory.";
ASSERT_NE (intranode_size, 0) << "Could not initialize shared memory.";

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

See comment above.

if (forest->global_first_desc == NULL) {
/* Set the shmem array type of comm */
t8_shmem_init (comm);
SC_CHECK_ABORT (t8_shmem_init (comm) > 0, "Error in shared memory setup. Could not partition forest.");
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
SC_CHECK_ABORT (t8_shmem_init (comm) > 0, "Error in shared memory setup. Could not partition forest.");
SC_CHECK_ABORT (t8_shmem_init (comm) != 0, "Error in shared memory setup. Could not partition forest.");

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

See comment above

if (forest->tree_offsets == NULL) {
/* Set the shmem array type of comm */
t8_shmem_init (comm);
SC_CHECK_ABORT (t8_shmem_init (comm) > 0, "Error in shared memory setup. Could not partition forest.");
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
SC_CHECK_ABORT (t8_shmem_init (comm) > 0, "Error in shared memory setup. Could not partition forest.");
SC_CHECK_ABORT (t8_shmem_init (comm) != 0, "Error in shared memory setup. Could not partition forest.");

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

See comment above

T8_ASSERT (forest->element_offsets == NULL);
/* Set the shmem array type to comm */
t8_shmem_init (comm);
SC_CHECK_ABORT (t8_shmem_init (comm) > 0, "Error in shared memory setup. Could not partition forest.");
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
SC_CHECK_ABORT (t8_shmem_init (comm) > 0, "Error in shared memory setup. Could not partition forest.");
SC_CHECK_ABORT (t8_shmem_init (comm) != 0, "Error in shared memory setup. Could not partition forest.");

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

See comment above


/* Try to set the comm type */
t8_shmem_init (comm);
SC_CHECK_ABORT (t8_shmem_init (comm) > 0, "Error in shared memory setup. Could not load cmesh.");
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
SC_CHECK_ABORT (t8_shmem_init (comm) > 0, "Error in shared memory setup. Could not load cmesh.");
SC_CHECK_ABORT (t8_shmem_init (comm) != 0, "Error in shared memory setup. Could not load cmesh.");

tree_offset = cmesh->first_tree_shared ? -cmesh->first_tree - 1 : cmesh->first_tree;
if (cmesh->tree_offsets == NULL) {
t8_shmem_init (comm);
SC_CHECK_ABORT (t8_shmem_init (comm) > 0, "Error in shared memory setup.");
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
SC_CHECK_ABORT (t8_shmem_init (comm) > 0, "Error in shared memory setup.");
SC_CHECK_ABORT (t8_shmem_init (comm) != 0, "Error in shared memory setup.");

Copy link
Collaborator

Choose a reason for hiding this comment

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

I think that the != 0 fits better the true/false version of C, e.g. true being not zero.

@Davknapp Davknapp assigned Davknapp and holke and unassigned Davknapp Dec 4, 2025
@holke holke assigned Davknapp and unassigned holke Jan 14, 2026
@holke
Copy link
Collaborator Author

holke commented Jan 14, 2026

Thanks for the review.

I argue for keeping the >0 condition everywhere since it will catch more error cases.
Thus, there should be no need to change code from my side.

There was one comment by @sandro-elsweijer which i believe i have answered positively.
If you agree, you can merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants