Shell PCIe bridge and shared-link-interface services in a PCIe system

One or more computer-storage media having computer-executable instructions embodied thereon that, when executed by a computing system having a processor and memory, cause the processor to:

• access, at a Shell PCIe Bridge (SPB), an outbound transaction intended for a PCIe endpoint vendor IP or an inbound transaction intended for an SPB client, wherein the SPB supports a shared PCIe physical link based on a shared-link-interface comprising a vendor-agnostic downstream custom interface and a vendor-specific upstream PCIe endpoint interface;
• process the outbound transaction or the inbound transaction based on one or more shared-link-interface services, wherein processing transactions comprises executing shared-link-interface operations that provide protection enhancements associated with isolating the first SPB client from a second SPB client that shares a common pool available resource while sharing the shared PCIe physical link wherein isolating the first SPB client from the second SPB client prevents the first SPB client from interfering with transactions of the second SPB client associated with the shared PCIe physical link;
• and
• communicate the outbound transaction to the PCIe endpoint vendor IP or the inbound transaction to the SPB client.

A computer-implemented method, the method comprising:

• accessing, at a Shell PCIe Bridge (SPB), an outbound transaction intended for a PCIe endpoint vendor IP or an inbound transaction intended for an SPB client, wherein the SPB supports a shared PCIe physical link based on a shared-link-interface comprising a vendor-agnostic downstream custom interface and a vendor-specific upstream PCIe endpoint interface;
• processing the outbound transaction or the inbound transaction based on one or more shared-link-interface services, wherein processing transactions comprises executing shared-link-interface operations that provide protection enhancements associated with isolating the first SPB client from a second SPB client that shares a common pool available resource while sharing the shared PCIe physical link wherein isolating the first SPB client from the second SPB client prevents the first SPB client from interfering with transactions of the second SPB client associated with the shared PCIe physical link;
• and
• communicating the outbound transaction to the PCIe endpoint vendor IP or the inbound transaction to the SPB client.