A method and system for DMA transfer of data in scatter/gather mode. A table of buffer descriptors may be used to determine the next buffer to be used when a current buffer storing data that has been transferred or will be transferred and may be used in automatic buffer switching, which does not require processor intervention. Entries in the table of buffer descriptors are entered programmatically. The method and system also provide for hardware writing to table of packet descriptors which describes location and size of incoming data and can indicate whether a packet of data straddles two or more buffers, thus decoupling packet sizes from buffer sizes.
|
1. A method of transferring data between a processor and an attached direct memory access (“DMA”) device in scatter/gather mode comprising:
a) transferring a packet of data from the DMA device to the processor;
b) detecting an end-of-packet condition; and
c) writing out a packet descriptor to a table in memory, wherein the packet descriptor includes a packet start address, a packet size, and a bit indicating whether the packet is split across a buffer boundary.
7. The method of
8. The method of
9. The method of
|
This application claims the benefit of provisional U.S. patent application entitled “Digital Signal Coprocessor,” application No. 60/492,060, filed on Jul. 31, 2003.
This invention relates to the transfer of data between a processor and an attached device, particularly DMA transfer of data.
Processors whose computer bus architectures have Direct Memory Access (“DMA”) capability may transfer data between a device attached to the processor (such as disk controllers, graphics cards, etc.) and the processor's system memory independent of the main CPU. DMA allows devices of different speeds to communicate without placing a processing burden on the CPU. DMA further speeds up data transfer by eliminating the fetch and execute cycles required when data transfers pass through the CPU.
In a DMA transfer, the CPU stops its bus activity to allow the DMA operation. A DMA controller then reads or writes memory bytes and transfers the data to the desired location; generally, a DMA transfer involves either a device read and memory write or a memory read and a device write. FIFO buffers may be used to store the data to be transferred.
It would be advantageous to enhance DMA transfer of data.
This need has been met with a method and system for DMA transfer of data in “scatter/gather” mode. In one embodiment, a table of buffer descriptors may be used to determine the next buffer to be used when a current buffer storing data that has been transferred or will be transferred and may be used in automatic buffer switching, which does not require processor intervention. The method and system also provide for a table of packet descriptors which describes location and size of incoming data and can indicate whether a packet of data straddles two or more buffers, thus decoupling packet sizes from buffer sizes. The method and system also provide for optional end-of-buffer and end-of-packet notifications to the controlling processor as well as optional termination by hardware, without software intervention, on an end-of-buffer condition.
In one embodiment, a method of transferring data between a processor and an attached direct memory access (“DMA”) device in scatter/gather mode comprises maintaining a table of buffer descriptors for determining a start address and size of a next buffer to be used when transferring data when a current buffer counter reaches zero, wherein entries in the table are linked programmatically; transferring data between a current buffer and the device via DMA; automatically switching buffers when the selected buffer counter reaches zero, wherein a next buffer descriptor table entry is read from memory and a new buffer pointer and size is updated based on the table entry; and transferring data between the next buffer and the device via DMA.
In another embodiment, a processor for transferring data between the processor and an attached direct memory access (“DMA”) device in scatter/gather mode comprises means for connecting the processor to the DMA device; a plurality of buffers for storing data transferred between the DMA device and the processor, each of the plurality of buffers having a buffer counter; a buffer descriptor table for each Data In FIFO and each Data Out FIFO of a DMA channel transferring data between the DMA device and the processor, each entry in the buffer descriptor table having a buffer address of one of the plurality of buffers, a buffer size of one of the plurality of buffers, and sequencing information for calculating a start address and size of a next buffer to be used for storing data transferred between the DMA device and the processor when a current buffer counter reaches zero, wherein entries in the buffer descriptor table are made programmatically; and a bus interface unit for transferring data between the DMA device and the processor, the bus interface unit including hardware for automatically fetching the calculated start address and size of the next buffer to be used to store data transferred between the DMA device and the processor from the buffer descriptor table so the bus interface unit can automatically switch buffers for storing data transferred between the DMA device and the processor when the current buffer counter reaches zero.
In another embodiment, a method of transferring data between a processor and an attached direct memory access (“DMA”) device in scatter/gather mode comprises transferring a packet of data from the DMA device to the processor; detecting an end-of-packet condition; and writing out a packet descriptor to a table in memory, wherein the packet descriptor includes a packet start address, a packet size, and a bit indicating whether the packet is split across a buffer boundary.
In another embodiment, a processor for transferring data between the processor and an attached direct memory access (“DMA”) device in scatter/gather mode comprises the means for connecting the processor to the DMA device; a plurality of buffers for storing data transferred between the DMA device and the processor; and a bus interface unit for transferring data between the DMA device and the processor, the bus interface unit including hardware for detecting an end-of-packet event and writing a packet descriptor to a packet descriptor table for each Data In FIFO of a DMA channel, each packet descriptor having a packet start address, a packet size, and a bit indicating whether the packet is split across a buffer boundary, wherein packet descriptors are written to the packet descriptor table each time an end-of-packet event is detected.
In
In one embodiment, the BIU can support up to 4 DMA channels, or DMA devices. (Other embodiments of the invention may support a different number of DMA channels.) Each DMA channel interfaces to one or more pin groups which functionally implements one I/O device. The BIU provides FIFO data buffering for up to 4 DMA devices, each of which has four FIFOs (Data In, Data Out, Command, and Status) in the BIU. The BIU assembles commands and outgoing data from the local data bus and places the data in the BIU's Data Out FIFO for transport to the DMA device's pin group FIFOs and assembles commands and incoming data from the device's pin group FIFOs and places the incoming data in the BIU's Data In FIFO for transport to the local data bus to be stored in memory. Transport of commands, status, and data between the BIU FIFOs and memory/processors is done either programmatically by the MTE (in non-scatter/gather and non-DMA configurations) or automatically by the BIU DMA engine. The BIU provides FIFO data assembly and buffering on demand, as requested by the MTE and/or the pin groups of the DMA device, and optionally also FIFO data transportation to and from chip memory.
With reference to
Each DMA device has 32 addressable registers which are mapped to the I/O quad address space. (In other embodiments, another number of registers may be employed). The format of the DMA register addresses for DMA registers 0-31 96 and DMA registers 32-63 98 are shown in
TABLE 1
Reg
R/W
Function
Name
Notes
0
RW
BIU
DMA Data FIFO
Read = Data in, Write = Data
out (1 byte)
1
Reserved
2
RW
BIU
DMA Data FIFO
Read = Data in, Write = Data
out (2 bytes)
3
Reserved
4
RW
BIU
DMA Data FIFO
Read = Data in, Write = Data
out (4 bytes)
5
Reserved
6
RW
BIU
DMA Data FIFO
Read = Data in, Write = Data
out (8 bytes)
7
Reserved
8
RW
BIU
DMA Command/Status
Read = Status, Write = Command
(1, 2, 4, or 8
bytes)
9
RW
BIU
Data In FIFO
For scatter/gather;
Packet
updated in place
Descriptor Table Pointer
10
RW
BIU
Data Out FIFO
For scatter/gather;
Buffer
updated in place
Descriptor Table
Pointer
11
RW
BIU
Data In FIFO
For scatter/gather;
Buffer
updated in place
Descriptor Table
Pointer
12
RW
BIU
Data Out FIFO
Parameters
13
RW
BIU
Data in FIFO
Parameters
14
RW
BIU
Command FIFO
Parameters
15
RW
BIU
Status FIFO
Parameters
16
WO
BIU
BIU FIFO Control
Enable, reset for Data
In, Data Out, Command,
Status FIFOs
17
RO
BIU
DMA Data In Byte
Enables
18:19
RW
DMA
DMA Address
18 = Address register,
Register
19 = 2nd word for 64
bit address
20:21
RW
DMA
DMA DC 0
Data Constant 0
22:23
RW
DMA
DMA DC 1
Data Constant 1
24
RW
BIU
Data Out FIFO
For interrupt, DMA,
DMA Address
scatter/gather;
updated in place
25
RW
BIU
Data Out FIFO
For scatter/gather;
Buffer; End
Interrupt
Address
26
RW
BIU
Data In FIFO DMA
For interrupt, DMA,
Address
scatter/gather;
updated in place
27
RW
BIU
Data In FIFO
For scatter/gather;
Buffer-End
Interrupt
Address
28:29
RW
BIU
Command FIFO
Command FIFO Addresses
Address
for Interrupt of DMA,
error
30:31
RW
BIU
Status FIFO
Status FIFO Addresses
Address
for Interrupt or DMA,
error
32
RW
BIU
Data In FIFO
For scatter/gather;
Packet
Descriptor Table
Tail
33
RC
BIU
Data In FIFO
For scatter/gather;
Packet
Descriptor
Status
34
RW
BIU
Data In FIFO
For scatter/gather;
Packet-End
interrupt
address
The BIU translates I/O register addresses between the local data bus and the I/O bus. This mapping of DMA register addresses as seen by the pin group is shown in Table 2 below. An “X” in the BIU column indicates these registers are in the BIU, not the pin groups. When the control, status, and data FIFOs are accessed from the local data bus, the FIFOs in the BIU are communicated with. The BIU communicates with the pin group FIFOs using some of these same addresses on the I/O bus; specifically, it uses DMA register addresses 0, 2, 4, and 6 as the address of the data FIFOs and register address 8 for the control/status FIFOs.
TABLE 2
Type
Reg
R/W
BIU
Function
Notes
DMA
0
RW
X
DMA Data FIFO
Read = Data in,
Write = Data out(1
byte)
DMA
1
Reserved
unused
DMA
2
RW
X
DMA Data FIFO
Read = Data in,
Write = Data out(2
bytes)
DMA
3
Reserved
DMA
4
RW
X
DMA Data FIFO
Read = Data in,
Write = Data out
(4 bytes)
DMA
5
Reserved
Unused
DMA
6
RW
X
DMA Data FIFO
Read = Data in,
Write = Data out
(8 bytes)
DMA
7
reserved
unused
DMA
8
RW
DMA Control/
Read = Status,
Status FIFO
Write = Cmd (1, 2,
or 4 bytes)
DMA
9:11
X
Scatter/Gather
Registers
DMA
12:15
X
FIFO Parameters
In the BIU only
DMA
16
BIU/Pin Group
Controls both BIU
FIFO Control
and pin group
FIFOs
DMA
17
reserved
DMA
18:19
RW
Address Register
18 = Addrs reg. 19 = 2nd
word for 64 bit
DMA
20:21
RW
DMA DC 0
20 = DC reg. 21 = 2nd
word for 64 bit
DMA
22:23
RW
DMA DC 1
22 = DC reg. 23 = 2nd
word for 64 bit
DMA
24:34
X
FIFO and
In the BIU only
scatter/gather
In
To transfer data, FIFOs in each DMA device submit a request, in the form of a DMA service code, via the DMA request logic to the DMA request line in the BIU. (The Data In and Status FIFOs generate requests when they have data for the BIU; the Data Out and Command FIFOs generate requests when they have space available for data from the BIU.) The DMA service code includes the DMA device code and two bits indicating which FIFO is requesting service; the code is decoded by the BIU and selects the appropriate DMA device and read/write transfer type. The requesting device receives service in the form of a bus transfer at its DMA address as long as no quad bus access is pending. Depending on the DMA service code, the bus transfer supplies or accepts data from the DMA device FIFO.
As noted above, the BIU contains four merge FIFOs for each DMA device. Input data and status information sent from the pin groups is aggregated and placed in the BIU FIFOs while output data and commands from the BIU FIFOs is split up and sent to the respective pin groups. In one embodiment, there are sixteen FIFOs implemented in a single dual port RAM. Each FIFO is 8 octets of 8 bytes per octet deep, a total of 128 octets (1 KB) of dual port RAM. (In other embodiments, different numbers of FIFOs and different amounts of RAM may be employed.)
The BIU can operate in one of three different event-driven modes: interrupt mode, DMA mode, and scatter/gather mode, which is an enhanced DMA mode. (In other embodiments of the invention, the BIU may operate in fewer or more modes than described here.) In interrupt mode the BIU issues an interrupt by writing a word to the interrupt address of the FIFO register when a block is ready for transfer to or from the data bus. The command and status FIFOs generally operate in interrupt mode. In automatic DMA mode, the BIU automatically transfers data to or from memory to or from the location defined by the BIU FIFO transfer address when a block is ready for transfer. Scatter/gather mode employs automatic buffer switching during DMA transfer of data. The mode in which the BIU operates is determined by a DMA FIFO parameters register. An example of the BIU FIFO parameters register format used in one embodiment is shown below in Table 3 (in other embodiments, other formats may be used).
TABLE 3
Bits
No
Type
Function
Comments
31
1
RW
Error Interrupt Enable
30
1
RW
Interrupt/DMA Enable
29:28
2
RW
DMA device width: 1/2/4
Bytes per transfer
bytes
to/from I/O bus
27:25
3
RW
Big Endian (BE) code
For endian swap on
transfer
24:23
2
RW
Byte position = LSB
Byte rotate by 0–3
position on I/O bus
bytes
22:21
2
reserved
20
1
RW
Count Mode:
0 = absolute,
1 = differential
19
1
RW
Mode: 1 = DMA,
DMA = automatic DMA
0 = Interrupt
to memory
18
1
RO
Read End
Read End byte has
left BIU FIFO
17
1
RW
Increment Address per
Increment address
transfer
on DMA xfer
16
1
RW
64 Bit
64-bit DMA device -
data FIFOs only
15:14
2
RW
Block size/Watermark
1/2/4 or 0/2/4/6
octets
13:7
7
RO
I/O bus Counter/
Function depends on
reserved
bit 20
6:0
7
RO
D Bus Counter/FIFO
Function depends on
count
bit 20
Scatter/gather is an advanced method of operating a BIU channel in DMA mode. It is available for Data In and Data Out FIFOs, not command and status FIFOs.
The BIU uses a table of buffer descriptors in scatter/gather mode for each Data In and Data Out FIFO. A table of packet descriptors for each Data In FIFO (i.e., each incoming scatter/gather DMA channel) is optionally created, for instance, for use with packet-based I/O interfaces. These tables may be located anywhere; in one embodiment, they are located in the I/O Quad data memory. Each table contains a sequence of entries; in one embodiment, the table of buffer descriptors is up to 128 entries long and the table of packet descriptors can have anywhere from 32 to 256 entries. Each entry in the buffer descriptor table consists of a buffer address, a buffer size, and sequencing information for calculating the next table entry's location. The entries in the buffer descriptor table are linked in a programmable (i.e., not necessarily sequential or circular) order. The non-linear link sequence of entries in the table can be changed dynamically, allowing reordering of IO data with minimal memory reads/writes, since changing address bits changes the order in which buffers are used. Each entry in the packet descriptor table consists of a packet start address, a packet size, and a bit indicating whether the packet is split across a buffer boundary, decoupling packet sizes from buffer sizes.
In scatter/gather mode, the BIU hardware performs DMA to/from the current buffer and performs automatic buffer switching. Buffer switching consists of reading the next buffer descriptor table entry from memory, where the descriptor (indicated by the sequencing information in each entry in the buffer descriptor table) is automatically fetched by hardware, and updating the buffer pointer and size from the table entry; thus, the next buffer address is obtained automatically from a table in memory by hardware. A buffer-end interrupt is optionally generated.
Data transfer is most efficient for Data Out FIFOs if the buffer sizes are a multiple of the DMA device width size and the start address is aligned on a width size boundary. For example, if the device is a 16-bit device with 2 data pin groups, the buffer size should be a multiple of 2 bytes and the start address should be on a half-word (2-byte) boundary. If the buffer is not also aligned on a DMA block size boundary, transfers will be inefficient until the address aligns on a DMA block size boundary. For Data In FIFOs, data transfer is most efficient if the programmer ensures the buffer sizes are a multiple of the DMA transfer block size and the start address is aligned on a DMA transfer block size boundary.
The following registers (indicated above in Table 1) are employed in scatter/gather mode:
TABLE 4
Reg. No
Type
Reg Name
Bit
Bit Name
Function
9
BIU
Packet
31:3
Address
Address bit 31:3 of
Descriptor
the table start; bits
Table Pointer
2:0 are always 0
2:0
Size
# of Table entries:
0 => Disable packet
descriptor generation
1 => # entries is 32
2 => # entries is 64
3 => # entries is 128
4 => # entries is 256
5–7 => reserved
10
BIU
Data Out
31:3
Address
Address bits 31:3 of
FIFO
start of table; bits
Buffer
2:0 are always 0
Descriptor
Table Pointer
2:1
Reserved
0
SGE
Scatter/Gather Enable
11
BIU
Data In
31:3
Address
Address bits 31:3 of
FIFO
start of table; bits
Buffer
2:0 are always 0
Descriptor
Table Pointer
2
PEI
Interrupt at Packet
End; 1 => interrupt
1
Reserved
0
SGE
Scatter/Gather Enable
32
BIU
Packet
31:11
Read/write bits
Descriptor
ignored by BIU
Table
Tail Pointer
10:3
Address bits of last
packet descriptor
processed
2:0
Reserved
33
BIU
Packet
31:13
Reserved
Descriptor
Status
Register
12:3
count
count of non-updates
of table because it
was full; saturates
at 0x3ff
2:0
Reserved
LSW
MEM
Buffer
31:0
Address
Buffer Address
Descriptor
Table
Entry -
Word 0
MSW
MEM
Buffer
31
EOBI
Interrupt at end-of-
Descriptor
buffer; 1 => interrupt
Table
Entry -
Word 1
30
EOBT
Terminate of end-of-
buffer; 1 => clear
SGE bit of reg 10 or
11
29:28
Reserved
27:21
NEXT
Address bits 9:3 of
next entry to use
20
Reserved
19:0
BSIZE
Buffer Size
LSW
MEM
Packet
31:0
Packet address
Descriptor
Table
Entry -
Word 0
MSW
MEM
Packet
31
PINC
Packet incomplete;
Descriptor
1 => incomplete
Table
Entry -
Word 1
30
PLAST
Last part of
incomplete packet; 1 => last part
29:20
reserved
19:0
PSIZE
Packet size
Packet
31:4
reserved
End
Interrupt
Write Value
3:2
Channel
DMA channel of FIFO
causing interrupt
1
Direction
0 => Data in FIFO, 1 => Data
Out FIFO
0
Type
0 => End of buffer, 1 => End
of packet
With reference to
Automatic buffer switching takes place when a buffer end event occurs (block 212). A buffer end event occurs when a transfer block is written to/from memory and the current buffer becomes full/empty. If no buffer end event occurs (block 212), the DMA operation continues (block 210). If a buffer end event occurs (block 212), and data transfer terminates (block 214) (as will be discussed in greater detail below, an end-of-buffer event may cause a scatter/gather operation to terminate), the process stops (block 216). However, if data transfer is not terminated (block 214), automatic buffer switching takes places to allow the DMA operation to continue. A packet descriptor is optionally assembled (block 222). The packet size counter is reset (block 224). A packet descriptor, a packet end interrupt, and a buffer end interrupt (discussed in greater detail below) are optionally written out (blocks 226, 228, and 230); the packet end interrupt and buffer end interrupt allow the controlling processor to initiate packet and buffer processing when a packet is complete or when the buffer is ready without constant status polling. In automatic buffer switching, the BIU reads the next buffer descriptor using the address in the buffer descriptor table pointer register (block 204). The DMA address register and the buffer size are updated based on the just-read buffer descriptor (block 206). The address in the buffer descriptor table pointer register is updated based on the just-read buffer descriptor (block 208) and the transfer block is written to memory (block 210). DMA transfers should have priority over descriptor and interrupt generation. In one embodiment, reading the next buffer descriptor (block 204) may be done ahead of time and updating the DMA address register and buffer size and optionally assembling a packet descriptor may be done in parallel in the cycle following the buffer-end event. In this embodiment, buffer switching will take only one cycle. The time to complete buffer switching is very short since buffer switching, which is done by hardware and is decoupled from software, requires one local memory access only; in one embodiment, it requires 20 local bus cycles or less to complete. If reading the next buffer descriptor from memory is done ahead of time, buffer switching time can effectively be reduced to 5 nsecs.
If a protocol is used where the packet size is not always a multiple of the DMA block transfer size, the BIU needs to be told when an incoming packet has ended in order to force the last few bytes to be written to memory. This is particularly important for incoming packets since packets generally will not be a multiple of DMA block transfer size and therefore the BIU needs to be told when the packet has ended in order to force the last few bytes to be written to memory.
In order to get the BIU to boundary align input data, the PSM issues a Clock Data In and Round Up command at the end of a packet. (In some embodiments, the Clock Data In and Round Up Command also gets the BIU to generate packet descriptors and end-of-packet interrupts.) Boundary alignment means that the Data In FIFO DMA address is incremented by the DMA block size regardless of the actual amount of data written to the FIFO when the Round Up command, which is associated with the last byte of a packet, was received. As a result, the next packet that is written out will start on a DMA block size boundary.
A buffer end interrupt causes a 32-bit write to the address specified in DMA register 25 or 27 (depending on whether the FIFO is Data In or Data Out) indicating the interrupt type and DMA channel number. (In this embodiment, the DMA block transfer size is 32 bits; in other embodiments with different block transfer sizes, the bit length of the write is equal to the DMA block transfer size.) When the PE receives a buffer end interrupt it will possibly write new value(s) to the table entry whose buffer has just been emptied or filled and possibly process the data in a just-filled buffer.
As noted above, the BIU can optionally write out a packet descriptor to a packet descriptor table upon detecting an end-of-packet event, which may include an end-of-buffer event. An end-of-packet event occurs one of two ways: 1) when the last byte of a packet, indicated by a Round Up command, has been written out to memory; or 2) when the current buffer fills up but the current packet is not finished (i.e., an end-of-buffer event where no Round Up command is associated with the DMA transfer block that fills up the current buffer). The packet descriptors are written to the current location in the packet descriptor table, in one embodiment, an octet-aligned circular buffer in I/O Quad data memory. In one embodiment, the packet descriptor table can be as little as 32 packet descriptors (256 bytes) or as large as 256 (2048 bytes) packet descriptors. The packet descriptor table pointer register (DMA register 9), which points to the location that will be written to when the next packet descriptor is written out, is updated in place and can be polled to determine whether there are any new packet descriptors to be processed. The start address and size of the packet descriptor table are derived from the packet descriptor table pointer register.
The packet descriptor includes a packet start address, a packet size, and a bit indicating whether the packet is split across a buffer boundary. In one embodiment, packet descriptors are octet-aligned and 8 bytes long. An exemplary format is shown in Table 4. PSIZE contains the packet size (if bit 31 is clear) or the size of the current packet fragment (if bit 31 is set, indicating a packet end event was caused by a buffer switch where the last transfer block to fill up the buffer did not have a Round Up command associated with it and allowing the PE/MTE to detect when a packet is split across buffers). Bit 30 is set if bit 31 was set for the last packet descriptor and this packet descriptor was generated due to a Round Up command. Bits 31 and 30 allow the PE/MTE to determine if the packet is a complete packet (bits 31:30 have the logic values 0,0), the first part of a packet (bits 31:30 have the logic values 1,0), or the last part of a packet that was split across buffers (bits 31:30 have the logic values 0,1). This is useful if one of the packet descriptors for a packet split across two buffers is lost, since it allows the software to quickly determine if parts of a split packet were lost due to packet descriptor table being full (discussed in greater detail below).
A packet end interrupt is optionally issued (depending on the setting in the buffer descriptor table pointer register) after a packet end event due to Round Up occurs. The packet end interrupt causes a 32-bit write to the address specified in DMA register 34, the packet end interrupt address. The value written indicates the interrupt type and the DMA channel number. If packet descriptor generation is enabled (bits 2:0 of the packet descriptor table pointer register are not 0,0,0), and packet end interrupts are enabled, then the packet end interrupt is generated after the packet descriptor has been written out to memory.
In
The packet descriptor table never overflows due to hardware throttling of packet descriptors. When the table is full, packet descriptors are not written out and the packet is dropped. The table is almost full when the head pointer (the packet descriptor table pointer register) is equal to the packet descriptor table tail pointer register minus 8; indicating there are only two available slots in the table. These slots are never filled and the packet descriptors are dropped to prevent overflow. As noted above, when scatter/gather is enabled, the packet descriptor table tail pointer is initialized to point to the packet descriptor table start address, signaling the table is empty. DMA register 33, the Data In FIFO packet descriptor status register, counts the number of times a packet descriptor is dropped. This register saturates at 0×3FF. Writing to this register, which is a write to clear register, causes the COUNT field to be reset to 0.
A buffer end condition (where the current buffer fills up with incoming data or is emptied of outgoing data) may terminate scatter/gather operation. If the EOBT bit (as shown in Table 4) is set, an end-of-buffer event will clear the scatter/gather enable (“SGE”) bit, causing hardware to terminate scatter/gather operation without software intervention. Termination of scatter/gather operation may occur when the data stream is finished. (Other operations may continue in scatter/gather mode.)
In some embodiments where wider interfaces are used, such as 16-bit or 32-bit devices, the packet size may not be a multiple of device width. When this occurs, the packet descriptor PSIZE field will include the unused bytes in the last I/O bus transfer because the BIU has no way of knowing how many of the last bytes are valid when it receives a Round Up command.
In one embodiment, a status byte is appended to the end of a packet when the PSM issues one of two commands—Input Status or Input Status and Round Up. The status byte notifies the PE how many of the last “device width” bytes are valid and the PE can then update the packet descriptor or internally use the corrected value. When either of these commands is issued, the 8-bit status from the PSM and pins will be clocked into the pin group's Data In FIFO. If the Input Status and Round Up command is issued, the Round Up bit will be set for that byte of data. When either of these commands is issued, the status generated in the Data In FIFO's pin group is pushed to the pin group's Data In FIFO.
Machnicki, Erik P., Longley, Mark, Simon, Moshe B.
Patent | Priority | Assignee | Title |
10698854, | Feb 27 2019 | International Business Machines Corporation | Secure and efficient application data processing |
11449367, | Feb 27 2019 | International Business Machines Corporation | Functional completion when retrying a non-interruptible instruction in a bi-modal execution environment |
7610415, | Jul 28 2005 | DIGI INTERNATIONAL INC | System and method for processing data streams |
8321605, | Dec 13 2010 | Apple Inc.; Apple Inc | PIO interjection between beats of a DMA operation |
Patent | Priority | Assignee | Title |
5991817, | Aug 07 1996 | Cisco Technology, Inc | Apparatus and method for a network router |
6647438, | Sep 19 2000 | Intel Corporation | Direct memory access transfer reduction method and apparatus to overlay data on to scatter gather descriptors for bus-mastering I/O controllers |
20030065735, | |||
20030120835, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Jul 19 2004 | SIMON, MOSHE B | Cradle Technologies | CORRECTION OF ASSIGNEE NAME, PREVIOUSLY RECORDED AT REEL 015679 FRAME 0719 | 022489 | /0945 | |
Jul 19 2004 | MACHNICKI, ERIK P | Cradle Technologies | CORRECTION OF ASSIGNEE NAME, PREVIOUSLY RECORDED AT REEL 015679 FRAME 0719 | 022489 | /0945 | |
Jul 19 2004 | LONGLEY, MARK | Cradle Technologies | CORRECTION OF ASSIGNEE NAME, PREVIOUSLY RECORDED AT REEL 015679 FRAME 0719 | 022489 | /0945 | |
Jul 19 2004 | SIMON, MOSHE B | CRADLE TECHNOLOGIES, INC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 015679 | /0719 | |
Jul 19 2004 | MACHNICKI, ERIK P | CRADLE TECHNOLOGIES, INC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 015679 | /0719 | |
Jul 19 2004 | LONGLEY, MARK | CRADLE TECHNOLOGIES, INC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 015679 | /0719 | |
Jul 26 2004 | Cradle Technologies, Inc. | (assignment on the face of the patent) | / | |||
Nov 10 2011 | Cradle Technologies | Cradle IP, LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 027210 | /0764 |
Date | Maintenance Fee Events |
Aug 31 2010 | M2551: Payment of Maintenance Fee, 4th Yr, Small Entity. |
Dec 29 2014 | M2552: Payment of Maintenance Fee, 8th Yr, Small Entity. |
Mar 11 2019 | REM: Maintenance Fee Reminder Mailed. |
Aug 26 2019 | EXP: Patent Expired for Failure to Pay Maintenance Fees. |
May 03 2021 | M2553: Payment of Maintenance Fee, 12th Yr, Small Entity. |
May 03 2021 | M2558: Surcharge, Petition to Accept Pymt After Exp, Unintentional. |
May 03 2021 | PMFG: Petition Related to Maintenance Fees Granted. |
May 03 2021 | PMFP: Petition Related to Maintenance Fees Filed. |
Date | Maintenance Schedule |
Jul 24 2010 | 4 years fee payment window open |
Jan 24 2011 | 6 months grace period start (w surcharge) |
Jul 24 2011 | patent expiry (for year 4) |
Jul 24 2013 | 2 years to revive unintentionally abandoned end. (for year 4) |
Jul 24 2014 | 8 years fee payment window open |
Jan 24 2015 | 6 months grace period start (w surcharge) |
Jul 24 2015 | patent expiry (for year 8) |
Jul 24 2017 | 2 years to revive unintentionally abandoned end. (for year 8) |
Jul 24 2018 | 12 years fee payment window open |
Jan 24 2019 | 6 months grace period start (w surcharge) |
Jul 24 2019 | patent expiry (for year 12) |
Jul 24 2021 | 2 years to revive unintentionally abandoned end. (for year 12) |