[oh-tracker] [ openhpi-Bugs-1878026 ] Auto insert timeout and domain architecture

[SourceForge.net <no...@so...>]

Bugs item #1878026, was opened at 2008-01-23 05:27
Message generated for change (Settings changed) made by pdphan
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=532251&aid=1878026&group_id=71730

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: OpenHPI base library
>Group: Future
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Anton Pak (avpak)
Assigned to: peter dinh phan (pdphan)
Summary: Auto insert timeout and domain architecture

Initial Comment:
Now OpenHPI domain architecture is out of plug-ins code and implemented under plug-in.

So Auto-Insert timeout is domain property and should be
set/obtained/kept in domain framework and domain stanza in configuration file, not in handler stanza and plug-in code.

HPI spec also says:(B.02.01 subsection 7.9.10):
A resource may exist in multiple domains, which themselves may have different auto-insertion timeout values.
Upon insertion, the resource begins its auto-insertion policy based on the smallest auto-insertion timeout value.

So one need a function in HPI core library that returns smallest auto-insertion timeout for resource.

The patch is attached.
I've changed only ipmidirect plug-in to demonstrate how to use instroduces 'oh_get_hotswap_auto_insert_timeout' function.

----------------------------------------------------------------------

Comment By: Renier Morales (renierm)
Date: 2008-02-29 14:17

Message:
Logged In: YES 
user_id=660960
Originator: NO

Yes, that's the way it should be done with one exception. The smallest
auto insert timeout should be calculated on initialization and then be kept
track of as saHpiAutoInsertTimeoutSet() is called. The reason is locking to
iterate through all domains every time you need to know the timeout value
is too expensive.

I'll push this out for now as this problem will have to be solved a
completely different way once the client can connect to multiple daemons
(each daemon housing only one domain).

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=532251&aid=1878026&group_id=71730