Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

Are locks redundant for mutually exclusive callback groups?

asked 2021-10-26 13:17:18 -0500

aposhian
1 ●1 ●2 ●2

I have two callbacks that access a shared resource, and use a mutex to manage access to it. If I set these callbacks to run in a mutually exclusive callback group (so the executor will not schedule them to run in different threads), then I don't need a mutex anymore, right?

edit retag flag offensive close merge delete

add a comment

1 Answer

Sort by » oldest newest most voted

answered 2021-11-01 09:01:17 -0500

osilva

1650 ●3 ●172 ●19 https://github.com/rob...

Hi @aposhian.

Users can use Mutually Exclusive Callback Groups in order to ensure
callbacks which operate on shared resources do not run at the same
time, without using locks.

Source

I believe you are right, Mutually Exclusive Group will do this for you.

edit flag offensive delete link

add a comment

Question Tools

3 followers

Stats

Asked: 2021-10-26 13:17:18 -0500

Seen: 244 times

Last updated: Nov 01 '21

Are locks redundant for mutually exclusive callback groups? edit

1 Answer

Question Tools

Stats

Related questions

Are locks redundant for mutually exclusive callback groups?