Skip to content

[Question] Get Routing Table support handling #170

Description

@faizana-nvidia

I'm opening a new thread for further discussions on support for GRTE command, this is in continuation with some of major points already discussed in #85 (comment) and #85 (comment)

Apart from complexity of involving GRTE support for Cascaded Bridge topology (which I think can be taken care in later stage), I'm curious on how are we planning to handle a case where a GRTE capable Bridge is not containing some of the endpoints entries from it's assigned pool space (for eg if something like HOST controlled GPUs are behind the bridge, in HOST off state GPUs are also in power off state thus bridge might not carry such endpoints entries in RT unless end device is visible to bridge).

As per our discussed logic, our approach for GRTE capable Bridges is to rely on RTE, which will be fetch during bridge's own discovery phase. Anything that becomes visible to Bridge in later point leading to update in its RTE list, how should this be communicated to BusOwner for new endpoint discovery?

One viable solution to this is to attempt a periodic GRTE, wanted to get your thoughts on this

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions