Abstract: Data analytics systems are described herein which may provide requests for file tiering to one or more file servers. The data analytics systems may receive metadata and/or event data from one or more file servers and may utilize the metadata and/or event data to select files for tiering. In some examples, files may be selected using a sliding window methodology. In some examples, files may be selected in part based on user behavior with the files in the file system. In some examples, file analytics systems may send requests to retry tiering operations which failed. The retry requests may be sent in a manner that is based on the error which caused the failure.

Abstract: An access point includes a WiFi chipset, a first radio that is coupled to the WiFi chipset and that is selectively coupled to a first radiating element through one of a first filter or a second filter, and a second radio that is coupled between the WiFi chipset and a second radiating element.

Abstract: Examples of file analytics systems are described that may obtain metadata data and events data from a virtualized file server. The metadata may be obtained by scanning one or more snapshots of the virtualized file server. The metadata and event data may be used to report various metrics relating to the virtualized file server.

Abstract: Examples of a virtualized file server that persistently stores file system event data records are described. The virtualized file server may include an audit framework with a connector publisher that is configured to publish the event data records and other information for consumption by other services using a message system. The event data records may include data related to various operations on the file system executed by the VFS. The VFS may persistently store event data records according to a data retention policy and/or until an event data record is consumed by one or more particular services.

Abstract: An example system includes a plurality of FSVMs executing at two or more computing nodes configured to cooperatively manage a distributed VFS and a system manager configured to provide a tag based on a pattern and an action associated with the tag to the plurality of FSVMs. The plurality of FSVMs are further configured to scan files of the VFS to tag files including the pattern and tag and to take the action with respect to files in the VFS having the tag.

Abstract: Methods, computer readable media, systems, and computing devices are provided for controlling execution instances. A method embodiment includes maintaining in a counter of a database, a count associated with a particular number of execution instances of a application registered in the database. The method includes setting for the counter, an upper number associated with a particular number of execution instances of the application allowed to be registered in the database. The method also includes receiving to the database, a request from the application to launch an execution instance of the application. The method further includes transmitting from the database to the application, a response to the request, based on the count and the upper number.

Abstract: A system and computer-implemented method of converting a contention scope attribute of a user thread executing in a multithreaded environment are described. The method includes dynamically converting the contention scope attribute of the user thread running in the multithreaded environment between a process scope and a system scope. In changing from system scope to process scope, the kernel thread to which the user thread is mapped is converted to a scheduler activation thread, the contention attribute for the user thread is reset in a threads library and the user thread is added to the run queue of a relevant virtual processor. In changing from process scope to system scope, the underlying scheduler activation kernel thread is permanently and exclusively mapped to the user thread to achieve a system scope for the thread. And a replacement scheduler activation kernel thread is created for other user threads of the same process previously sharing the original scheduler activation kernel thread.

Abstract: A system includes a portable computer having a first bus and a docking base having a second bus. A serial link (e.g., a 1394 link) couples the portable computer to the docking base. The portable computer may include a controller to convert a first bus cycle targeted for the second bus to a serial cycle. The first and second buses may each include a Peripheral Component Interconnect (PCI) bus.