Latency on indirect admin commands
A data storage device includes a memory device and a controller coupled to the memory device. The controller is configured to receive a parent physical function (PF), receive one or more child PFs, determine whether any part of a first child command of a first child PF of the one or more child PFs can be executed prior to receiving approval from the parent PF, and start executing the first child command. The controller is further configured to initialize an indirect queue, set fetching pointers of the indirect queue to the first child command, mimic a doorbell for the first child command, fetch the first child command, determine whether the first child command has started execution by a child PF flow, and complete the first child command.
1. A data storage device, comprising:
a memory device; and
a controller coupled to the memory device, wherein the controller is configured to:
receive a parent physical function (PF);
receive one or more child PFs;
fetch a first child command of a first child PF of the one or more child PFs from a child submission queue;
mark a command arrival time for the first child command;
place the first child command in a command pool;
determine whether any part of the first child command of the first child PF of the one or more child PFs can be executed prior to receiving approval from the parent PF; and
start executing the first child command.
2. The data storage device of claim 1 , wherein the controller is further configured to determine whether the first child command has been executed by a parent PF command.
3. The data storage device of claim 1 , wherein the controller is further configured to pull the first child command out of the command pool.
4. The data storage device of claim 1 , wherein the controller is further configured to receive an approval to execute the first child command after starting to execute the first child command.
5. The data storage device of claim 1 , wherein the controller is further configured to complete execution of the first child command prior to receiving approval to execute the first child command.
6. The data storage device of claim 5 , wherein the controller is further configured to withhold sending a completion message to a host regarding the first child command until after receiving the approval to execute the first child command.
7. A data storage device, comprising:
a memory device; and
a controller coupled to the memory device, wherein the controller is configured to:
receive a parent physical function (PF);
receive one or more child PFs;
determine whether the first child command has been executed by a parent PF flow;
determine whether any part of a first child command of a first child PF of the one or more child PFs can be executed prior to receiving approval from the parent PF; and
start executing the first child command.
8. The data storage device of claim 7 , wherein the controller is further configured to determine whether the first child command has been approved after determining that the first child command has been executed by the parent PF flow.
9. A data storage device, comprising:
a memory device; and
a controller coupled to the memory device, wherein the controller is configured to:
receive a parent physical function (PF);
receive one or more child PFs;
determine whether a first child command of a first child PF of the one or more child PFs is approved by the parent PF, wherein the first child command is fetched from a child submission queue;
initialize an indirect queue, wherein the initialized indirect queue comprises:
the first child command and first child command pointers, wherein:
the first child command pointers point to the child submission queue; and
the child submission queue comprises the first child command; and
second command pointers, wherein the second command pointers point to a different location than the first child command pointers;
set fetching pointers of the indirect queue to the first child command;
mimic a doorbell for the first child command;
fetch the first child command;
determine whether the first child command has started execution by a child PF flow; and
complete the first child command.
10. The data storage device of claim 9 , wherein the controller is further configured to determine that the first child command has already started execution by the child PF flow.
11. The data storage device of claim 10 , wherein the controller is further configured to continue to execute the first child command.
12. The data storage device of claim 9 , wherein the first child command is fetched from a child submission queue.
13. The data storage device of claim 9 , wherein the controller is further configured to begin executing the first child command prior to the approval.
14. The data storage device of claim 9 , wherein the controller is further configured to fetch the first child command twice.
15. A data storage device, comprising:
memory means; and
a controller coupled to the memory means, wherein the controller is configured to:
receive a parent physical function (PF);
receive one or more child PFs;
mark a time of arrival of the first child command and place the first child command into a command pool; and
begin processing a first child command associated with a first child PF of the one or more child PFs, wherein the processing occurs prior to receiving approval from a first parent command of the parent PF.
16. The data storage device of claim 15 , wherein the controller is further configured to determine whether the first child command has started processing, wherein the determining occurs after the approval.
17. The data storage device of claim 15 , wherein the controller is configured to initialize an indirect queue, wherein the indirect queue comprises the first child command a pointers to child submission queue that also comprises the first child command.