Responding to dminer's comments on Target Discovery design, v 0.6: 3.3 In our discussions, only /var was named as a critical filesystem to check for, Updated document.
4.1.1. I have clarified the documentation to indicate that when you rediscover a particular type, that all cached information for that type will be discarded before the discovery is repeated. This was designed so that discover reports the latest information on currently available devices and status. td_discover_release() was designed as a simple means to restore all discovery resources after discovery completes. I do not anticipate a need to release only part of the resources. The sentence that comprises section 8 is supposed to indicate that caching is not intelligent and is completely manual and based on calls to td_discover()/td_discover_release(). Clarified this section. 4.1.2.1 Overloading errno values saves creating and using new definitions, but I see the potential for confusion and will supply subsystem-specific error codes. The enumeration call was kept separate from the attributes call in anticipation of other possible calls in future Caiman releases. The attributes call is the most expensive call, since it involves issuing ioctls that could hang on unresponsive devices and is done in a separate thread, so I didn't want this to be bound to the enumeration. td_get_slice_next() was defined here for future expansion, anticipating the need to get slices for a specific device or OS instance. 4.1.3 Corrected and moved TD interface table and deleted 4.1.3 4.1.6 (now 4.1.5) Updated documentation to clarify that an alternate thread will be spun to get device attributes, which issues an ioctl that can block indefinitely. This thread will be spun automatically. The thread can be stopped manually through td_discover_release(). The data structure used for synchronization and data sharing is now in this section. Re: desired discussion: I have almost completed coding this multi-threaded code and can post it to the wiki for closer review if you wish. 9 Updated documentation to indicate the consolidation private status and needs upgrading, the details of which are under review. The document will be updated when the upgrade needs are established. -- This message posted from opensolaris.org
