---
** [tickets:#1609] Introduce dedicated AIS handler threads**
**Status:** unassigned
**Milestone:** 5.0.FC
**Created:** Tue Nov 24, 2015 09:03 AM UTC by Anders Widell
**Last Updated:** Tue Nov 24, 2015 09:03 AM UTC
**Owner:** nobody
This is a generic cleanup ticket for introducing one or
I would like to propose the implementation to logsv.
The document and the prototype are attached.
Any comments are welcomed.
Attachments:
-
[1609_Proposal.txt](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/06f8bcbb/d902/attachment/1609_Proposal.txt)
(3.4 kB; text/plain)
-
[lgsv_
Missed lgs_imm.h in the patch. This file shows the protocol for inter-thread
communication.
Attachments:
-
[lgs_imm.h](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/06f8bcbb/6735/attachment/lgs_imm.h)
(2.7 kB; text/plain)
---
** [tickets:#1609] Introduce dedicated AIS handler t
There are 02 kind of events comming to this dedicated thead - mailbox and IMMA
events.
As there are important events in the mailbox, E_OI_INIT and E_OI_CLEAR, so,
this kind of event is prioritized to do first.
To avoid blocking the IMMA callback, the number of retries for doing
CREATE/MODIFY/DE
The prototype is put into 2 files for easy reading.
The condition variable is introduced to make sure the “OI CLEAR message” and
"OI INIT message" has been taken by the IMM OI thread before unblocking the
main thread. Max wait time is also provided.
Attachments:
-
[lgs_imm_oi.c](https://sour
Note: this ticket is on the global OpenSAF level. Changes specific to the LOG
service are covered by a separate ticket: [#1531]
---
** [tickets:#1609] Introduce dedicated AIS handler threads**
**Status:** unassigned
**Milestone:** 5.0.FC
**Created:** Tue Nov 24, 2015 09:03 AM UTC by Anders Wid
- **Milestone**: 5.0.FC --> future
---
** [tickets:#1609] Introduce dedicated AIS handler threads**
**Status:** unassigned
**Milestone:** future
**Created:** Tue Nov 24, 2015 09:03 AM UTC by Anders Widell
**Last Updated:** Mon Dec 07, 2015 12:41 PM UTC
**Owner:** nobody
This is a generic cle
Attach a very first draft, it only comes from the need of handling CLM API
error code in thread in AMFD, 2 patches:
- ais_executor.diff: abstract executor as a helper to run AIS api. First
attempt will run AIS call as in host thread. If this call is denied (due to
TRY_AGAIN/TIMEOUT), next retry
Hi Praveen
Looks OK - as an enhancement perhaps the OI handle could be created in the
thread itself to avoid passing the CB into the thread.
---
** [tickets:#1609] Introduce dedicated AIS handler threads**
**Status:** unassigned
**Milestone:** future
**Created:** Tue Nov 24, 2015 09:03 AM UTC
