- **summary**: imm: Don't check for pending fevs when updating pure runtime
attributes --> imm: Don't check for pending fevs when only updating pure
runtime attributes
- **Comment**:
The optimization is only for the pure and local case.
This should typically be the case for a pure RTA update, which should only be
the result
of a read request from some client.
However, the saImmOiRtObjectUpdate API actually leaves it open to the OI to
allow
it to update both pure RTAs and cached RTAs in the same call.
Probably no one has tested that mixed variant since it has no clear use-case.
---
** [tickets:#1445] imm: Don't check for pending fevs when only updating pure
runtime attributes**
**Status:** review
**Milestone:** 4.7-Tentative
**Created:** Thu Aug 13, 2015 09:48 AM UTC by Hung Nguyen
**Last Updated:** Fri Aug 14, 2015 06:21 AM UTC
**Owner:** Neelakanta Reddy
When invoking saImmOiRtObjectUpdate(), number of pending fevs messages is
always checked on server side and TRY_AGAIN is returned when it reaches
IMMSV_DEFAULT_FEVS_MAX_PENDING.
If the attributes to be updated are pure runtime attributes, number of pending
fevs messages should not be checked because the IMMD_EVT_ND2D_OI_OBJ_MODIFY
message wouldn't be sent out to broadcast to other IMMNDs.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
