qp.backline.Transport

class Transport(name)[source]

Bases: object

A named data transport.

A Backline uses a transport to select how messages move between the Controller and its coprocessors, and exposes it as transport. The compiler combines the transport with each node’s hardware to select a concrete runtime backend.

The built-in transports are:

  • "rdma": messages travel over RDMA, so every coprocessor needs an Endpoint.

  • "memcpy": messages are copied in memory, with no network endpoint.

  • "none": no messages move. The placement is a Controller alone, and passing any coprocessor raises an error.

Any other transport a backend in Catalyst’s transport backend registry implements is accepted as well, so a backend package adds a transport without a PennyLane change.

Warning

Backline is experimental and only usable through the Catalyst compiler.

Parameters:

name (str) – The registry name of the transport, e.g. "rdma".

Example

Transports are normally selected by name, and Backline resolves the string:

>>> dev = qp.Backline(controller=qp.Controller(), transport="rdma")
>>> dev.transport
Transport(name='rdma')

Passing a Transport instance directly is equivalent.

name

The registry name of the transport, e.g. "rdma".

name = <dataclasses._MISSING_TYPE object>

The registry name of the transport, e.g. "rdma".