I'm sponsoring the following fast track for Harsha.
The timer is set to expire on 08/10/2010.
The supporting document is located in the case directory
under "materials/". Patch binding is requested.
- Govinda
Template Version: @(#)sac_nextcase 1.70 03/30/10 SMI
This information is Copyright (c) 2010, Oracle and/or its affiliates. All
rights reserved.
1. Introduction
1.1. Project/Component Working Name:
Extensions for LDC transport API
1.2. Name of Document Author/Supplier:
Author: Sriharsha Basavapatna
1.3 Date of This Document:
03 August, 2010
4. Technical Description
4.1 Project Summary
This case provides a new LDC transport API for LDC clients such as VIO
drivers, that need to know whether direct mapped shared memory can be used
for data buffers. The LDC transport API was approved under PSARC/2006/152.
This case provides an extension of the APIs defined in the original LDC
transport API specification.
4.2 Problem and Requirements
Currently, the LDC transport API does not provide an interface to obtain
the amount of available direct mapping space for the client. Also, there is
no restriction on the amount of direct mapping space per LDC. This poses
problems for clients that may need to know whether sufficient space is
available for direct mapping data buffers exported by a peer LDC end point.
For example, the vnet and the vswitch LDC clients need to determine this
information prior to negotiating their mode of data transfer. They need to
know whether sufficient space is available to direct map the data buffer
area and to operate in RxDringData mode (Reference [2]).
To achieve the above objectives, the following interface is required:
Given a LDC handle, provide the amount of direct mapping space available
to the client on that LDC.
4.3 Changes From the Previous Case
This project is an extension to the approved case, PSARC/2006/152 -
"Logical Domain Channels Transport API". The existing APIs are not changed.
But a new API is added, which extends the capabilities of the existing
interfaces.
The change includes:
- A new API function (ldc_info()) to return the amount of direct map
space available on a given LDC handle to the client.
4.4 Project Description
Please see the new section "Channel Information" on page 12, in the
documents provided in the case directory.
4.5 Interfaces
4.5.1 Exported Interfaces
Interface Name | Classification | Comment
----------------------|------------------------|----------------------
Data Types: | |
----------- | |
ldc_info_t | Consolidation Private | Channel Information
| |
Functions: | |
----------- | |
ldc_info | Consolidation Private | Get Channel Info
4.5.2 Imported Interfaces
None
5. References
[1] Logical Domain Channels Transport API - PSARC/2006/152
http://sac.sfbay.sun.com/Archives/CaseLog/arc/PSARC/2006/152/
[2] VIO vNet/vSwitch support for Rx Dring Data mode - FWARC/2010/054
http://sac.sfbay.sun.com/Archives/CaseLog/arc/FWARC/2010/054/
6. Resources and Schedule
6.4. Steering Committee requested information
6.4.1. Consolidation C-team Name:
ON
6.5. ARC review type: FastTrack
6.6. ARC Exposure: open
_______________________________________________
opensolaris-arc mailing list
opensolaris-arc@opensolaris.org
