Abstract: In particular embodiments, a method may include automatically determining that a mobile computing device is unlocked and away from a pre-determined trusted user associated with the mobile computing device, where the determining that the mobile computing device is away from the pre-determined trusted user is based on communication between the mobile computing device and an identification device carried by the trusted user, and by the mobile computing device, automatically erasing all software and data on the mobile computing device. The identification device may include a BLUETOOTH fob, a Near-Field Communication (NFC) tag, or a Radio-Frequency Identification (RFID) tag. The method may include communicating with the identification device to verify that the identification device is in a vicinity of the mobile computing device. The communication may be via a communication protocol such as BLUETOOTH, a Near-Field Communication (NFC), or Radio-Frequency Identification (RFID).

Abstract: In one embodiment, a mobile computing device automatically determines an occurrence of a security event associated with the mobile computing device, and automatically erase all software and data on the mobile computing device.

Abstract: A mobile computing device may automatically determine an occurrence of a security event associated with the device, and automatically erase all software and data on the device. The security event may be the mobile computing device being unlocked and away from a trusted location or user associated with the device, or the device moving a pre-determined distance over a pre-determined amount of time while unlocked, or a user performing an incorrect touch gesture to unlock the mobile computing device, or entry of an incorrect password a pre-determined consecutive number of times. The mobile computing may display a visual cue to the user to prompt the user to perform the incorrect touch gesture. Software and data on the mobile computing device may be automatically erased without receiving instructions from another computing device, or may be erased when the mobile computing device establishes a network connection with another computing device.

Abstract: A data object management scheme for storing a large plurality of small data objects (e.g., image files) in small number of large object stack file for storage in secondary storage (e.g., hard disks). By storing many individual data objects in a single object stack file, the number of files stored in the secondary storage is reduced by several orders of magnitude, from the billions or millions to the hundreds or so. Index data for each object stack file is generated and stored in primary storage to allow efficient and prompt access to the data objects. Requests to store or retrieve the data objects are made using HTTP messages including file identifiers that identify the files storing the data objects and keys identifying the data objects. A file server stores or retrieves the data object from secondary storage of a file server without converting the requests to NSF or POSIX commands.

Abstract: A data object management scheme for storing a large plurality of small data objects (e.g., image files) in small number of large object stack file for storage in secondary storage (e.g., hard disks). By storing many individual data objects in a single object stack file, the number of files stored in the secondary storage is reduced by several orders of magnitude, from the billions or millions to the hundreds or so. Index data for each object stack file is generated and stored in primary storage to allow efficient and prompt access to the data objects. Requests to store or retrieve the data objects are made using HTTP messages including file identifiers that identify the files storing the data objects and keys identifying the data objects. A file server stores or retrieves the data object from secondary storage of a file server without converting the requests to NSF or POSIX commands.

Abstract: A data object management scheme for storing a large plurality of small data objects (e.g., image files) in small number of large object stack file for storage in secondary storage (e.g., hard disks). By storing many individual data objects in a single object stack file, the number of files stored in the secondary storage is reduced by several orders of magnitude, from the billions or millions to the hundreds or so. Index data for each object stack file is generated and stored in primary storage to allow efficient and prompt access to the data objects. Requests to store or retrieve the data objects are made using HTTP messages including file identifiers that identify the files storing the data objects and keys identifying the data objects. A file server stores or retrieves the data object from secondary storage of a file server without converting the requests to NSF or POSIX commands.

Abstract: A system is provided to improve performance of a storage system. The system comprises a multi-tier buffer cache. The buffer cache may include a global cache to store resources for servicing requests issued from one or more processes at the same time, a free cache to receive resources from the global cache and to store the received resources as free resources, and a local cache to receive free resources from the free cache, the received free resources to store resources that can be accessed by a single process at one time. The system may further include a buffer cache manager to manage transferring resources from the global cache to the free cache and from the free cache to the local cache.

Abstract: A system is provided to improve performance of a storage system. The system comprises a multi-tier buffer cache. The buffer cache may include a global cache to store resources for servicing requests issued from one or more processes at the same time, a free cache to receive resources from the global cache and to store the received resources as free resources, and a local cache to receive free resources from the free cache, the received free resources to store resources that can be accessed by a single process at one time. The system may further include a buffer cache manager to manage transferring resources from the global cache to the free cache and from the free cache to the local cache.