Hi Dat,
Ack from me.
Best Regards,
Thien
________________________________
From: Dat Tran Quoc Phan <dat.tq.p...@dektech.com.au>
Sent: Tuesday, April 2, 2024 8:47 AM
To: Thang Duc Nguyen <thang.d.ngu...@dektech.com.au>; Thien Minh Huynh
<thien.m.hu...@dektech.com.au>; Tai Huynh Nguyen <tai.h.ngu...@dektech.com.au>
Cc: opensaf-devel@lists.sourceforge.net <opensaf-devel@lists.sourceforge.net>;
Dat Tran Quoc Phan <dat.tq.p...@dektech.com.au>
Subject: [PATCH 0/2] Review Request for ticket 3349 V3
Summary: ntf: remove overdue notification from logger buffer [#3349]
Review request for Ticket(s): 3349
Peer Reviewer(s): Thang, Thien, Tai
Pull request to: *** LIST THE PERSON WITH PUSH ACCESS HERE ***
Affected branch(es): develop
Development branch: ticket-3349
Base revision: fcb47390bf79f1b5026093c2b5456cc1d48ecb79
Personal repository: git://git.code.sf.net/u/dattqphan/review
--------------------------------
Impacted area Impact y/n
--------------------------------
Docs n
Build system n
RPM/packaging n
Configuration files n
Startup scripts n
SAF services n
OpenSAF services y
Core libraries n
Samples n
Tests n
Other n
Comments (indicate scope for each "y" above):
---------------------------------------------
*** EXPLAIN/COMMENT THE PATCH SERIES HERE ***
revision ad744c90e242272fe78ba09694e41de5eb164455
Author: dat.tq.phan <dat.tq.p...@dektech.com.au>
Date: Tue, 2 Apr 2024 07:50:57 +0700
amf: move ntf job to the end of queue [#3349]
When AMF sends job to NTF but NTF is busy with full buffer,
AMF will be stuck and unable to process other jobs.
Solution is to move the front NTF job to the end of queue
when NTF is busy and continue to process other jobs.
revision e58044b667bcc6c8b776d30fa04dbbbfdb49ebde
Author: dat.tq.phan <dat.tq.p...@dektech.com.au>
Date: Mon, 1 Apr 2024 18:14:56 +0700
ntf: remove overdue notification from logger buffer [#3349]
When logger buffer on NTF is full, it cannot receive requests.
Sometimes, notifications stay in logger buffer for too long make
NTF always busy.
Solution is to remove overdue notification out of logger buffer
so NTF can continue receive requests.
Complete diffstat:
------------------
src/amf/amfd/ntf.cc | 7 +++++++
src/ntf/ntfd/NtfLogger.cc | 18 ++++++++++++++++++
src/ntf/ntfd/NtfLogger.h | 1 +
src/ntf/ntfd/NtfNotification.cc | 9 +++++++++
src/ntf/ntfd/NtfNotification.h | 3 +++
src/ntf/ntfd/ntfs.h | 2 ++
6 files changed, 40 insertions(+)
Testing Commands:
-----------------
*** LIST THE COMMAND LINE TOOLS/STEPS TO TEST YOUR CHANGES ***
Testing, Expected Results:
--------------------------
*** PASTE COMMAND OUTPUTS / TEST RESULTS ***
Conditions of Submission:
-------------------------
*** HOW MANY DAYS BEFORE PUSHING, CONSENSUS ETC ***
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.
_______________________________________________
Opensaf-devel mailing list
Opensaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-devel
