Storage device that writes data from a host during garbage collection

1. A storage device that is configured to perform read and write operations based on read and write commands output from a host, comprising:

a controller;

a buffer that comprises a volatile memory; and

a nonvolatile memory including a plurality of blocks, wherein each of the blocks includes a plurality of pages, wherein:

the controller is configured to:

associate one or more blocks of the nonvolatile memory with a first namespace such that data associated with the first namespace are selectively stored therein;

associate other one or more blocks of the nonvolatile memory with a second namespace such that data associated with the second namespace are selectively stored therein;

carry out garbage collection by reading data from one or more pages of a target block of the garbage collection and selectively copying valid data included in the read data to another block,

determine during the garbage collection an amount of invalid data included in the read data, and

receive, in the buffer during the garbage collection, first write data from the host up to a first size which depends on the determined amount of invalid data;

wherein the garbage collection and the determining of the amount are carried out independently with respect to each of the first and second namespaces, and

wherein third write data associated with the first namespace and fourth write data associated with the second namespace are received in the buffer up to a maximum amount which is determined based on a sum of the determined amount for the first namespace and the determined amount for the second namespace.

2. The storage device according to claim 1 , wherein

the controller is further configured to decrease the sum of the determined amounts by an amount of the first write data received in the buffer, during the garbage collection.

3. The storage device according to claim 1 , wherein

the controller reads the data from the target block of the garbage collection until the valid data included in the read data amount to a size of one page, and then receive the first write data from the host up to the sum of the determined amounts.

4. The storage device according to claim 1 , wherein

the controller is further configured to count a number of non-written portions in a block in which second write data in the buffer is to be written, and accept, in the buffer, the second write data from the host, up to an amount corresponding to the counted number of non-written portions, while the garbage collection is not carried out.

5. The storage device according to claim 1 , wherein

the controller is further configured to start the garbage collection upon determining that a number of free blocks in which no valid data are stored is less than a threshold.

6. The storage device according to claim 1 , wherein

the controller is further configured to map the target block for the garbage collection as a free block in which no valid data are stored after the valid data in all pages of the target block are copied.

7. The storage device according to claim 1 , wherein

the garbage collection, the determining of the amount, and the receiving of the first write data from the host are carried out independently with respect to each of the first and second namespaces.

8. A method of operating a storage device including a buffer that comprises a volatile memory, and a nonvolatile memory including a plurality of blocks, the storage device configured to perform read and write operations based on read and write commands output from a host, wherein each of the blocks includes a plurality of pages, the method comprising:

associating one or more blocks of the nonvolatile memory with a first namespace such that data associated with the first namespace are selectively stored therein;

associating other one or more blocks of the nonvolatile memory with a second namespace such that data associated with the second namespace are selectively stored therein;

carrying out garbage collection by reading data from one or more pages of a target block of the garbage collection and selectively copying valid data included in the read data to another block;

determining during the garbage collection an amount of invalid data included in the read data; and

receiving, in the buffer during the garbage collection, first write data from the host up to a first size which depends on the determined amount of invalid data,

wherein the garbage collection and the determining of the amount are carried out independently with respect to each of the first and second namespaces, and

wherein third write data associated with the first namespace and fourth write data associated with the second namespace are received in the buffer, up to a maximum amount which is determined based on a sum of the determined amount for the first namespace and the determined amount for the second namespace.

9. The method according to claim 8 , further comprising:

decreasing the sum of the determined amounts by an amount of the first write data received in the buffer, during the garbage collection.

10. The method according to claim 8 , wherein

the data are read from the target block of the garbage collection until the valid data included in the read data amount to a size of one page, and then the first write data from the host up to the sum of the determined amounts are received in the buffer.

11. The method according to claim 8 , further comprising:

during a write operation during which the garbage collection is not carried out, counting a number of non-written portions in a block in which second write data in the buffer is to be written, and receiving, in the buffer, the second write data from the host, up to an amount corresponding to the counted number of non-written portions.

12. The method according to claim 8 , wherein

the garbage collection is started upon determining that a number of free blocks in which no valid data are stored is less than a threshold.

13. The method according to claim 8 , further comprising:

mapping the target block for the garbage collection as a free block in which no valid data are stored after the valid data in all pages of the target block are copied.

14. The method according to claim 8 ,

wherein

the garbage collection, the determining of the amount, and the receiving of the first write data from the host are carried out independently with respect to each of the first and second namespaces.