Summary: msg: add support for critical capacity thresholds [#2625] Review request for Ticket(s): 2625 Peer Reviewer(s): Srinivas Pull request to: Affected branch(es): develop Development branch: ticket-2625 Base revision: 39ff6baecdda95d205d251c7fa33971dc22503c1 Personal repository: git://git.code.sf.net/u/trguitar/review
-------------------------------- Impacted area Impact y/n -------------------------------- Docs n Build system n RPM/packaging n Configuration files n Startup scripts n SAF services y OpenSAF services n Core libraries n Samples n Tests n Other n NOTE: Patch(es) contain lines longer than 80 characers Comments (indicate scope for each "y" above): --------------------------------------------- revision e65f8532d4cac97a996707cfd8f080d346aa0d94 Author: Alex Jones <[email protected]> Date: Tue, 7 Nov 2017 13:04:23 -0500 msg: add support for critical capacity thresholds [#2625] This commit implements Sections 3.4.12 and 6.2.2 of the B.03.01 MSG spec. Added Files: ------------ src/msg/apitest/test_CapacityThresholds.cc src/msg/msgd/mqd_ntf.cc src/msg/msgd/mqd_ntf.h Complete diffstat: ------------------ src/msg/Makefile.am | 8 +- src/msg/agent/mqa_api.c | 330 +++++++++ src/msg/apitest/test_CapacityThresholds.cc | 1049 ++++++++++++++++++++++++++++ src/msg/apitest/test_ErrUnavailable.cc | 110 ++- src/msg/common/mqsv_edu.c | 74 +- src/msg/common/mqsv_evt.h | 15 +- src/msg/msgd/mqd_api.c | 64 +- src/msg/msgd/mqd_db.h | 4 + src/msg/msgd/mqd_ntf.cc | 310 ++++++++ src/msg/msgd/mqd_ntf.h | 49 ++ src/msg/msgnd/mqnd_db.h | 6 + src/msg/msgnd/mqnd_evt.c | 359 +++++++++- src/msg/msgnd/mqnd_imm.c | 5 +- src/msg/msgnd/mqnd_util.c | 4 + 14 files changed, 2374 insertions(+), 13 deletions(-) Testing Commands: ----------------- run msgtest Testing, Expected Results: -------------------------- msgtest passes Conditions of Submission: ------------------------- Ack from developer or Nov 13, 2017 Arch Built Started Linux distro ------------------------------------------- mips n n mips64 n n x86 n n x86_64 y y powerpc n n powerpc64 n n Reviewer Checklist: ------------------- [Submitters: make sure that your review doesn't trigger any checkmarks!] Your checkin has not passed review because (see checked entries): ___ Your RR template is generally incomplete; it has too many blank entries that need proper data filled in. ___ You have failed to nominate the proper persons for review and push. ___ Your patches do not have proper short+long header ___ You have grammar/spelling in your header that is unacceptable. ___ You have exceeded a sensible line length in your headers/comments/text. ___ You have failed to put in a proper Trac Ticket # into your commits. ___ You have incorrectly put/left internal data in your comments/files (i.e. internal bug tracking tool IDs, product names etc) ___ You have not given any evidence of testing beyond basic build tests. Demonstrate some level of runtime or other sanity testing. ___ You have ^M present in some of your files. These have to be removed. ___ You have needlessly changed whitespace or added whitespace crimes like trailing spaces, or spaces before tabs. ___ You have mixed real technical changes with whitespace and other cosmetic code cleanup changes. These have to be separate commits. ___ You need to refactor your submission into logical chunks; there is too much content into a single commit. ___ You have extraneous garbage in your review (merge commits etc) ___ You have giant attachments which should never have been sent; Instead you should place your content in a public tree to be pulled. ___ You have too many commits attached to an e-mail; resend as threaded commits, or place in a public tree for a pull. ___ You have resent this content multiple times without a clear indication of what has changed between each re-send. ___ You have failed to adequately and individually address all of the comments and change requests that were proposed in the initial review. ___ You have a misconfigured ~/.gitconfig file (i.e. user.name, user.email etc) ___ Your computer have a badly configured date and time; confusing the the threaded patch review. ___ Your changes affect IPC mechanism, and you don't present any results for in-service upgradability test. ___ Your changes affect user manual and documentation, your patch series do not contain the patch that updates the Doxygen manual. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Opensaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-devel
