Fortinet, Inc.

Qualcomm Incorporated

Girish Bhat

Rajesh I Balay

Gregory Lockwood

Rama Krishnam Nagarajan

Rama Krishnan Nagarajan

George Patsilaras

Subbarao Palacharla

Vipul Gandhi

Alain Artieri

Simon Peter William Booth

Steven Halter

Samar Asbe

Jeffrey Shabel

Kedar Bhole

Mahadevamurty Nemani

Subodh Singh

Isaac Berk

Victor Wong

Ram Nagarajan

Younghoon Kim

Hiral Nandu

Sparsh Singhai

Kapil Bansal

Miguel Ballesteros

Pradeep Atur

Yen-Kuan Wu

Various embodiments include methods and devices for implementing a criterion aware cache replacement policy by a computing device. Embodiments may include updating a staling counter, writing a value of a local counter to a system cache in association with a location in the system cache for with data, in which the value of the local counter includes a value of the staling counter when (i.e., at the time) the associated data is written to the system cache, and using the value of the local counter of the associated data to determine whether the associated data is stale.

Multimedia compressed frame aware cache replacement policy

Integrated circuits (ICs) employ subsystem shared cache memory for facilitating extension of low-power island (LPI) memory. An LPI subsystem and primary subsystems access a memory subsystem on a first access interface in a first power mode and the LPI subsystem accesses the memory subsystem by a second access interface in the low power mode. In the first power mode, the primary subsystems and the LPI subsystem may send a subsystem memory access request including a virtual memory address to a subsystem memory interface of the memory subsystem to access either data stored in an external memory or a version of the data stored in a shared memory circuit. In the low-power mode, the LPI subsystem sends an LPI memory access request including a direct memory address to an LPI memory interface of the memory subsystem to access the shared memory circuit to extend the LPI memory.

Integrated circuits (IC) employing subsystem shared cache memory for facilitating extension of low-power island (LPI) memory and related methods

Resource access control in a system-on-chip ('SoC') may employ an agent executing on a processor of the SoC and a trust management engine of the SoC. The agent, such as, for example, a high-level operating system or a hypervisor, may be configured to allocate a resource comprising a memory region to an access domain and to load a software image associated with the access domain into the memory region. The trust management engine may be configured to lock the resource against access by any entity other than the access domain, to authenticate the software image associated with the access domain, and to initiate booting of the access domain in response to a successful authentication of the software image associated with the access domain.

Access control system and method for isolating mutually distrusting security domains

Methods, apparatus and data structures are provided for managing multicast IP flows. According to one embodiment, a router identifies active multicast IP sessions. A data structure is maintained by the router that contains information regarding the active multicast IP sessions and includes multiple pairs of a source field and a group field ({S, G} pairs), a first pointer associated with each of the {S,G} pairs and a set of slots. Each of the {S, G} pairs defines an active multicast IP session. The source field defines a source of a multicast transmission of the multicast IP session and the group field defines a group corresponding to the multicast IP session. The first pointer points to a dynamically allocated set of outbound interface (OIF) blocks. Each slot has stored therein a second pointer to a transmit control block (TCB) data structure that services users participating in the multicast IP session.

Scalable IP-services enabled multicast forwarding with efficient resource utilization

One or more triggers may be coupled to sources on a system on a chip of a portable computing device. The sources monitor the system for status conditions. The one or more triggers are coupled to a trigger bus. A sequencer engine is coupled to the trigger bus and a communication bus. The sequencer engine receives one or more instructions from the communication bus for determining how the sequencer engine should monitor the one or more triggers via the trigger bus and preserve data received from the one or more triggers before a system reset. The sequencer engine then receives data from the one or more triggers and stores the data in local memory storage. The sequencer engine, if programmed, may generate at least one of a trace packet, an interrupt signal, and a general purpose input/output signal in response to receiving data from one or more triggers.

System and method for preserving critical debug data in a portable computing device

Methods, apparatus and data structures are provided for managing multicast IP flows. According to one embodiment, a network switch module includes a memory and multiple processors partitioned among multiple virtual routers (VRs). Each VR maintains a data structure containing therein information regarding the multicast sessions, including a first value for each of the multicast sessions, at least one chain of one or more blocks of second values and one or more transmit control blocks (TCBs). Each first value is indicative of a chain of one or more blocks of second values. Each second value corresponds to an outbound interface (OIF) participating in the multicast session and identifies a number of times packets associated with the multicast session are to be replicated. The TCBs have stored therein control information to process or route packets. Each second value is indicative of a TCB that identifies an OIF of the network device through which packets are to be transmitted.

Methods, apparatus and data structures are provided for managing multicast IP flows. According to one embodiment, active multicast IP sessions are identified by a network device. A data structure is maintained by the network device and contains therein information regarding the multicast sessions, including a first value for each of the multicast sessions, at least one chain of one or more blocks of second values and one or more transmit control blocks (TCBs). Each first value is indicative of a chain of one or more blocks of second values. Each second value corresponds to an outbound interface (OIF) participating in the multicast session and identifies a number of times packets associated with the multicast session are to be replicated. The TCBs have stored therein control information to process or route packets. Each second value is indicative of a TCB that identifies an OIF of the network device through which packets are to be transmitted.

Methods, apparatus and data structures are provided for managing multicast IP flows. According to one embodiment, active multicast IP sessions are identified by a router. A data structure is maintained by the router and contains therein information regarding the multicast sessions, including a first pointer for each of the multicast sessions, at least one chain of one or more blocks of second pointers and one or more transmit control blocks (TCBs). Each first pointer points to a chain of one or more blocks of second pointers. Each second pointer corresponds to an outbound interface (OIF) participating in the multicast session and identifies a number of times packets associated with the multicast session are to be replicated. The TCBs have stored therein control information to process or route packets. Each second pointer points to a TCB that identifies an OIF of the router through which packets are to be transmitted.

Methods, apparatus and data structures are provided for managing multicast IP flows. According to one embodiment, a network switch module includes a memory and multiple processors partitioned among multiple virtual routers (VRs). Each VR maintains a data structure including information relating to multicast sessions handled by the VR and including a first pointer for each multicast session, a chain of blocks of second pointers and one or more TCBs. Each first pointer points to a chain of blocks of second pointers. Each second pointer corresponds to an OIF of the VR participating in the multicast session defined by the first pointer and defines how many times to replicate packets associated with the multicast session. The TCBs store control information relevant to processing or routing packets. Each second pointer points to a TCB, which identifies the OIF out which packets of the multicast session are transmitted from the VR.

Methods and apparatus are provided for managing multicast Internet Protocol (IP) flows. According to one embodiment, a multicast IP flow is identified at an interface of a network device using information from a packet header. For any newly identified multicast IP flow, if flow-specific services are required, a new first transmit control block (TCB), which includes one or more attributes relating to flow-specific services required by the newly identified multicast IP flow, is created for the newly identified multicast IP flow. Otherwise, if flow-specific services are not required by the newly identified multicast IP flow, a default second TCB, which excludes any attributes relating to flow-specific services and which includes one or more attributes related to a virtual interface (VI) serving as an outbound interface (OIF) for the newly identified multicast IP flow, is used.

Methods, apparatus and data structures are provided for managing multicast IP flows. According to one embodiment, a memory of a router has stored therein a data structure, which includes information relating to multicast sessions being handled by the router and including a first pointer for each multicast session, at least one chain of blocks of second pointers and one or more TCBs. Each first pointer points to a chain of blocks of second pointers. Each second pointer corresponds to an OIF of the router participating in the multicast session defined by the first pointer and defines how many times packets associated with the multicast session are to be replicated. The TCBs are configured to store control information relevant to processing or routing packets. Each second pointer points to a TCB and each TCB identifies the OIF out which packets of the multicast session are transmitted from the router.

This document describes, among other things, a router providing service-enabled multicast forwarding for a flow-based architecture. Services are enabled using inbound/outbound policies from Access Control Lists (ACLs). In a first mode, per-flow services are not enabled, and flows are aggregated for efficiency. In a second mode, per-flow services are enabled, and control information for an outbound interface (OIF) is shared across all multicast flows that do not have per-flow service enabled. A flow management scheme for these modes allows dynamic multicast membership updates while reducing disruption of active flows. This supports a large multicast OIF list and a high rate of multicast 'Joins' and 'Leaves'. This provides scalability and performance, such as desired for deploying multicast for broadband subscriber applications.

Growing community of inventors

San Diego, CA, United States of America

Girish Bhat