Danny H Lam, 73Mira Loma, CA

6754773, Jun 22, 2004

Jan 29, 2002

10/060878

Thomas R. Ulrich - Rancho Santa Margarita CA
James R. Schweitzer - Huntington Beach CA
Gregory D. Bolstad - Tustin CA
Jay G. Randall - Newport Beach CA
John R. Staub - Newport Beach CA
George W. Priester - Westminster CA
David H. Barry - Placentia CA
Leonard D. Olsen - Anaheim CA
Danny Lam - Garden Grove CA

Snap Appliance, Inc. - Irvine CA

G06F 1300

711118, 709203, 709201, 709219, 711111

A programmable data path accelerator is described. The programmable data path accelerator operates on a file server that includes a network interface for communicating with one or more clients. The network interface includes a network transaction queue. A metafile processor is configured to communicate with the network interface across a first memory-mapped bus and is configured to communicate with the storage interface across a second memory-mapped bus. A data engine configured to communicate with the network interface across the first memory-mapped bus and to communicate with the storage interface across the second memory-mapped bus.

2002016, Oct 31, 2002

Jan 29, 2002

10/060956

Thomas Ulrich - Rancho Santa Margarita CA, US
James Schweitzer - Huntington Beach CA, US
Gregory Bolstad - Tustin CA, US
Jay Randall - Newport Beach CA, US
John Staub - Newport Beach CA, US
Wilbur Priester - Westminster CA, US
David Barry - Placentia CA, US
Leonard Olsen - Anaheim CA, US
Danny Lam - Garden Grove CA, US
Ronald Godshalk - Placentia CA, US

G06F015/16
G06F015/167

709/213000, 709/219000, 707/010000

A data path controller architecture is disclosed. The architecture includes a network interface for communicating with one or more clients, a storage interface for communicating with one or more disk drives. A data engine configured to communicate with the storage interface to receive file data from the one or more disk drives. The data engine communicates with the network interface to send file data to the one or more clients. A CPU is configured to queue transaction requests for the data engine in response to file requests from the clients. The data engine receives file data in response to at least a portion of the transaction requests. The data engine sends file data to the one or more clients in response to the transaction requests.

2002016, Nov 7, 2002

Jan 29, 2002

10/060911

Thomas Ulrich - Rancho Santa Margarita CA, US
James Schweitzer - Huntington Beach CA, US
Gregory Bolstad - Tustin CA, US
Jay Randall - Newport Beach CA, US
John Staub - Newport Beach CA, US
Wilbur Priester - Westminster CA, US
David Barry - Placentia CA, US
Leonard Olsen - Anaheim CA, US
Danny Lam - Garden Grove CA, US
Ronald Godshalk - Placentia CA, US

G06F015/16
G06F017/30
G06F007/00
G06F012/00

709/219000, 707/010000, 707/202000, 714/005000

A data path accelerator with variable parity, variable length, and variable extent groups is described. The data path accelerator includes a network interface for communicating with one or more clients and a storage interface for communicating with one or more disk drives. A metafile processor is configured to queue network transaction requests to the network interface and to queue storage transaction requests to the storage interface. The metafile processor is further configured to manage file system metafile information. The file system metafile information includes disk locations of one or more distributed parity groups on the one or more disk drives. Each distributed parity group includes one or more data blocks and a parity block. The file system metafile information further includes information regarding a length of each distributed parity group. A data engine is configured to communicate with the storage interface to receive data from or to write data to the one or more disk drives in satisfaction of the storage transaction requests. The data engine is further configured to communicate with the network interface to receive data from or to write data to the one or more clients in satisfaction of the network transaction requests. The data engine includes at least one data cache and one or more parity engines to perform parity calculations for cached distributed parity groups.