Jeffrey L Munsil

20110087890, Apr 14, 2011

Apr 27, 2010

12/768058

Jeffrey L. Munsil - Fort Collins CO, US
Jeffrey L. Williams - Rochester MN, US

H04L 9/32
G06F 21/00

713184

Described embodiments provide for authenticating a user request for access to at least a portion of an encrypted storage device. First, the request for access to at least a portion of the encrypted storage device is received. The request includes a plaintext password. A hash module generates a hashed version of the received plaintext password based on an authentication hash key. A hashed value of the generated plaintext password is retrieved from a key storage. A hash comparator compares the hashed version of the received plaintext password with the retrieved hashed value of the generated plaintext password. If the hashed version of the received plaintext password and the retrieved hashed value of the generated plaintext password are equal, the user is authenticated for access to at least a portion of the encrypted storage device. Otherwise, the user is denied access to the encrypted storage device.

20190095341, Mar 28, 2019

Nov 27, 2018

16/201733

- Cupertino CA, US
Jeffrey Munsil - Fort Collins CO, US
Jackson Ellis - Fort Collins CO, US
Mark Ish - Sandy Springs GA, US

G06F 12/1009
G06F 3/06
G06F 12/02

Method and apparatus for managing data in a memory, such as a flash memory. A memory module has a non-volatile memory (NVM) and a memory module electronics (MME) circuit configured to program data to and read data from solid-state non-volatile memory cells of the NVM. A map structure associates logical addresses of user data blocks with physical addresses in the NVM at which the user data blocks are stored. A controller circuit arranges the user data blocks into map units (MUs), and directs the MME circuit to write the MUs to a selected page of the NVM. The controller circuit updates the map structure to list only a single occurrence of a physical address for all of the MUs written to the selected page. The map structure is further updated to list an MU offset and an MU length for each of the MUs written to the selected page.

20190050417, Feb 14, 2019

Aug 8, 2017

15/671469

- Cupertino CA, US
Jeffrey Munsil - Fort Collins CO, US
Carl Forhan - Rochester MN, US

G06F 17/30
G06F 3/06
G06F 21/78
G06F 21/62

A method includes compressing input data to form compressed data and comparing a size of the compressed data to a maximum allowed size determined from a fixed sector size for a lower tier of the multi-tier storage system and a minimum pad length for a pad that is stored in the same sector as the compressed data when the compressed data is migrated to the lower tier. When the size of the compressed data is greater than the maximum allowed size, the input data is stored instead of the compressed data in an upper tier of the multi-tier storage system.

20180349035, Dec 6, 2018

May 30, 2017

15/608203

- Cupertino CA, US
Jeffrey Munsil - Fort Collins CO, US
Timothy Canepa - Los Gatos CA, US
Stephen Hanna - Fort Collins CO, US

G06F 3/06

A data storage device with one or more buffers can employ buffer tenure management with at least a data storage device having a first buffer, a second buffer, a buffer manager, and a non-volatile memory. The first buffer can be located on-chip while the second buffer is located off-chip. The first buffer may be filled with data having a tenure of less than a predetermined tenure threshold as directed by the buffer manager.

20180349036, Dec 6, 2018

Jun 1, 2017

15/610806

- Cupertino CA, US
Jeffrey Munsil - Fort Collins CO, US

G06F 3/06
G06F 12/10

A data storage device can be configured with a data map that has one or more custom map attributes. A non-volatile memory of the data storage device may store data organized into a data map by a mapping module. The data map consisting of at least a data address translation and a custom attribute pertaining to an operational parameter of the data map with the custom attribute generated and maintained by the mapping module.

20180349285, Dec 6, 2018

May 31, 2017

15/609758

- Cupertino CA, US
Steven S. Williams - Longmont CO, US
Jeffrey Munsil - Fort Collins CO, US

G06F 12/10

Apparatus and method for managing namespaces in a Non-Volatile Memory Express (NVMe) controller environment. A non-volatile memory (NVM) is arranged to store map units (MUs) as addressable data blocks in one or more namespaces. A forward map has a sequence of map unit address (MUA) entries that correlate each of the MUs with the physical locations in the NVM. The MUA entries are grouped into immediately adjacent, contiguous ranges for each of the namespaces. A base MUA array identifies the address, within the forward map, of the beginning MUA entry for each namespace. A new namespace may be added by appending a new range of the MUA entries to the forward map immediate following the last MUA entry, and by adding a new entry to the base MUA array to identify the address, within the forward map, of the beginning MUA entry for the new namespace.

20180341594, Nov 29, 2018

May 26, 2017

15/606502

- Cupertino CA, US
Jeffrey Munsil - Fort Collins CO, US
Jackson Ellis - Fort Collins CO, US
Mark Ish - Sandy Springs GA, US

G06F 12/1009
G06F 3/06

Method and apparatus for managing data in a memory, such as a flash memory. A memory module has a non-volatile memory (NVM) and a memory module electronics (MME) circuit configured to program data to and read data from solid-state non-volatile memory cells of the NVM. A map structure associates logical addresses of user data blocks with physical addresses in the NVM at which the user data blocks are stored. A controller circuit arranges the user data blocks into map units (MUs), and directs the MME circuit to write the MUs to a selected page of the NVM. The controller circuit updates the map structure to list only a single occurrence of a physical address for all of the MUs written to the selected page. The map structure is further updated to list an MU offset and an MU length for each of the MUs written to the selected page.