# US 2003/0217185 A1 · Method and apparatus for reducing interrupts in a high-speed ethernet media access controller (MAC) by interrupt canceling

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

- Number: US 2003/0217185 A1
- Document ID: US20030217185A1
- Status: Published application
- Kind: A1
- Application number: 10/113,477
- Filed: 2002-03-29
- Published: 2003-11-20
- Earliest claimed: 2002-03-29
- Inventors: Anshuman Thakur; Frank C. Verhoorn III
- Web page: https://patentgrep.com/patent/US20030217185A1

## CPC

- G06F 9/4825: {Interrupt from clock, e.g. time of day}
- G06F 13/102: {where the program performs an interfacing function, e.g. device driver (G06F13/105 takes precedence; contention policies within device drivers G06F9/4881; scheduling within device drivers G06F9/52)}
- G06F 13/24: using interrupt (G06F13/32 takes precedence)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A system to accumulate routine and critical interrupt-triggering events, and generate an interrupt. A network communicates data. A computing device executes an operating system. A Network Interface Card (NIC) communicates data with the network and with the operating system, and invokes an interrupt. The NIC accumulates routine interrupt-triggering events and includes a timer to limit a length of time during which routine interrupt-triggering events accumulate, and if a critical interrupt-triggering event is received or the timer expires, the interrupt is invoked and the timer is reset. A driver provides an interface between the operating system and the NIC.

## Claims

### Claim 1

A system to accumulate routine and critical interrupt-triggering events, and invoke an interrupt, comprising:
a network to communicate data;
a computing device to execute an operating system;
a Network Interface Card (NIC) to communicate data with the network and with the operating system, and to invoke the interrupt, wherein the NIC accumulates the routine interrupt-triggering events and includes a timer to limit a length of time during which the routine interrupt-triggering events accumulate, and if one of the critical interrupt-triggering events is received or the timer expires, the interrupt is invoked and the timer is reset; and
a driver to provide an interface between the operating system and the NIC.

### Claim 2 (depends on 1)

The system of claim 1, wherein the driver sets an interrupt servicing routine to specify how the interrupt is processed.

### Claim 3 (depends on 1)

The system of claim 1, wherein the timer is initialized when a first routine interrupt-triggering event is received.

### Claim 4 (depends on 1)

The system of claim 1, wherein the timer is initialized when each routine interrupt-triggering event is received.

### Claim 5 (depends on 1)

The system of claim 1, wherein the network is a 1 Gigabit Ethernet network.

### Claim 6 (depends on 1)

The system of claim 1, wherein the network is a 10 Gigabit Ethernet network.

### Claim 7 (depends on 1)

The system of claim 1, wherein the NIC has an interrupt generation logic to specify the routine and critical interrupt-triggering events.

### Claim 8 (depends on 1)

The system of claim 1, wherein the operating system is Microsoft Windows or Linux.

### Claim 9 (depends on 1)

The system of claim 1, wherein the driver services the interrupt.

### Claim 10

A method to accumulate routine and critical interrupt-triggering events, and invoke an interrupt, comprising:
executing an operating system;
communicating data with a network and an operating system via a Network Interface Card (NIC);
accumulating the routine interrupt-triggering events; and
limiting a length of time of a timer during which the routine interrupt-triggering events accumulate, wherein when the timer expires or one of the critical interrupt-triggering events is received, the interrupt is invoked and the timer is reset.

### Claim 11 (depends on 10)

The method of claim 10, further including setting an interrupt servicing routine to specify how the interrupt is processed.

### Claim 12 (depends on 10)

The method of claim 10, further including initializing the timer when a first routine interrupt-triggering event is received.

### Claim 13 (depends on 10)

The method of claim 10, further including initializing the timer when each routine interrupt-triggering event is received.

### Claim 14 (depends on 10)

The method of claim 10, wherein the network is a 1 Gigabit Ethernet network.

### Claim 15 (depends on 10)

The method of claim 10, wherein the network is a 10 Gigabit Ethernet network.

### Claim 16 (depends on 10)

The method of claim 10, further including utilizing interrupt generation logic to specify the routine and critical interrupt-triggering events.

### Claim 17 (depends on 10)

The method of claim 10, wherein the operating system is Microsoft Windows or Linux.

### Claim 18 (depends on 10)

The method of claim 10, further including servicing the interrupt.

### Claim 19

A machine code storage device, comprising:
a machine-readable medium; and
machine-readable code, stored on the computer-readable medium, having instructions to execute an operating system;
communicate data with a network and with the operating system via a Network Interface Card (NIC); and
accumulate the routine interrupt-triggering events; and
limit a length of time of a timer during which the routine interrupt-triggering events accumulate and when the timer expires or a critical interrupt-triggering event is received, the interrupt is invoked and the timer is reset.

### Claim 20 (depends on 19)

The machine code storage device of claim 19, wherein the machine-readable code further includes instructions to set an interrupt servicing routine to specify how the interrupt is processed.

### Claim 21 (depends on 19)

The machine code storage device of claim 19, wherein the machine-readable code further includes instructions to initialize the timer when a first routine interrupt-triggering event is received.

### Claim 22 (depends on 19)

The machine code storage device of claim 19, wherein the machine-readable code further includes instructions to initialize the timer when each routine interrupt-triggering event is received.

### Claim 23 (depends on 19)

The machine code storage device of claim 19, wherein the machine-readable code further includes instructions to utilize interrupt generation logic to specify the routine and critical interrupt-triggering events.

### Claim 24 (depends on 19)

The machine code storage device of claim 19, wherein the operating system in Microsoft Windows.

### Claim 25

A Network Interface Card (NIC) to accumulate routine and critical interrupt-triggering events, and generate an interrupt, comprising:
interrupt generation logic to specify the routine and critical interrupt-triggering events;
an accumulation device to accumulate the routine interrupt-triggering events;
a timer to limit a length of time during which routine interrupt-triggering events accumulate; and
an invocation device to invoke the interrupt when (a) the timer expires or (b) a critical interrupt-triggering event is received, and reset the timer.

### Claim 26 (depends on 25)

The NIC of claim 25, further including an interrupt servicing routine to specify how the interrupts are processed.

### Claim 27 (depends on 25)

The NIC of claim 25, wherein the timer is initialized when a first routine interrupt-triggering event is received.

### Claim 28 (depends on 25)

The NIC of claim 25, wherein the timer is initialized when a each routine interrupt-triggering event is received.

### Claim 29 (depends on 25)

The NIC of claim 25, further including an interrupt generation logic to specify the routine and critical interrupt-triggering events.
