Asynchronous object manager in a network routing environment

Patent metadata

Field	Value
Publication number	US-12308997-B2
Application number	US-202318516173-A
Country	US
Kind code	B2
Filing date	Nov 21, 2023
Priority date	Aug 23, 2018
Publication date	May 20, 2025
Grant date	May 20, 2025

Abstract

Systems, methods, and devices for offloading network data to a datastore. A system includes routing chip hardware and an asynchronous object manager in communication with the routing chip hardware. The asynchronous object manager is configurable to execute instructions stored in non-transitory computer readable storage media. The instructions include asynchronously receiving a plurality of objects from one or more producers. The instructions include identifying one or more dependencies between two or more of the plurality of objects. The instructions include reordering the plurality of objects according to the one or more dependencies. The instructions include determining whether the one or more dependencies is resolve. The instructions include, in response to determining the one or more dependencies is resolved, calling back an application and providing one or more of the plurality of objects to the application.

First claim

What is claimed is:

1. A method comprising:
identifying a dependency between two or more objects of a plurality of objects, wherein the dependency identifies a parent object and a dependent object;
determining whether the dependency is resolved; and
in response to determining the dependency is not resolved, postponing one or more of:
an update on the dependent object until creation of the parent object; or
deletion of the parent object until deletion of the dependent object.

2. The method of claim 1 , wherein identifying the dependency comprises identifying a unique key associated with the parent object that is adopted by the dependent object.

3. The method of claim 1 , further comprising reordering at least a portion of the plurality of objects based on the unique key such that the dependent object depends upon the parent object.

4. The method of claim 1 , further comprising asynchronously receiving the plurality of objects by way of an application program interface (API) integrated with an asynchronous object manager;
wherein the asynchronous object manager is a layer of a software stack configured to manage operations of a networking device comprising a switch or a router.

5. The method of claim 4 , wherein the asynchronous object manager is a state machine.

6. The method of claim 4 , wherein the asynchronous object manager provides a means for a first producer to provide a message to the asynchronous object manager in lieu of providing a message directly to a second producer of a next hop.

7. The method of claim 4 , wherein the networking device further comprises a routing information base, wherein the routing information base is a data table stored on the networking device that comprises a listing of routes to networking destinations.

8. The method of claim 4 , wherein the asynchronous object manager comprises a multiple threaded architecture.

9. The method of claim 8 , wherein the asynchronous object manager manages work distribution by causing each thread within the multiple threaded architecture to manage care of data plane programming for one or more data plane services.

10. The method of claim 8 , wherein each thread within the multiple threaded architecture comprises an instance of the asynchronous object manager to store information from producers and to program assigned devices.

11. The method of claim 4 , wherein the networking device comprises:
hardware;
the asynchronous object manager installed as a bottom-most layer of the software stack for managing the hardware;
a data plan adaptation layer (DPAL);
a forwarding information base;
a routing information base; and
a configuration agent.

12. The method of claim 4 , wherein the networking device further comprises a forwarding information base configured to identify proper output network interface to which an input interface should forward an object, and wherein the forwarding information base is a dynamic table that maps media access control addresses to ports.

13. The method of claim 4 , wherein identifying the dependency comprises identifying a unique key associated with the parent object that is adopted by the dependent object;
wherein the unique key is associated with a next hop object; and
wherein a router object added to the asynchronous object manager.

14. The method of claim 1 , further comprising, in response to determining the dependency is resolved, calling back an application and providing the two or more of the plurality of objects to the application.

15. The method of claim 1 , further comprising receiving the plurality of objects from one or more producers, and wherein the one or more produces comprises one or more of an application, a process, a thread, or a function.

16. The method of claim 1 , further comprising, in response to determining the dependency is resolved, providing the two or more of the plurality of objects to a data plane adaptation layer (DPAL) of a networking device, wherein the networking device is a switch or a router.

17. The method of claim 16 , further comprising providing the DPAL a route for transferring messages from a first location to a final destination.

18. The method of claim 16 , further comprising receiving a query from the DPAL, wherein the query requests a route for transmitting a message from a first location to a final destination.

19. The method of claim 18 , further comprising:
calculating the route requested by the DPAL;
recording the route; and
providing the route to the DPAL;
wherein providing the route comprises providing only in response to determining the dependency is resolved.

20. The method of claim 1 , further comprising:
receiving a deletion sequence for the plurality of objects from one or more producers; and
reordering the deletion sequence based on the dependency.

Assignees

• Arrcus Inc

Inventors

• Pai Nalinaksh
• Rajaraman Kalyani
• Ragukumar Vikram

Classifications

• G06F2009/45595

  Network integration; Enabling network access in virtual machine instances · CPC title

• H04L67/1097

  for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS] · CPC title

• G06F9/4881

  Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues · CPC title

• G06F9/542

  Event management; Broadcasting; Multicasting; Notifications · CPC title

• G06F16/278

  Data partitioning, e.g. horizontal or vertical partitioning · CPC title