# US 2017/0285951 A1 · Packed row representation for efficient network serialization with direct column indexing in a network switch

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2017/0285951 A1
- Document ID: US20170285951A1
- Status: Published application
- Kind: A1
- Application number: 15/274,276
- Filed: 2016-09-23
- Published: 2017-10-05
- Earliest claimed: 2016-04-01
- Assignees: Arista Networks, Inc.
- Applicants: Arista Networks, Inc.
- Inventors: Michael Greenwald; Stephen Schleimer; Daniel Greene
- Web page: https://patentgrep.com/patent/US20170285951A1

## CPC

- G06F 16/24534: {Query rewriting; Transformation}
- G06F 3/0604: {Improving or facilitating administration, e.g. storage management}
- G06F 3/0638: {Organizing or formatting or addressing of data}
- G06F 3/0659: {Command handling arrangements, e.g. command buffers, queues, command scheduling}
- G06F 3/067: {Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]}
- G06F 16/1734: {Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs}
- G06F 16/245: Query processing
- G06F 16/24568: {Data stream processing; Continuous queries}
- H04L 49/25: Routing or path finding in a switch fabric
- H04L 49/901: using storage descriptor, e.g. read or write pointers
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A method for operating a network element includes obtaining a write request that specifies a variable length data. The method includes identifying a row of a table based on the write request. The method includes processing the row to identify an empty portion of a variable length data storage portion of the row. The method includes determining an offset that that specifies the location of the empty portion. The method includes storing the offset and a length of the variable length data in a fixed length storage element of the fixed length data storage portion. The method includes storing the variable length data in the empty portion of the variable length data storage portion.

## Claims

### Claim 1

A network element, comprising:
a computer hardware processor;
a memory, accessible by the computer hardware processor, storing:
a database, and
a plurality of rows, wherein a row of the plurality of rows comprises:
a fixed length data storage portion, and
a variable length data storage portion;
wherein the database executes on the computer hardware processor and is programmed to:
obtain a write request that specifies a variable length data;
process the row to identify an empty portion of the variable length data storage portion;
determine an offset that specifies the location of the empty portion;
store the offset and a length of the variable length data in a fixed length storage element of the fixed length data storage portion; and
store the variable length data in the empty portion of the variable length data storage portion.

### Claim 2 (depends on 1)

The network element of claim 1, wherein the database is further programmed to:
generate an association between the fixed length storage element and the variable length data, wherein the association specifies that the variable length data is accessible using the fixed length storage element;
recording the association in a database planner.

### Claim 3 (depends on 1)

The network element of claim 1, wherein the database is further programmed to:
obtain a read request that specifies a second variable length data;
determine a second row that stores the second variable length data;
process the second row to obtain a second fixed length storage element that specifies a second offset and a length of the second variable length data;
read a portion of a variable length data storage portion of the second row using the second offset and the length of the second variable length data; and
provide the portion of the variable length data storage portion to a recipient based on the read request.

### Claim 4 (depends on 3)

The network element of claim 3, wherein the database determines the second row using an association stored in a database planner,
wherein the association specifies that the second variable length data is accessible using the second fixed length storage element.

### Claim 5 (depends on 1)

The network element of claim 1, wherein the memory comprises persistent storage.

### Claim 6 (depends on 1)

The network element of claim 1, wherein the memory comprises volatile storage.

### Claim 7 (depends on 1)

The network element of claim 1, wherein the database is further programmed to:
obtain a second write request that specifies a fixed length data;
process the row to identify a fixed length storage element that is empty; and
store the fixed length data in the fixed length storage element.

### Claim 8 (depends on 1)

The network element of claim 1, wherein the database is further programmed to:
obtain a read request that specifies a fixed length data;
determine a second row that stores the fixed length data;
process the second row to obtain a second fixed length storage element that stores the second fixed length data;
read contents of the second fixed length storage element;
provide the contents of the second fixed length storage element to a recipient based on the read request.

### Claim 9 (depends on 1)

The network element of claim 1, wherein the row further comprises:
a row definition that specifies a location that divides the row between the fixed length data storage portion and the variable length data storage portion.

### Claim 10 (depends on 9)

The network element of claim 9, wherein the location is specified by a second offset.

### Claim 11 (depends on 9)

The network element of claim 9, wherein the location is specified by a flag stored at the location.

### Claim 12 (depends on 1)

The network element of claim 1, wherein the network element is one selected from a group consisting of a switch, a multilevel switch, and a router.

### Claim 13

A non-transitory computer readable medium comprises instructions, which when executed by a process performs a method, the method comprising:
obtaining a write request that specifies a variable length data;
identifying a row of a table based on the write request;
processing the row to identify an empty portion of a variable length data storage portion of the row;
determining an offset that that specifies the location of the empty portion;
storing the offset and a length of the variable length data in a fixed length storage element of the fixed length data storage portion; and
storing the variable length data in the empty portion of the variable length data storage portion.

### Claim 14 (depends on 13)

The computer readable medium of claim 13, wherein the method further comprises:
obtaining a read request that specifies a second variable length data;
determining a second row that stores the second variable length data;
processing the second row to obtain a second fixed length storage element that specifies a second offset and a length of the second variable length data;
reading a portion of a variable length data storage portion of the second row using the second offset and the length of the second variable length data; and
providing the portion of the variable length data storage portion to a recipient based on the read request.

### Claim 15 (depends on 13)

The computer readable medium of claim 13, wherein the method further comprises:
obtaining a second write request that specifies a fixed length data;
processing the row to identify a fixed length storage element that is empty; and
storing the fixed length data in the fixed length storage element.

### Claim 16 (depends on 13)

The computer readable medium of claim 13, wherein the method further comprises:
obtaining a read request that specifies a fixed length data;
determining a second row that stores the fixed length data;
processing the second row to obtain a second fixed length storage element that stores the second fixed length data;
reading contents of the second fixed length storage element;
providing the contents to a recipient based on the read request.

### Claim 17

A method for operating a network element, the method comprising:
obtaining a write request that specifies a variable length data;
identifying a row of a table based on the write request;
processing the row to identify an empty portion of a variable length data storage portion of the row;
determining an offset that that specifies the location of the empty portion;
storing the offset and a length of the variable length data in a fixed length storage element of the fixed length data storage portion; and
storing the variable length data in the empty portion of the variable length data storage portion.

### Claim 18 (depends on 17)

The method of claim 17, wherein the method further comprises:
obtaining a read request that specifies a second variable length data;
determining a second row that stores the second variable length data;
processing the second row to obtain a second fixed length storage element that specifies a second offset and a length of the second variable length data;
reading a portion of a variable length data storage portion of the second row using the second offset and the length of the second variable length data; and
providing the portion of the variable length data storage portion to a recipient based on the read request.

### Claim 19 (depends on 17)

The method of claim 17, wherein the method further comprises:
obtaining a second write request that specifies a fixed length data;
processing the row to identify a fixed length storage element that is empty; and
storing the fixed length data in the fixed length storage element.

### Claim 20 (depends on 17)

The method of claim 17, wherein the method further comprises:
obtaining a read request that specifies a fixed length data;
determining a second row that stores the fixed length data;
processing the second row to obtain a second fixed length storage element that stores the second fixed length data;
reading contents of the second fixed length storage element;
providing the contents to a recipient based on the read request.
