Summary: amfd : terminate SUs in reverse order [#81]
Review request for Trac Ticket(s):AMF #81
Peer Reviewer(s):hans F., Nagendra
Pull request to: Nagendra
Affected branch(es):Default
Development branch: <<IF ANY GIVE THE REPO URL>>
--------------------------------
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
Comments (indicate scope for each "y" above):
---------------------------------------------
Please see the commit log below and ticket.
changeset a75866fa7d81f9c4256fe0031118be8b70106e3c
Author: praveen.malv...@oracle.com
Date: Thu, 07 Nov 2013 13:57:45 +0530
amfd : terminate SUs in reverse order [#81] This patch ensures that
TERMINATION of SUs in the context of LOCK_IN operation on SG should be
performed in reverse order of saAmfSuRank. As of now patch does not
ensure,
like the case of instantiation, that SUs of any given rank will be
terminated only after the SUs of lower ranks have moved to TERMINATED
state.
AMFD will request AMFNDs to perform the termination of SUs by sending
termination request in reverse order.
Complete diffstat:
------------------
osaf/services/saf/amf/amfd/sg.cc | 43
++++++++++++++++++++++++++-----------------
1 files changed, 26 insertions(+), 17 deletions(-)
Testing Commands:
-----------------
Tested by issuing LOCK_IN operation on SG by hosting all the SUs on same node.
Testing, Expected Results:
--------------------------
SUs termination started in reverse order.
Conditions of Submission:
-------------------------
Ack from Hans or Nagendra.
Arch Built Started Linux distro
-------------------------------------------
mips n n
mips64 n n
x86 y y
x86_64 n n
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 ~/.hgrc file (i.e. username, 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.
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-devel mailing list
Opensaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-devel
