Browse Prior Art Database

Service Function Planes to extend the capabilities of the service co-processor architecture

IP.com Disclosure Number: IPCOM000223119D
Publication Date: 2012-Nov-05
Document File: 1 page(s) / 30K

Publishing Venue

The IP.com Prior Art Database

Abstract

Service Function Planes to extend the capabilities of the service co-processor architecture

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 71% of the total text.

Page 01 of 1

Service Function Planes to extend the capabilities of the service co-processor architecture

The power of the service co-processor architecture is restricted by the existence of a single Service Address Space SAS. This restriction imposes several limitations on the potential of the service co-processor architecture . Two examples of these limitations are the inability to take and manipulate copies of the SAS in core storage, and the inability to mark particular storage locations within the address space for special functionality. The SAS could potentially be copied out to DASD storage, but any subsequent manipulation of the copied storage would be relatively slow compared to operations on core storage. Storage locations which are the target of special functionality could be marked in the SAS directly but this would corrupt the contents of the SAS. The ability to take and manipulate copies of the SAS, and a mechanism for marking storage locations for special processing (without corrupting

the SAS) are required to facilitate powerful new tooling based on the service co-processor architecture.

    Service function planes can map over the SAS such that for each byte of storage in the SAS there is a matching byte of storage in the service function plane. The service function planes are retained in core storage. The contents of the SAS can thus be copied to, retained in, and manipulated from a service function plane. A particular byte of storage in the SAS can be flagged a...