The Distributed Software Defined Network (dSDN) disclosed herein is an end-to-end architecture that enables secure and flexible programmability across a network with full lifecycle management of services and infrastructure applications (fxDeviceApp). The dSDN also harmonizes application deployment across the network independent of the hardware vendor. As a result, the dSDN simplifies the network deployment lifecycle from concept to design to implementation to decommissioning.

In one embodiment, a method for managing a smart network interface controller includes: sending a request for estimated resource requirements associated with the smart network interface controller to a baseboard management controller of the information handling system, the estimated resource requirements indicating estimated system resources likely to be required by emulated devices of the smart network interface controller; receiving the estimated resource requirements from the baseboard management controller; initializing the estimated system resources based on the estimated resource requirements; enumerating system resources for one or more additional devices of the information handling system; determining that the smart network interface controller is in a ready state; identifying actual resource requirements associated with the smart network interface controller indicating actual system resources required by the emulated devices of the smart network interface controller; and enumerating the actual system resources for the emulated devices of the smart network interface controller.

Technology is disclosed for establishing and administering multiple virtual machines, each with an audio, video and control (AVC) operating system (OS). The technology can also establish and administer cloud based AVC OSs. A server implementing this technology can perform real-time AVC processing, alongside soft and non-real-time processing and can host multiple, independent, virtual AVC OSs. Each AVC OS can perform the processing for an AVC setup. Each of the AVC OSs can be operated by a corresponding virtual machine controlled by a hypervisor running on the server. A cloud based AVC OS can perform processing for a corresponding remote AVC setup comprising multiple AVC devices. An AVC routing system can cause AVC signals from a particular AVC setup to reach a corresponding cloud AVC OS and conversely can cause signals from an AVC OS to reach the correct destination device.

Software configuration deployment techniques for disaggregated computing architectures, platforms, and systems are provided herein. In one example, a method includes presenting a user interface configured to receive instructions related to deployment of software to compute units, and receiving user selections of a software element for deployment to a compute unit comprising a processing element and a storage element. Responsive to the user selections, the method includes instructing a management processor of a communication fabric to deploy the software element for use by the compute unit by at least establishing a first partitioning in the communication fabric between the management processor and the storage element, deploying the software element to the storage element using the first partitioning, de-establishing the first partitioning, and establishing a second partitioning in the communication fabric between the processing element and the storage element comprising the software element, wherein the processing element operates using the software element.

A storage system includes a nonvolatile memory, a controller that controls writing and reading of data to and from the nonvolatile memory, a first interface, and a second interface, and is connected to a host device via the first interface and the second interface. While the host device is being started, a boot loader read from the nonvolatile memory is transferred to the host device via the second interface, and the first interface is initialized in parallel. After the host device is started, write data and read data to or from the nonvolatile memory via any one or both of the first interface and the second interface.

Examples implementations relate to configuration of computational drives. An example computational drive includes a housing to be inserted in a drive bay of a host device, and persistent storage. The computational drive may also include a processor to respond to an insertion of the housing into the drive bay of the host device by configuring the computational drive to operate as a new node of a distributed file system, and connecting the computational drive to the distributed file system as the new node.

An example computing device is provided. The computing device includes an interface to connect to a headphone and a processor communicatively coupled to the interface. The processor is to execute an application to hos an audio call, determine a headphone-only audio option is enabled for the application, detect that the headphone is connected to the interface, and allow a participant to join the audio call based on detection of the headphone connected to the interface.

Systems and methods are provided that may be implemented to provide a hardware-rooted, protected, and operating system (OS)-agnostic environment in which designated logic (e.g., one or more software and/or firmware tools such as an OS agent) may be run to verify the ownership and/or registration of a given information handling system before the OS is booted and running, and therefore before system data (e.g., user data) is exposed. In one exemplary embodiment, the designated logic may include a unified extensible firmware interface (UEFI) driver that is protected (e.g., signed), and that runs during the system boot sequence before the OS is booted. The disclosed systems and methods may be advantageously implemented in one embodiment to allow a system user who purchases and acquires a given information handling system from a source and/or channel other than the original system manufacturer to register and/or associate the given information handling system with their manufacturer-assigned user account.

A data processing system comprises a hybrid processor comprising a big TPU and a small TPU. At least one of the TPUs comprises an LP of a processing core that supports SMT. The hybrid processor further comprises hardware feedback circuitry. A machine-readable medium in the data processing system comprises instructions which, when executed, enable an OS in the data processing system to collect (a) processor topology data from the hybrid processor and (b) hardware feedback for at least one of the TPUs from the hardware feedback circuitry. The instructions also enable the OS to respond to a determination that a thread is ready to be scheduled by utilizing (a) an OP setting for the ready thread, (b) the processor topology data, and (c) the hardware feedback to make a scheduling determination for the ready thread. Other embodiments are described and claimed.

A computing device saves storage space by foregoing writing the payloads for batches of feature files to local storage and then automatically downloading payloads for individual batches of feature files as associated features are called upon. In various embodiments, an operating system (OS) that includes both frequently used and infrequently used features is executing on the computing device. Batches of feature files for the frequently used features of the OS may be hydrated on the computing device whereas batches of feature files for the infrequently used features of the OS may be left dehydrated on the computing device. When an infrequently used feature is requested, the computing device automatically downloads a corresponding batch of feature files. Then, the computing device may fulfill the request by implementing the infrequently used feature. Thus, predetermined batches of feature files remain immediately accessible at the computing device without consuming storage space unless called upon.