1. Introduction 1.1. Project/Component Working Name: LDOMs Domain Services API 1.2. Name of Document Author/Supplier: michael.christensen@sun.com narayan.venkat@sun.com 1.3. Date of This Document: 09/04/2008 1.4. Name of Major Document Customer(s)/Consumer(s): 1.4.1. The PAC or CPT you expect to review your project: Solaris PAC 1.4.2. The ARC(s) you expect to review your project: PSARC 1.4.3. The Director/VP who is "Sponsoring" this project: Jerri-Ann Meyer 1.4.4. The name of your business unit: Software 1.5. Email Aliases: 1.5.1. Responsible Manager: Jay.Jayachandra@Sun.com 1.5.2. Responsible Engineer: Michael.Christensen@Sun.com 1.5.3. Marketing Manager: Trefor.Jones@Sun.com 1.5.4. Interest List: ldoms-internal@sun.com, ldoms-io-fma@sun.com 2. Project Summary 2.1. Project Description: This case is a part of the sun4v umbrella case FWARC/2004/510, the Logical Domains umbrella case FWARC/2005/633, and the LDOMs Domain Services Specification FWARC/2006/055 The sun4v Domain Services framework provides a logical mechanism to allow domain to domain communication via registered service providers and service clients. This case outlines a set of APIs exported by the Solaris Domain Services module to user applications. 2.2. Risks and Assumptions: See FWARC/2004/510 3. Business Summary 3.1. Problem Area: See FWARC/2004/510 and FWARC/2005/633 3.2. Market/Requester: See FWARC/2004/510 and FWARC/2005/633 3.3. Business Justification: See FWARC/2004/510 and FWARC/2005/633 3.4. Competitive Analysis: See FWARC/2004/510 and FWARC/2005/633 3.5. Opportunity Window/Exposure: See FWARC/2004/510 and FWARC/2005/633 3.6. How will you know when you are done?: See FWARC/2004/510 and FWARC/2005/633 4. Technical Description: 4.1 Overview See FWARC/2004/510, FWARC/2005/633 and FWARC/2006/055 for overview. The LDOMs Domain Services framework (FWARC/2006/055) provides a logical mechanism for inter-domain communication based upon registered domain service providers and service clients. However, these may only be accessed via in-kernel modules. This case outlines the list of API's user programs may use to implement a domain service. 4.2. Bug/RFE Number(s): 6689118 LDoms Domain Services (DS) extensions for user program API 4.3. In Scope: This one-pager proposes new interfaces exported by a sun4v platform specific in-kernel module for use by user programs. 4.4. Out of Scope: N/A 4.5 Interfaces 4.5.1 Exported Interfaces Interface Name | Classification | Comment ----------------------|------------------------|---------------------- Data Types: | | ----------- | | ds_hdl_t | Consolidation Private | uint64_t service | | handle ds_domain_hdl_t | Consolidation Private | uint64_t domain handle ds_cb_arg_t | Consolidation Private | Callback argument ds_ver_t | Consolidation Private | Version structure ds_capability_t | Consolidation Private | Capability structure ds_ops_t | Consolidation Private | Operators structure | | Functions: | | ----------- | | ds_init | Consolidation Private | Initialize services ds_fini | Consolidation Private | Finalize services ds_svc_reg | Consolidation Private | Register Service | | Provider ds_clnt_reg | Consolidation Private | Register Service | | Client ds_hdl_lookup | Consolidation Private | Lookup Service | | Handles ds_domain_lookup | Consolidation Private | Lookup Domain | | Handle ds_unreg_hdl | Consolidation Private | Unregister Service | | Handle ds_unreg_svc | Consolidation Private | Unregister Service ds_send_msg | Consolidation Private | Send Service Message ds_recv_msg | Consolidation Private | Receive Service Message ds_isready | Consolidation Private | Query if Handle is | | Ready ds_dom_hdl_to_name | Consolidation Private | Get Domain Name of | | Domain Handle ds_dom_name_to_hdl | Consolidation Private | Get Domain Handle of | | Domain Name 4.5.2 Imported Interfaces None 4.6. Doc Impact: None 4.7. Admin/Config Impact: N/A 4.8. HA Impact: None 4.9. I18N/L10N Impact: No 4.10. Packaging & Delivery: This projects currently will be delivered as part of new LDoms specific package along with its client drivers. This support will be integrated in S10 update 7 release. 4.11. Security Impact: N/A 4.12. Dependencies: This project depends upon FWARC/2008/563 "Virtual Domain Service MD nodes and misc. properties". 5. Reference Documents: - LDOMs Domain Services API (attached) - Project and Architecture docs are available at: http://cpubringup.sfbay.sun.com/twiki/bin/view/LDoms/WebHome - FWARC/2004/510 - Project Q Umbrella - FWARC/2005/633 - LDoms: Project Q Logial Domaining Umbrella - FWARC/2006/055 - Domain Services - FWARC/2008/563 - Virtual Domain Service MD nodes and misc. properties 6. Resources and Schedule: 6.1. Projected Availability: S10U7 6.2. Cost of Effort: See FWARC/2005/633 6.3. Cost of Capital Resources: Capital resources are subsumed as part of overall product development. 6.4. Product Approval Committee requested information: 6.4.1. Consolidation Name: ON 6.4.2. Contributing OpCo/BU/Division Name: Software 6.4.3. Type of PAC Review and Approval expected: Fast Track 6.4.4. Project Boundary Conditions: N/A 6.4.5. Is this a necessary project for OEM agreements: No. 6.4.6. Notes/Dependencies: N/A 6.4.7. Target RTI Date/Release: N/A - Not a separate deliverable. 6.4.8. Target Code Design Review Date: Q3CY08 6.4.9. Update approval addition: N/A 6.5. ARC review type: Fast Track 7. Prototype Availability: 7.1. Prototype Availability: Q3CY08 7.2. Prototype Cost: Done using existing resources.