Apple Inc.

Eric Tsz Leung Cheng

Cahya Adiansyah Masputra

Sandeep Nair

Wei Shen

Francesco R Dimambro

Vidhi Goel

Methods and apparatus for split memory allocations in non-kernel space. Many modern networking technologies use asymmetric transmit and/or receive resource. Various aspects described herein split memory resources for transmit and receive, configuring each for their respective hardware optimizations. For example, a receive data paths that support batch processing and packet aggregation may be allocated large memory objects (32 KB) that can route data packets on a per-flow basis. In contrast, transmit data paths that support multiple concurrent network connections may be allocated small memory objects (2 KB) that can route data packets one at a time.

Methods and apparatus for thread-level execution in non-kernel space

Methods and apparatuses for cross-layer processing. In some embodiments, kernel processes are executed at a higher privilege and priority than user space processes, thus cross-layer communication that spans both kernel and user space may introduce system vulnerabilities and/or consume limited resources in an undesirable manner. Unlike kernel space networking architectures that have to accommodate generic use cases, user space networking architectures are application specific, run in their own memory allocations, and can be terminated without affecting other user space applicationsand/or kernel space operation. Various aspects described herein provide application specific, non-generic functionality without kernel assistance. Exemplary embodiments for buffer cloning, packet aggregation and 'just in time' transformations, are illustrative of the broader concepts enabled by the present disclosure.

Methods and apparatuses for cross-layer processing

Techniques are provided for managing a user space protocol stack are disclosed herein. A nexus in a kernel space can receive a packet from a packet pool, and extract information from the packet to generate a flow key indicating a particular flow for the packet. The nexus can further look up the flow key in a flow table to determine whether there is an existing flow key stored in the flow table matching the flow key of the packet, and store the packet into a batch of packets of the existing flow when the existing flow key matches the flow key of the packet. When a release condition being met, the nexus can release the batch of packets of the existing flow to a user space protocol stack within a user space application through a channel communicatively coupled to the nexus and the user space protocol stack.

Methods and apparatus for flow-based batching and processing

Methods and apparatus for emerging use case support in user space networking architectures. In one embodiment, an apparatus configured to segregate packet data based on a packet type is disclosed. The exemplary embodiment provides a custom data type registry that enables the definition, addition, removal, modification, and/or prioritization of custom packet processing rules. Variants of the registry may support custom ethertype packets, network packets, and/or transport packets. In another embodiment, mechanisms for enabling an intermediary packet processing stage are described. Intermediary packet processing may enable user space system extensions that support e.g., packet filtering, packet modification, and/or other forms of packet processing.

Methods and apparatus for emerging use case support in user space networking

Methods and apparatus for low latency operation in user space networking architectures. In one embodiment, an apparatus configured to enable low latency data transfer is disclosed. The exemplary embodiment provides a multiplexer that allocates a fixed portion of network bandwidth for low latency traffic. Low latency traffic is routed without the benefit of general-purpose packet processing. In one embodiment, network extensions for low latency operations are described. Specifically, an agent is described that enables low latency applications to negotiate for low latency access. In one embodiment, mechanisms for providing channel event notifications are described. Channel event notifications enable corrective action/packet processing by the low latency application. In one embodiment, mechanisms for providing interface advisory information are described. Interface advisory information may be provided asynchronously to assist in low latency operation.

Growing community of inventors

Cupertino, CA, United States of America

Eric Tsz Leung Cheng