CN109032897A - Data scheduling method, host and solid state disk - Google Patents

Abstract

The embodiment of the present application discloses a data scheduling method, a host computer and a solid-state hard disk, which are used to export debugging information online through a custom debugging interface set in a custom area, thereby improving the accuracy of debugging fault information. The method in the embodiment of the present application includes: the host sends a debugging command to the SSD SSD through a custom debugging interface and a custom debugging interface address corresponding to the custom debugging interface, and the custom debugging interface is set on the bus and the interface by the SSD A standard PCIe device, the self-defined debugging interface corresponds to the target configuration space of the self-defined area in the PCIe device, and the target configuration space is used to store debugging data; the host sends the SSD to the SSD through the self-defined debugging interface An export command; the host receives the internal debugging information of the SSD through the custom debugging interface.

Description

Data Scheduling Method, Host, and Solid State Disk

technical field

The present application relates to the technical field of computers, in particular to a data scheduling method, a host computer and a solid-state hard disk.

Background technique

With the development of technologies such as the Internet, cloud computing, and the Internet of Things, solid-state drives, as a new generation of storage devices, have been widely used.

At present, due to the simple interaction between the solid state disk and the host, when the solid state disk (SSD) fails, it is usually difficult for the host to locate the cause of the failure of the solid state disk. Mail it to the manufacturer, and the manufacturer will locate the cause of the fault.

However, after the manufacturer receives the solid-state hard drive by mail, since the solid-state hard drive is not at the fault site, important on-site fault information may be lost, which makes it impossible for the manufacturer to obtain accurate fault information when detecting the cause of the fault.

Contents of the invention

The embodiment of the present application provides a data scheduling method, a host, and a solid-state hard disk, which can export debugging information online through a custom debugging interface set in a custom area, thereby improving the accuracy of debugging fault information.

The embodiment of this application provides a data scheduling method, including:

The host sends a debugging command and the corresponding custom debugging interface address of the custom debugging interface to the SSD through the custom debugging interface, and the custom debugging interface is set on a bus and an interface standard (peripheral component interconnect express, PCIe) device by the SSD , the self-defined debugging interface corresponds to the target configuration space of the self-defined area in the PCIe device, and the target configuration space is used to store debugging data;

The host sends an export command to the SSD through the custom debugging interface;

The host receives debugging information inside the SSD through the custom debugging interface.

Optionally, before the host sends a debugging command and a custom debugging interface address corresponding to the custom debugging interface to the SSD through the custom debugging interface, the method further includes:

When the host determines that the SSD fails, the host determines whether the PCIe device can be identified;

If not, the host scans the host itself to acquire the information of the PCIe device.

Optionally, the host scanning the host itself to obtain the information of the PCIe device includes:

When the host is a Linux host, the Linux host obtains the information of the PCIe device according to a scan command;

or,

When the host is a Windows host, the Windows host searches for information about the PCIe device in a device manager of the Windows host.

The embodiment of this application provides another data scheduling method, including:

The solid-state disk SSD sets a custom debugging interface at the bus and interface standard PCIe equipment, and the self-defining debugging interface corresponds to the target configuration space of the self-defined area in the PCIe device, and the target configuration space is used to store debugging data;

The SSD receives the debugging command sent by the host and the custom debugging interface address corresponding to the custom debugging interface through the custom debugging interface;

The SSD collects debugging information inside the SSD through an error correction module in the SSD;

The SSD stores the debugging information in the target configuration space;

The SSD receives an export command sent by the host through the custom debugging interface;

The SSD exports the internal debugging information of the SSD to the host through the custom debugging interface.

The embodiment of this application provides a host, including:

The first sending unit is used to send a debugging command and a custom debugging interface address corresponding to the custom debugging interface to the solid state disk SSD through a custom debugging interface, and the custom debugging interface is set on the bus and interface standard by the SSD PCIe device, the self-defined debugging interface corresponds to the target configuration space of the self-defined area in the PCIe device, and the target configuration space is used to store debugging data;

A second sending unit, configured to send an export command to the SSD through the custom debugging interface;

A receiving unit, configured to receive internal debugging information of the SSD through the custom debugging interface.

Optionally, the host also includes:

A first judging unit, configured to judge whether the PCIe device can be identified when it is determined that the SSD fails;

The scanning unit is configured to, when it is determined that the PCIe device cannot be identified, scan to acquire the information of the PCIe device.

Optionally, the scanning unit specifically includes:

When the host is a Linux host, the information of the PCIe device is obtained according to a scan command;

or,

When the host is a Windows host, search for information about the PCIe device in a device manager of the Windows host.

The embodiment of the present application provides a solid-state hard disk, including:

The setting unit is used to set a custom debugging interface on the bus and interface standard PCIe equipment, and the self-defining debugging interface corresponds to the target configuration space of the self-defined area in the PCIe device, and the target configuration space is used to store debugging data;

The receiving unit is configured to receive the debugging command sent by the host through the custom debugging interface and the custom debugging interface address corresponding to the custom debugging interface;

A collection unit, configured to collect debugging information inside the SSD through an error correction module in the SSD;

a storage unit, configured to store the debugging information in the target configuration space;

A third sending unit, configured to receive an export command sent by the host through the custom debugging interface;

An exporting unit, configured to export the internal debugging information of the SSD to the host through the custom debugging interface.

An embodiment of the present application provides a host, and the host has a function of implementing the behavior of the host in the above data scheduling method for the host. This function can be implemented by hardware or by executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

An embodiment of the present application provides a solid-state hard disk, and the solid-state hard disk has a function of implementing the behavior of the solid-state hard disk in the above data scheduling method for the solid-state hard disk. This function can be implemented by hardware or by executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

An embodiment of the present application provides a computer storage medium, and the computer storage medium is used for storing computer software instructions used by the above-mentioned storage device, including a program designed for executing a host.

An embodiment of the present application provides a computer storage medium, and the computer storage medium is used for storing computer software instructions used by the above-mentioned storage device, including a program for executing a program designed for a solid-state hard disk.

An embodiment of the present application provides a computer program product, where the computer program product includes computer software instructions, and the computer software instructions can be loaded by a processor to implement the flow of the above data scheduling method.

As can be seen from the above technical solutions, the embodiment of the present application has the following advantages: the host sends a debugging command and the corresponding custom debugging interface address to the SSD through the custom debugging interface set by the solid state disk on the PCIe device, and then the host Send an export command to the SSD through the custom debugging interface, and finally receive the internal debugging information of the SSD through the custom debugging interface, so the host can obtain important on-site fault information in real time through the custom debugging interface, thereby correctly locating the cause of the fault and improving the detection of the host The accuracy of the reason for the failure of the SSD.

Description of drawings

FIG. 1 is a schematic diagram of an embodiment of a data scheduling method in an embodiment of the present application;

Figure 2 is a schematic diagram of another embodiment of the data scheduling method in the embodiment of the present application

FIG. 3 is a schematic diagram of another embodiment of the data scheduling method in the embodiment of the present application;

FIG. 4 is a schematic diagram of an embodiment of a host in the embodiment of the present application;

FIG. 5 is a schematic diagram of another embodiment of the host in the embodiment of the present application;

FIG. 6 is a schematic diagram of an embodiment of a solid-state hard disk in the embodiment of the present application;

FIG. 7 is a schematic diagram of another embodiment of a solid state disk in the embodiment of the present application.

Detailed ways

The embodiment of the present application provides a data scheduling method, a host computer, and a solid-state disk, which are used to export debugging information online through a custom debugging interface set in a custom area, thereby improving the accuracy of debugging fault information.

Please refer to FIG. 1 . FIG. 1 is a schematic diagram of an embodiment of the data scheduling method in the embodiment of the present application. The following describes an embodiment of the data scheduling method in FIG. 1 from the host side.

An embodiment of the data recovery method of the solid-state hard disk in the embodiment of the present application includes:

101. The host sends a debugging command and a custom debugging interface address to the SSD through a custom debugging interface;

In this embodiment, in order to export debugging information inside the SSD, the host may send a debugging command and a custom debugging interface address corresponding to the custom debugging interface to the SSD through the custom debugging interface.

Specifically, the PCIe device of the SSD is provided with a configuration space, and the configuration space corresponds to various interfaces on the PCIe device, including interfaces in the area of the basic header (basic header) and interfaces in the area of the custom header (vender defined header) , the interface of the area of the PCIe header, etc. Through the configuration space of the PCIe device, the host can interact with the SSD for various information. The custom debugging interface is set by the SSD at the position corresponding to the custom area in the PCIe device. The custom interface corresponds to the configuration space of the custom area in the PCIe device, and the configuration space of the custom area is configured by the SSD itself. The custom interface also corresponds to the custom debugging interface address. Through the custom debugging interface address, the host can send various commands to the solid state disk, and the solid state disk can store the debugging information in the target corresponding to the custom debugging interface address. configuration space.

And the self-defined debugging interface is the key of the present invention, the self-defined debugging interface is configured by the solid-state hard disk, is that the solid-state hard disk divides a part of the configuration space from the self-defined area as the self-defined debugging space, that is to say, the solid-state hard disk is subordinate to the self-defined debugging space. A part of the interfaces in the defined area is divided for sending commands and storing debugging information. In the embodiment of the present application, this part of the interfaces is called a custom debugging interface. This part divided by the solid state disk is used as the configuration space of the custom debugging space, which is called the target configuration space in the embodiment of the present application. Therefore, it can also be said that the custom debugging interface corresponds to the target configuration space in the custom area of the PCIe device. The target configuration space can be used to store debugging information for detecting and locating the cause of a solid-state disk failure.

Referring to Table 1 below, Table 1 is a configuration table of the configuration space of the PEIe device in the embodiment of the present application. The host and the SSD exchange information through the configuration space. Referring to Table 1, each interface from 00h to 184h corresponds to its own offset address, and the offset address will be referred to as address for short in the following. Interfaces from 00h to 34h correspond to the configuration space defined by the PCIe standard, and interfaces from 40h to 60h belong to the configuration space of the custom area. The size of the configuration space corresponding to each interface is fixed, generally 16 bytes or 32 bytes.

Table 1

In the custom configuration space corresponding to the 40h～60h interface, 54h, 58h, 5Ch, and 60h are the configuration spaces for debugging fault information allocated by the solid state disk in the present invention. The host can send debugging commands to the SSD's custom debugging configuration space through these four custom debugging interfaces (that is, custom debugging addresses), and requires the SSD to collect debugging information; and, the host can send corresponding commands through these custom debugging interfaces. The address of the custom debugging interface for the custom debugging interface. The configuration space corresponding to the 54h interface is further divided into three sub-configuration spaces, which are used to store the jump value of the primary bootloader (primary bootloader jump value, PBL jump value), upper address (upperaddress), delete command (delete command) ); the configuration space corresponding to the 58h interface is used to store the PBL lower address (PBL lower address); the configuration space corresponding to the 5Ch interface is used to store the PBL data mark (PBL data mark); the configuration space corresponding to the 60h interface is used for the PBL data (PBL data). In this embodiment, the configuration space for custom debugging is collectively referred to as the target configuration space.

102. The host sends an export command to the SSD through a custom debugging interface;

In this embodiment, after the host sends the debugging command and the address of the custom debugging interface to the custom debugging configuration space of the SSD through the custom debugging interface, it can send an export command to the SSD through the custom debugging interface, requesting to export the internal debugging information of the SSD. data.

It should be noted that, since the configuration space corresponding to each interface can generally store 16 bytes or 32 bytes of data, the configuration space corresponding to each interface is limited. This requires the host to limit the exported data every time it sends an export command. The amount of data, so the host can continuously send export commands to the SSD through the custom debug interface.

103. The host receives debugging information inside the SSD through a custom debugging interface.

After the host sends the export command to the SSD through the custom debugging interface, the SSD will collect the internal debugging information of the SSD through the built-in error correction module, and save the debugging information to the target configuration space corresponding to the custom debugging interface. The debugging information includes debugging logs and various parameters of the SSD (including management data and metadata). Through the above steps, the host can export the internal debugging information of the SSD through the custom debugging interface, so as to be used by technicians to detect the cause of the SSD failure.

It should be noted that the operation steps in this embodiment can be used not only to detect the debugging information of SSD power failure, but also to detect the debugging information of SSD failure without power failure but communication interruption, which is not limited here. .

In the embodiment of this application, the host sends the debugging command and the corresponding custom debugging interface address to the SSD through the custom debugging interface set by the solid state disk on the PCIe device, and then the host sends the export command to the SSD through the custom debugging interface , and finally receive the debugging information inside the SSD through the custom debugging interface, so the host can obtain important on-site fault information in real time through the custom debugging interface, thereby correctly locating the cause of the fault and improving the accuracy of the host in detecting the cause of the solid state drive failure.

An embodiment of the data scheduling method in the embodiment of the present application has been described above from the host side. Another embodiment of the data scheduling method in the embodiment of the present application is described below from the SSD side. Referring to FIG. 2, FIG. 2 is another embodiment of the data scheduling method in the embodiment of the present application.

Another embodiment of the data scheduling method in the embodiment of the present application includes:

201. The SSD sets a custom debugging interface on the PCIe device;

In this embodiment, the SSD can first set a custom debugging interface in a custom area of the PCIe device, each custom debugging interface corresponds to a different configuration space, and corresponds to a different offset address (abbreviated as an address). The self-defined debugging interfaces are 54h, 58h, 5Ch and 60h mentioned above in step 101 of FIG. 1 . The specific self-assignment of the custom interface by the SSD has been described in detail in the aforementioned step 101 of FIG. 1 , and will not be repeated here.

202. The SSD receives the debugging command sent by the host and the address of the custom debugging interface through the custom debugging interface;

In this embodiment, after the PCIe device completes the setting of the custom debugging interface, the SSD can receive the debugging command sent by the host through the custom debugging interface, and receive the custom debugging interface address corresponding to the custom debugging interface, and the custom debugging interface The address corresponds to the configuration space of the custom debugging interface, that is, the target configuration space.

203. The SSD collects debugging information inside the SSD through an error correction module in the SSD;

After the SSD receives the debugging command, it can collect the debugging information related to the fault inside the SSD through the error correction (debug) module inside the SSD.

204. The SSD stores the debugging information in the target configuration space;

After the SSD finishes collecting the debugging information, it can store the debugging information in the target configuration space corresponding to the address of the custom debugging interface for use by the host.

205. The SSD receives the export command sent by the host through the custom debugging interface;

In this embodiment, after the SSD stores the debugging information in the target configuration space, it can receive the export command sent by the host through the custom debugging interface.

206. The SSD exports debugging information inside the SSD to the host through a custom debugging interface.

In this embodiment, after the SSD receives the export command sent by the host, it can export the internal debugging information of the SSD to the host through the custom debugging interface of the PCIe device.

It should be noted that the SSD can continuously receive the export commands sent by the host through the custom debugging interface of the PCIe device, so the SSD exports debugging information to the host one by one through each export command. Generally speaking, each interface in the SSD PCIe device can transmit 16 bytes or 32 bytes of data, so according to the received export command, the SSD can only export a limited amount of data such as 16 bytes or 32 bytes. . Because of this, the host needs to send export commands continuously, so that the SSD can collect debugging information.

In the embodiment of this application, the SSD receives the debugging command sent by the host and the address of the custom debugging interface through the custom debugging interface preset in the PCIe device, and then collects the debugging information inside the SSD through the error correction module inside the SSD, and sends the debugging information to Stored in the target configuration space, when the SSD receives the export command sent by the host through the custom debugging interface, it can export the internal debugging information of the SSD to the host through the custom debugging interface, so that the host can obtain important information in real time through the custom debugging interface. On-site failure information, so as to correctly locate the cause of the failure, and improve the accuracy of the host to detect the cause of the solid-state hard disk failure.

The above describes the data scheduling method in the embodiment of the present application from the side of the solid-state hard disk. Referring to FIG. 3 , FIG. 3 is another embodiment of the data scheduling method in the embodiment of the present application.

Another embodiment of the data scheduling method in the embodiment of the present application includes:

301. The SSD sets a custom debugging interface on the PCIe device;

Step 301 in this embodiment is similar to step 201 in the foregoing embodiment described in FIG. 2 , and will not be repeated here.

302. When the host determines that the SSD fails, the host determines whether the PCIe device can be identified;

In this embodiment, when the host determines that the SSD is faulty, the host may first determine whether the PCIe device set in the SSD can be identified.

It should be noted that the failure of the SSD mentioned in the embodiment of the present application may be a failure of the SSD being powered off, or a failure of communication interruption between the SSD and the host, which is not specifically limited here.

If the PCIe device in the SSD can be identified, step 304 is performed without scanning the SSD to identify the PCIe device in the SSD; if not, step 303 is performed.

303. The host scans the host itself to obtain the information of the PCIe device;

If the host cannot recognize the PCIe in the SSD, the host can scan to obtain the information of the PCIe device.

Further, when the host is a Linux host, the Linux host can obtain the information of the PCIe device according to the scan command. For example, the scan command could be:

echo 1>/sys/bus/pci/rescan.

When the host is a Windows host, the Windows host can refresh and search for PCIe device information in the device manager of the Windows host.

The method for the host to scan the host itself to obtain the information of the PCIe device may vary depending on the operating system of the host, which is not specifically limited here.

304. The SSD collects debugging information inside the SSD through an error correction module in the SSD;

305. The SSD stores the debugging information in the target configuration space;

Steps 304 and 305 in this embodiment are similar to steps 203 and 204 in the embodiment described above in FIG. 2 , and are not specifically limited here.

306. The host sends an export command to the SSD through a custom debugging interface;

This step is similar to step 102 in the embodiment described above in FIG. 1 , and is not specifically limited here.

307. The SSD exports debugging information inside the SSD to the host through a custom interface.

This step is similar to step 206 in the embodiment described above in FIG. 2 , and is not specifically limited here.

In the embodiment of this application, since the host can determine whether the PCIe device can be recognized before sending the debugging command to the SSD, if it cannot be recognized, then scan and identify to obtain the information of the PCIe device, so that the custom debugging interface can be found to export the SSD from the SSD The debugging information of the failure, so the practicability of the technical solution of the embodiment of the present application is further improved. On this basis, it can be ensured that the host can obtain important on-site failure information and correctly locate the cause of the failure, which not only improves the host's detection of SSD failure causes. The accuracy of the method improves the practicability of the technical solution of the present invention.

The data scheduling method in the embodiment of the present application is described above, and the host in the embodiment of the present application is described below, please refer to FIG. 4, which is a schematic diagram of an embodiment of the host in the embodiment of the present application;

An embodiment of the host in the embodiment of this application includes:

The first sending unit 401 is used to send a debug command and a custom debug interface address corresponding to the custom debug interface to the solid-state disk SSD through a custom debug interface. The custom debug interface is set on the bus and the interface standard PCIe device by the SSD. The custom debugging interface corresponds to the target configuration space of the custom area in the PCIe device, and the target configuration space is used to store debugging data;

The second sending unit 402 is configured to send an export command to the SSD through a custom debugging interface;

The receiving unit 403 is configured to receive internal debugging information of the SSD through a custom debugging interface.

Optionally, the host also includes:

The first judging unit 404 is configured to judge whether the PCIe device can be identified when it is determined that the SSD fails;

The scanning unit 405 is configured to, when it is determined that the PCIe device cannot be identified, scan to obtain information about the PCIe device.

Optionally, the scanning unit 405 specifically includes:

When the host is a Linux host, the information of the PCIe device is obtained according to a scan command;

or,

When the host is a Windows host, search for information about the PCIe device in a device manager of the Windows host.

In the embodiment of the present application, the first sending unit 401 sends the debugging command and the custom debugging interface address corresponding to the custom debugging interface to the SSD through the custom debugging interface set by the solid state disk on the PCIe device, and then the second sending unit 402 sends the debugging command through the self-defined debugging interface Define the debugging interface to send export commands to the SSD, and finally receive the internal debugging information of the SSD through the custom debugging interface, so the host can obtain important on-site fault information in real time through the custom debugging interface, thereby correctly locating the cause of the fault and improving the detection of the solid state drive by the host. The accuracy of the cause of the failure.

Referring to FIG. 5, FIG. 5 is a schematic diagram of another embodiment of the host in the embodiment of the present application. Another embodiment of the solid-state hard disk in the embodiment of the present application includes:

The solid-state hard drive 500 may have relatively large differences due to different configurations or performances, and may include one or more processors (central processing units, CPU) 501 (for example, one or more processors) and memory 505, the memory 505 There are one or more applications or data stored in it.

Wherein, the storage 505 may be a volatile storage or a persistent storage. The program stored in the memory 505 may include one or more modules, and each module may include a series of instructions to operate on the server. Furthermore, the processor 501 may be configured to communicate with the memory 505 , and execute a series of instruction operations in the memory 505 on the solid state disk 500 .

The solid state hard drive 500 can also include one or more power supplies 502, one or more wired or wireless network interfaces 503, one or more input and output interfaces 504, and/or, one or more operating systems, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.

It should be noted that the storage 505 in this embodiment may use a storage hard disk with a SATA interface, which is not specifically limited here. In addition, the solid state hard disk 500 in this embodiment may not be provided with a power-down protection device, and may only be provided with one processor 501 , which is not specifically limited here.

The process executed by the processor 501 in the solid state disk 500 in this embodiment is similar to the process described in the above-mentioned embodiments shown in FIGS. 1 to 3 , and will not be repeated here.

The beneficial effect of the embodiment of the present application is that the processor 501 can obtain important on-site fault information through the custom debugging interface set by the solid-state hard drive on the PCIe device, thereby correctly locating the cause of the fault and improving the accuracy of the host to detect the cause of the solid-state hard drive failure .

The embodiment of the present application also provides a computer storage medium, which is used to store computer software instructions used by the aforementioned host, including a program for executing a program designed for the host.

The host in the embodiment of the present application has been described above, and the solid state disk in the embodiment of the present application will be described below. Referring to FIG. 6, FIG. 6 is an embodiment of a solid state disk in the embodiment of the present application.

An embodiment of the solid-state hard disk in the embodiment of the present application includes:

The setting unit 601 is used to set a custom debugging interface on the bus and interface standard PCIe devices, the custom debugging interface corresponds to the target configuration space of the custom area in the PCIe device, and the target configuration space is used to store debugging data;

The receiving unit 602 is configured to receive the debugging command sent by the host through the custom debugging interface and the custom debugging interface address corresponding to the custom debugging interface;

The collection unit 603 is used to collect debugging information inside the SSD through the error correction module in the SSD;

a storage unit 604, configured to store debugging information in the target configuration space;

The third sending unit 605 is configured to receive an export command sent by the host through a custom debugging interface;

The exporting unit 606 is configured to export debugging information inside the SSD to the host through a custom debugging interface.

In the embodiment of this application, the receiving unit 602 receives the debugging command and the address of the custom debugging interface sent by the host through the custom debugging interface preset by the PCIe device through the setting unit 601, and then the collecting unit 603 collects the debugging information inside the SSD through the error correction module , the storage unit 604 stores the debugging information in the target configuration space. When the SSD receives the export command sent by the host through the custom debugging interface, the export unit 606 can export the internal debugging information of the SSD to the host through the custom debugging interface, so it can The host can obtain important on-site fault information in real time through the custom debugging interface, so as to correctly locate the cause of the fault and improve the accuracy of the host to detect the cause of the solid-state hard disk failure.

Please refer to FIG. 7 . FIG. 7 is a schematic diagram of another embodiment of the solid state disk in the embodiment of the present application.

Another embodiment of the solid-state hard disk in the embodiment of the present application includes:

The solid-state hard disk 700 may have relatively large differences due to different configurations or performances, and may include one or more processors (central processing units, CPU) 701 (for example, one or more processors) and memory 705, the memory 705 There are one or more applications or data stored in it.

Wherein, the storage 705 may be a volatile storage or a persistent storage. The program stored in the memory 705 may include one or more modules, and each module may include a series of instructions to operate on the server. Furthermore, the processor 701 may be configured to communicate with the memory 705 , and execute a series of instruction operations in the memory 705 on the solid state disk 700 .

The solid state hard drive 700 can also include one or more power supplies 702, one or more wired or wireless network interfaces 703, one or more input and output interfaces 704, and/or, one or more operating systems, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.

It should be noted that the storage 705 in this embodiment may use a storage hard disk with a SATA interface, which is not specifically limited here. In addition, the solid state hard disk 700 in this embodiment may not be provided with a power-off protection device, and may only be provided with one processor 701 , which is not specifically limited here.

The process executed by the processor 701 in the solid state disk 700 in this embodiment is similar to the process described in the above-mentioned embodiments shown in FIG. 1 to FIG. 3 , and will not be repeated here.

The beneficial effect of the embodiment of the present application is that the processor 701 can preset a custom debugging interface on the PCIe device, and collect the internal debugging information of the SSD through the error correction module according to the received debugging command, and finally pass the self-defined debugging information according to the received export command. Define the debugging interface to export the debugging information inside the SSD to the host, so that the host can obtain important on-site fault information in real time through the custom debugging interface, thereby correctly locating the cause of the fault and improving the accuracy of the host in detecting the cause of the SSD failure.

The embodiment of the present application also provides a computer storage medium, which is used for storing computer software instructions used for the aforementioned solid-state hard disk, including a program for executing a program designed for the solid-state hard disk.

An embodiment of the present application further provides a computer program product, where the computer program product includes computer software instructions, and the computer software instructions can be loaded by a processor to implement the method flow in the foregoing embodiments shown in FIGS. 1 to 3 .

Those skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the above-described system, device and unit can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

If the integrated unit is realized in the form of a software function unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or part of the contribution to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , including several instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-OnlyMemory), random access memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program codes.

Claims (10)

1. A method for scheduling data, comprising:

the host sends a debugging command and a custom debugging interface address corresponding to the custom debugging interface to a Solid State Disk (SSD) through the custom debugging interface, the custom debugging interface is arranged on a bus and interface standard PCIe (peripheral component interconnect express) device by the SSD, the custom debugging interface corresponds to a target configuration space of a custom area in the PCIe device, and the target configuration space is used for storing debugging data;

the host sends a export command to the SSD through the custom debugging interface;

and the host receives debugging information inside the SSD through the custom debugging interface.

2. The method of claim 1, wherein before the host sends a debug command and a custom debug interface address corresponding to the custom debug interface to the SSD through the custom debug interface, the method further comprises:

when the host determines that the SSD fails, the host judges whether the PCIe device can be identified;

if not, the host scans the information of the PCIe equipment acquired by the host.

3. The method of claim 2, wherein the host scanning the host itself for information about the PCIe device comprises:

when the host is a Linux host, the Linux host acquires information of the PCIe equipment according to a scanning command;

or,

and when the host is a Windows host, the Windows host searches the information of the PCIe equipment in the equipment manager of the Windows host.

4. A method for scheduling data, comprising:

the method comprises the steps that a Solid State Disk (SSD) sets a custom debugging interface on a bus and interface standard PCIe device, wherein the custom debugging interface corresponds to a target configuration space of a custom area in the PCIe device, and the target configuration space is used for storing debugging data;

the SSD receives a debugging command sent by a host and a custom debugging interface address corresponding to the custom debugging interface through the custom debugging interface;

the SSD collects debugging information inside the SSD through an error correction module in the SSD;

the SSD stores the debugging information in the target configuration space;

the SSD receives a lead-out command sent by a host through the custom debugging interface;

and the SSD exports debugging information inside the SSD to the host through the custom debugging interface.

5. A host, comprising:

a processor, a memory, an input-output device, and a bus;

the processor, the memory and the input and output equipment are respectively connected with the bus;

the processor is configured to perform the steps of:

sending a debugging command and a custom debugging interface address corresponding to the custom debugging interface to a Solid State Disk (SSD) through the custom debugging interface, wherein the custom debugging interface is arranged on a bus and interface standard PCIe (peripheral component interconnect express) device by the SSD, the custom debugging interface corresponds to a target configuration space of a custom area in the PCIe device, and the target configuration space is used for storing debugging data; sending a export command to the SSD through the custom debug interface; and receiving debugging information inside the SSD through the custom debugging interface.

6. The host of claim 5, wherein the processor is further configured to determine whether the PCIe device is identifiable upon determining that the SSD is malfunctioning; and if not, scanning to acquire the information of the PCIe equipment.

7. The method of claim 6, wherein the processor is specifically configured to:

when the host is a Linux host, acquiring information of the PCIe equipment according to a scanning command;

or,

and when the host is a Windows host, searching the information of the PCIe equipment in the equipment manager of the Windows host.

8. A solid state disk, comprising:

a processor, a memory, an input-output device, and a bus;

the processor, the memory and the input and output equipment are respectively connected with the bus;

the processor is configured to perform the steps of:

setting a custom debugging interface on a bus and interface standard PCIe device, wherein the custom debugging interface corresponds to a target configuration space of a custom area in the PCIe device, and the target configuration space is used for storing debugging data; receiving a debugging command sent by a host and a custom debugging interface address corresponding to the custom debugging interface through the custom debugging interface; collecting debugging information inside the SSD through an error correction module in the SSD; storing the debugging information in the target configuration space; receiving a lead-out command sent by a host through the custom debugging interface; and exporting the debugging information inside the SSD to the host through the custom debugging interface.

9. A computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of any one of claims 1 to 3.

10. A computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of claim 4.