Data Parking for SSDs with Zones

A storage device, comprising:

• a non-volatile storage unit, wherein a capacity of the non-volatile storage unit is divided into a plurality of zones, and wherein the non-volatile storage unit comprises a plurality of dies, each of the plurality of dies comprising a plurality of erase blocks, and wherein the non-volatile storage unit comprises one or more dedicated data parking sections;
• a first volatile memory unit;
• and
• a controller coupled to the first volatile memory unit and the non-volatile storage unit, the controller comprising a second volatile memory unit, wherein the controller is configured to:
• receive a first write command corresponding to a first zone within a plurality of zones;
• generate XOR or parity data associated with the first zone, the XOR or parity data corresponding to the first write command;
• copy the XOR or parity data to a first location in the one or more dedicated data parking sections;
• and
• copy the XOR or parity data to a first location in the second volatile memory unit.

A storage device, comprising:

• a non-volatile storage unit, wherein a capacity of the non-volatile storage unit is divided into a plurality of zones, wherein the non-volatile storage unit comprises a plurality of dies, each of the plurality of dies comprising a plurality of erase blocks, and wherein the non-volatile storage unit comprises one or more dedicated data parking sections;
• a first volatile memory unit;
• and
• a controller coupled to the non-volatile storage unit and the first volatile memory unit, wherein the controller is configured to:
• receive one or more write commands associated with one or more zones of the plurality of zones;
• generate XOR or parity data associated with the one or more zones for each of the one or more write commands in the first volatile memory unit;
• copy the XOR or parity data associated with the one or more zones from the first volatile memory unit to the one or more dedicated data parking sections sequentially;
• copy previously generated XOR or parity data associated with the one or more zones from the one or more dedicated data parking sections to the first volatile memory unit when one or more additional write commands are received to write data to the one or more zones;
• update the previously generated XOR or parity data for each of the one or more additional write commands in the first volatile memory unit;
• and
• copy the updated previously generated XOR or parity data for each of the one or more additional write commands to the one or more dedicated data parking sections sequentially.