Data storage device providing data maintenance services

• US 10,444,998 B1
• Filed: 03/30/2015
• Issued: 10/15/2019
• Est. Priority Date: 10/24/2013
• Status: Active Grant

• Current Assignee: Sandisk Technologies Incorporated (Western Digital Corporation)
• Original Assignee: Western Digital Technologies Incorporated (Western Digital Corporation)
• Inventors: Obukhov, Dmitry S., Bombet, Marc A.
• Primary Examiner(s): Blust, Jason W
• Application Number:
  US14/673,392
• Time in Patent Office: 1,660 Days
• Field of Search: None
• CPC Class Codes: G06F 3/061 Improving I/O performance
• CPC Class Codes: G06F 3/0641 De-duplication techniques
• CPC Class Codes: G06F 3/0644 Management of space entities, e.g. partitions, extents, pools
• CPC Class Codes: G06F 3/0658 Controller construction arrangements
• CPC Class Codes: G06F 3/0664 at device level, e.g. emulation of a storage device or system
• CPC Class Codes: G06F 3/0679 Non-volatile semiconductor memory device, e.g. flash memory, one time programmable memory [OTP]
• CPC Class Codes: G06F 3/0688 Non-volatile semiconductor memory arrays

Abstract

Systems and methods are disclosed for performing data maintenance and/or other data operations within a data storage device. A data storage device is disclosed including a device controller, non-volatile data storage, an interface for receiving data storage commands from a host system, a framework including a memory for storing xenocode code received from the host system, and a processor for executing the xenocode. The device controller is configured to write user data received from the host system to a first partition of the non-volatile data storage in response to a storage command received via the interface from the host system. The xenocode, when executed, causes the processor to read the user data from the first partition of the non-volatile data storage, perform data operations on the read user data, and write results associated with the data operations in a second partition of the non-volatile data storage.

Claims

1. A data storage device comprising:

non-volatile data storage;

an interface for receiving data storage commands from a host system; and

a framework including a memory for storing xenocode received from the host system and a processor for executing the xenocode, wherein the xenocode comprises executable code configured by the host system, and wherein the configured executable code is further compiled by the host system prior to the memory storing the xenocode received from the host system;

wherein the data storage device is configured to write user data received from the host system to a first partition of the non-volatile data storage in response to a storage command received via the interface from the host system; and

wherein the xenocode, when executed, causes the processor to;

read the user data from the first partition of the non-volatile data storage without using the interface;

perform data operations on the read user data; and

write results associated with the data operations in a second partition of the non-volatile data storage without using the interface.

2. The data storage device of claim 1, wherein the xenocode further cause the data storage device to provide at least a portion of the results to the host system.

3. The data storage device of claim 2, wherein said providing the at least a portion of the results to the host system is performed in response to a request from the host system.

4. The data storage device of claim 2, wherein said providing the at least a portion of the results to the host system is performed according to a predetermined schedule.

5. The data storage device of claim 1, wherein the xenocode comprises a non-native software application.

6. The data storage device of claim 1, wherein the first and second partitions of the non-volatile data storage are physical partitions.

7. The data storage device of claim 1, wherein the first and second partitions of the non-volatile data storage are logical partitions.

8. The data storage device of claim 1, wherein the data storage device is configured to determine a low-duty period of time and cause said data operations to be performed at least partially during the low-duty period of time.

9. The data storage device of claim 1, wherein the data storage device is configured to cause the data operations to be performed in coordination with execution of firmware of the data storage device.

10. The data storage device of claim 1, wherein the data operations include one or more of indexing, data de-duplication, virus searching, and statistical analysis.

11. The data storage device of claim 1, wherein the data storage device is further configured to prevent the host system from writing to the second partition.

12. The data storage device of claim 1, wherein the processor is part of a device controller.

13. A method of performing data operations in a data storage device comprising non-volatile data storage and a memory, the method comprising:

receiving xenocode comprising processor executable instructions from a host system, wherein the xenocode comprises executable code configured by the host system, and wherein the configured executable code is further compiled by the host system;

storing the xenocode in a memory of a framework for storing and executing the xenocode in a data storage device, wherein storing the xenocode in the memory occurs after the configured executable code is compiled by the host system;

receiving a storage command from the host system over a communication interface;

writing user data associated with the storage command and received from the host system to a first partition of a non-volatile data storage of the data storage device in response to receiving the storage command;

executing the xenocode to cause a processor of the framework to;

read the user data from the first partition of the non-volatile data storage without using the communication interface;

perform data operations on the read user data; and

write results associated with the data operations in a second partition of the non-volatile data storage without using the communication interface.

14. The method of claim 13, further comprising providing at least a portion of the results to the host system.

15. The method of claim 14, wherein said providing the at least a portion of the results to the host system is performed in response to a request from the host system.

16. The method of claim 14, wherein said providing the at least a portion of the results to the host system is performed according to a predetermined schedule.

17. The method of claim 13, wherein the xenocode comprises a non-native virtual software application.

18. The method of claim 13, wherein the first and second partitions of the non-volatile data storage are physical partitions.

19. The method of claim 13, wherein the first and second partitions of the non-volatile data storage are logical partitions.

20. The method of claim 13, further comprising determining a low-duty period of time and performing said data operations at least partially during the low-duty period of time.

21. The method of claim 13, wherein the data operations include one or more of indexing, data de-duplication, virus searching, and statistical analysis.

22. The method of claim 13, further comprising preventing the host system from writing to the second partition.