Microsoft Technology Licensing, LLC

Andrew M Herron

Mehmet Iyigun

Yevgeniy Bak

Karan Mehra

Robin Andrew Alexander

Xiaozhong Xing

Eric Bluestein

Senthil Rajaram

Neal Robert Christiansen

Ravinder S Thind

Surendra Verma

William R Tipton

Shiv Kumar Rajpal

Sarosh Cyrus Havewala

Nathan Steven Obr

Jonathan M Cargille

Darren Glen Moss

Colin Watson

Christian Gregory Allred

Dana D Groff

Malcolm James Smith

Juan-Lee Pang

Daniel W H Chan

Kenneth D Ray

Paul J Leach

Charles W Kaufman

Dan Teodosiu

Rajsekhar Das

Jonathan D Schwartz

Alexey A Polyakov

Krassimir Emilov Karamfilov

Dragos Sambotin

Brian Kenneth Dewey

Bryan Stephen Matthew

Duncan G Bryce

Shi Cong

Matthew Charles Setzer

Pankaj Mohan Kamat

Daniel Chan

John Richard McDowell

Karthik Thirumalai

Gregory J Jacklin

Ankur Kasturiya

Yevgeniy M Bak

Eric M Bluestein

Shiv Rajpal

Krassimir E Karamfilov

John Mcdowell

Ducan G Bryce

A hybrid drive includes multiple parts: a performance part (e.g., a flash memory device) and a base part (e.g., a hard disk drive). A drive access system, which is typically part of an operating system of a computing device, issues input/output (I/O) commands to the hybrid drive to store data to and retrieve data from the hybrid drive. Some data can be stored in one part but not the other, and this data can be synchronized with (e.g., copied to) the other part at various times. The drive access system provides indications to the hybrid drive of when to synchronize data in one part with the other part. These indications are made so that potential interference with use of the device by the user and/or power saving modes of the device due to the synchronization is reduced.

Dirty data management for hybrid drives

A hybrid drive includes multiple parts: a performance part (e.g., a flash memory device) and a base part (e.g., a magnetic or other rotational disk drive). A drive access system, which is typically part of an operating system of a computing device, issues input/output (I/O) commands to the hybrid drive to store data to and retrieve data from the hybrid drive. The drive access system supports multiple priority levels and obtains priority levels for groups of data identified by logical block addresses (LBAs). The LBAs read while the device is operating in a power saving mode are assigned a priority level that is at least the lowest of the multiple priority levels supported by the device, increasing the likelihood that LBAs read while the device is operating in the power saving mode are stored in the performance part of the hybrid drive.

Power saving mode hybrid drive access management

A system in which a file system may operate on a volume in which the logical address extent of the volume is divided into multiple tiers, each tier providing storage having a distinct trait set by mapping the logical addresses of the volume to appropriate underlying storage systems. A volume system exposes the volume to the file system in a manner that the file system itself has awareness of the tiers, and is aware of the trait sets of each tier. The file system may thus store file system namespaces (such as directories and files) into the tiers as appropriate for the file system namespace. A provisioning system may also be provided and be configured to provision the volume to include such tiers, and if desired, to extend the tiers.

Heterogenic volume generation and use system

A hybrid drive includes multiple parts: a performance part (e.g., a flash memory device) and a base part (e.g., a magnetic or other rotational disk drive). A drive access system, which is typically part of an operating system of a computing device, issues input/output (I/O) commands to the hybrid drive to store data to and retrieve data from the hybrid drive. The drive access system assigns, based on various available information, a priority level to groups of data identified by logical block addresses (LBAs). With each I/O command, the drive access system includes an indication of the priority level of the LBA(s) associated with the I/O command. The hybrid drive determines, based on the priority level indications received from the drive access system, which LBAs are stored on which part or parts of the hybrid drive.

Assigning priorities to data for hybrid drives

The provisioning of a volume that has multiple tiers corresponding to different trait sets. The volume to be provisioned is identified along with multiple tiers that are to be in the volume. For each of the tiers that are to be provisioned within the volume, a corresponding trait set is identified as to be applied to each tier. This corresponding trait set may be based on underlying storage systems that are available at the time of provisioning, or which are anticipated to be available. The volume is then caused to be provisioned with the corresponding tiers having the corresponding trait sets. Also, the provisioning of a file, which is determined to have one or more storage traits. Based on these storage traits, the file is then caused to be assigned to an appropriate tier.

Provisioning in heterogenic volume of multiple tiers

A volume system that presents a volume having an extent of logical addresses to a file system. A volume exposure system exposes the volume to the file system in a manner that the volume has multiple tiers, each offering storage of different traits. This is performed using multiple heterogenic underlying storage systems, each having different storage system-specific traits. Each underlying storage system may be hardware, software, or a combination thereof that permits each storage system to expose storage having the particular storage system-specific traits to the file system. The volume system supports each tier by mapping logical addresses of the tier to portions of underling storage systems that are consistent with the tier traits.

Volume having tiers of different storage traits

A file system that operates on an underlying volume that has multiple tiers, each tier including a particular trait set. Upon creating or otherwise identifying a file system namespace (such as a directory or file) that is in a volume or that is to be included within the volume, a storage trait set to be applied corresponding to the file system namespace is identified. Then, the storage trait set is compared against the trait sets for the multiple tiers to identify a tier into which to store the file system namespace. The file system namespace is then caused to be stored within the identified tier. Thus, the file system is provided with a volume that has multiple tiers (each having different trait sets) to choose from in storing files.

File system operation on multi-tiered volume

A set of application programming interfaces ('APIs') is provided that enables an application to perform operations on multiple system resources as a single logical unit of work through a transaction. The application can then commit or roll back the entire group of changes as a single unit in a coordinated manner. The APIs expose functions and methods that take a reference to a transaction context, such as a handle, name, or pointer, as one of their parameters so that the application can manipulate the resource as a transacted operation. The transaction is bound to all created handles so that all operations on the resource using those handles are also transacted. In an illustrative example, the set of APIs are transacted name-based WIN32 APIs that take a transaction handle. The transacted APIs expose transacted operations to the application for durable system resources in the OS kernel, including the NTFS file system (New Technology File System) and registry.

Application programming interfaces for transacted file and registry operations

In accordance with one or more aspects, one or more portions of at least one file that have been freed are determined. One or more delete notifications are generated that identify the one or more portions of the at least one file. Each portion is identified as a range of data on a storage device, and each delete notification includes one or more ranges of data on the storage device. A determination is made as to when to send the generated delete notifications based on one or more threshold-based criteria. These generated delete notifications are then sent to a storage stack.

Use of delete notifications by file systems and applications to release storage space

A delete notification can be received at a storage stack filter in a storage stack. It can be determined whether the delete notification applies to an entire storage device. If the delete notification does not apply to the entire storage device, a first set of actions can be taken with the storage stack filter in response to the delete notification. If the delete notification does apply to the entire storage device, a second set of actions can be taken with the storage stack filter in response to the delete notification.

Delete notifications for an entire storage device

A packed command can be received at a storage device. The packed command can include an indicator of a source data location in the storage device and an indicator of a destination data location in the storage device. In response to receiving the packed command, a storage map table in the storage device can be updated. Also, a storage processing guide can be sent to a storage device. The processing guide can include a stream indicator associating the processing guide with a storage command stream. A set of storage commands can also be sent to the storage device. One or more of the commands in the set can each include a stream indicator that matches the stream indicator in the processing guide and identifies the command with the stream.

Packed storage commands and storage command streams

In accordance with one or more aspects, one or more portions of each of multiple files that have been freed are determined. One or more delete notifications are generated identifying the one or more portions of the multiple files. Each portion is identified as a range of data on a storage device, and each delete notification includes one or more ranges of data on the storage device. These generated delete notifications are then sent to a storage stack. Additionally, an application can determine that one or more ranges of data of a storage device are to be freed and send a delete notification, in the absence of a file system on the device, to the storage stack identifying the one or more ranges of data of the storage device that are to be freed.

Growing community of inventors

Redmond, WA, United States of America

Andrew M Herron