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

Add pipe option to ignore MsgLim exceedance #2255

Open
skliper opened this issue Mar 10, 2023 · 1 comment
Open

Add pipe option to ignore MsgLim exceedance #2255

skliper opened this issue Mar 10, 2023 · 1 comment

Comments

@skliper
Copy link
Contributor

skliper commented Mar 10, 2023

Is your feature request related to a problem? Please describe.
Currently CFE_SB_MSGID_LIM_ERR_EID only reports the first 16 events on any pipe:

#define CFE_PLATFORM_SB_FILTERED_EVENT3 CFE_SB_MSGID_LIM_ERR_EID
#define CFE_PLATFORM_SB_FILTER_MASK3 CFE_EVS_FIRST_16_STOP

There's a use case where only the oldest or newest (see #541) message on the pipe should be kept, and the rest dropped. For example on a low rate link you may just want up to one message of each type, even though they may be getting produced at a higher rate (say if you want to slowly round-robin through HK msgs). This intentional dropping causes the error event and if/when it does get filtered since the event ID is shared with all the other pipes a legitimate issue (on a pipe where you don't want to exceed MsgLim) would be hidden.

Describe the solution you'd like
Add a pipe option to selectively ignore this error.

Describe alternatives you've considered
Could use QOS instead of pipe opts.

Additional context
Would be helpful to fix along with keeping newest msg:

Requester Info
Jacob Hageman - NASA/GSFC

@skliper
Copy link
Contributor Author

skliper commented Mar 10, 2023

Note the use case is actually that there's multiple links supporting different rates... so changing the production rate doesn't solve it. Desire is to get all the packets on the high rate link, and just one of each round-robin on the low rate.

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

No branches or pull requests

2 participants