A peripheral system includes (a) a peripheral device having peripheral memory located thereon, (b) at least one input/output (I/O) card communicating with the peripheral device, and (c) a means for managing the peripheral memory between the peripheral device and the at least one I/O card. In a preferred embodiment, the means for managing the peripheral memory includes (a) a means for determining, during normal operation, an optimum amount of peripheral memory for allocating to each I/O card, and (b) a means for allocating, during normal operation, the optimum amount of peripheral memory to each I/O card. A preferred method for managing memory, between a peripheral device, having peripheral memory thereon, and at least one input/output (I/O) card, includes (a) determining, during normal operation, an optimum amount of peripheral memory for allocating to each I/O card, and (b) allocating, during normal operation, the optimum amount of peripheral memory to each I/O card.
|
18. A method for managing memory between a peripheral device, having peripheral memory thereon, and at least one input/output (I/O) card having at least one channel, the method comprising:
(a) determining, during normal operation, a first optimum amount of peripheral memory for allocating to each I/O card; (b) determining, during normal operation, a second optimum amount of peripheral memory for allocating to each channel; (c) allocating, during normal operation, the first optimum amount of peripheral memory to each I/O card; and, (d) allocating, during normal operation, the second optimum amount of peripheral memory to each channel.
14. A system for managing memory between a peripheral device, having peripheral memory thereon, and at least one input/output (I/O) card having at least one channel, the system comprising:
(a) first means for determining, during normal operation, a first optimum amount of peripheral memory for allocating to each I/O card; (b) second means for determining, during normal operation, a second optimum amount of peripheral memory for allocating to each channel; (c) first means for allocating, during normal operation, the first optimum amount of peripheral memory to each I/O card; and, (d) second means for allocating, during normal operation, the second optimum amount of peripheral memory to each channel.
7. A peripheral system comprising:
(a) a peripheral device having peripheral memory located thereon; (b) at least one input/output (I/O) card communicating with the peripheral device, the at least one I/O card having at least one channel; (c) means for allocating the peripheral memory between the peripheral device, the at least one I/O card, and each channel of each I/O card; (d) first I/O card means for returning to the peripheral device, during normal operation, control of an amount of peripheral memory allocated to the at least one I/O card; and, (e) second I/O card means for returning to the peripheral device, during normal operation, control of an amount of peripheral memory allocated to the at least one channel.
1. A peripheral system comprising:
(a) a peripheral device having peripheral memory located thereon; (b) at least one input/output (I/O) card having at least one channel and communicating with the peripheral device; (c) means for allocating the peripheral memory between the peripheral device, the at least one I/O card, and each channel of the at least one I/O card; (d) first peripheral means for reclaiming from the at least one I/O card, during normal operation, control of an amount of peripheral memory allocated to the at least one I/O card; and, (e) second peripheral means for reclaiming from the at least one channel, during normal operation, control of an amount of peripheral memory allocated to the at least one channel.
6. A method for managing memory between a peripheral device, having peripheral memory thereon, and at least one input/output (I/O) card having at least one channel, the method comprising:
(a) determining, during normal operation, a first optimum amount of peripheral memory for allocating to each I/O card; (b) determining, during normal operation, a second optimum amount of peripheral memory for allocating to each channel; (c) allocating, during normal operation, the first optimum amount of peripheral memory to each I/O card; and, (d) allocating, during normal operation, the second optimum amount of peripheral memory to each channel; and, wherein the first and second optimum amounts of peripheral memory are determined from, selectively, an amount of I/O activity, a print job status, a print job size, a print job priority, an I/O transmission speed, and an I/O type.
5. A system for managing memory between a peripheral device, having peripheral memory thereon, and at least one input/output (I/O) card having at least one channel, the system comprising:
(a) first means for determining, during normal operation, a first optimum amount of peripheral memory for allocating to each I/O card; (b) second means for determining, during normal operation, a second optimum amount of peripheral memory for allocating to each channel; (c) first means for allocating, during normal operation, the first optimum amount of peripheral memory to each I/O card; (d) second means for allocating, during normal operation, the second optimum amount of peripheral memory to each channel; and, wherein the first and second means for determining each include a means for considering, selectively, an amount of I/O activity, a print job status, a print job size, a print job priority, an I/O transmission speed, and an I/O type.
10. A peripheral system comprising:
(a) a peripheral device having peripheral memory located thereon; (b) at least one input/output (I/O) card having at least one channel and communicating with the peripheral device; and, (c) means for managing the peripheral memory between the peripheral device, the at least one I/O card, and each channel of the at least one I/O card, the means for managing the peripheral memory including: (i) first means for determining, during normal operation, a first optimum amount of peripheral memory for allocating to each I/O card; (ii) second means for determining, during normal operation, a second optimum amount of peripheral memory for allocating to each channel; (iii) first means for allocating, during normal operation, the first optimum amount of peripheral memory to each I/O card; and (iv) second means for allocating, during normal operation, the second optimum amount of peripheral memory to each channel. 9. A peripheral system comprising:
(a) a peripheral device having peripheral memory located thereon; (b) at least one input/output (I/O) card communicating with the peripheral device; and, (c) means for managing the peripheral memory between the peripheral device and the at least one I/O card, the means for managing the peripheral memory including: (i) means for determining, during normal operation, an optimum amount of peripheral memory for allocating to each I/O card, the means for determining including means for considering, selectively, an amount of I/O activity, a print job status, a print job size, a print job priority, an I/O transmission speed, and an I/O type; (ii) means for allocating, during normal operation, the optimum amount of peripheral memory to each I/O card; and (iii) I/O card means for returning to the peripheral device, during normal operation, control of the amount of peripheral memory allocated to the at least one I/O card. 3. A peripheral system comprising:
(a) a peripheral device having peripheral memory located thereon; (b) at least one input/output (I/O) card communicating with the peripheral device; and, (c) means for managing the peripheral memory between the peripheral device and the at least one I/O card, the means for managing the peripheral memory including: (i) means for determining, during normal operation, an optimum amount of peripheral memory for allocating to each I/O card, the means for determining including means for considering, selectively, an amount of I/O activity, a print job status, a print job size, a print job priority, an I/O transmission speed, and an I/O type; (ii) means for allocating, during normal operation, the optimum amount of peripheral memory to each I/O card; and (iii) peripheral means for reclaiming from the at least one I/O card, during normal operation, control of the amount of peripheral memory allocated to the at least one I/O card. 4. A peripheral system comprising:
(a) a peripheral device having peripheral memory located thereon, (b) at least one input/output (I/O) card having at least one channel and communicating with the peripheral device; and, (c) means for managing the peripheral memory between the peripheral device and the at least one I/O card, the means for managing the peripheral memory including: (i) first means for determining, during normal operation, a first optimum amount of peripheral memory for allocating to each I/O card, the means for determining including means for considering, selectively, an amount of I/O activity, a print job status, a print job size, a print job priority, an I/O transmission speed, and an I/O type; (ii) second means for determining, during normal operation, a second optimum amount of peripheral memory for allocating to each channel; (iii) first means for allocating, during normal operation, the first optimum amount of peripheral memory to each I/O card; and (iv) second means for allocating, during normal operation, the second optimum amount of peripheral memory to each channel. 2. The peripheral system of
(a) first means for determining, during normal operation, an optimum amount of peripheral memory for allocating to each I/O card; and, (b) second means for determining, during normal operation, an optimum amount of peripheral memory for allocating to each channel.
8. The peripheral system of
(a) first means for determining, during normal operation, an optimum amount of peripheral memory for allocating to each I/O card; and, (b) second means for determining, during normal operation, an optimum amount of peripheral memory for allocating to each channel.
11. The peripheral system of
(a) means for writing a packet to a queue position, each packet including: (i) a start of data packet header field containing a first value indicating an address in the peripheral memory of a buffer and, (ii) a maximum data length packet header field containing a second value indicating a size of the buffer; and, (b) peripheral means for selectively changing the first value and the second value.
12. The peripheral system of
13. The peripheral system of
15. The system of
(a) means for writing a packet to a queue position, each packet including: (i) a start of data packet header field containing a first value indicating an address in the peripheral memory of a buffer and, (ii) a maximum data length packet header field containing a second value indicating a size of the buffer; and, (b) peripheral means for selectively changing the first value and the second value.
16. The system of
17. The system of
19. The method of
(a) writing a packet to a queue position, each packet including: (i) a start of data packet header field containing a first value indicating an address in the peripheral memory of a buffer and, (ii) a maximum data length packet header field containing a second value indicating a size of the buffer; and, (b) the peripheral device selectively changing the first value and the second value.
20. The method of
21. The method of
|
|||||||||||||||||||||||||||
This invention relates, in general, to peripheral device systems and, more specifically, to memory management by peripheral devices with respect to associated input/output cards.
Many peripherals (i.e., printers and scanners) use the modular input/output (MIO) scheme where a modular input/output (I/O) card carries memory that is used to communicate with the peripheral. The memory, while residing on the I/O card, is also (at least in part) accessible to the processor(s) of the peripheral. This MIO scheme is described in Campbell et al., U.S. Pat. No. 5,197,128 and will be referred to as the conventional MIO protocol.
Since the memory resides on an individual I/O card in the conventional MIO protocol, the memory cannot be used by the peripheral to service another I/O card. Consequently, an I/O card's memory may wait unused while another I/O card operates at reduced efficiency for lack of memory.
In the conventional MIO protocol, the I/O card passes control of the memory to the peripheral during peripheral--I/O card initialization. The memory is logically broken up by the peripheral into smaller entities called buffers. The buffer size is based on a one time negotiation between the peripheral and the I/O card. The buffer size is fixed at initialization and may not be varied during normal operation. Since the buffer size is fixed, the peripheral must allocate a buffer to each I/O card which is at least large enough to serve the maximum data transfer which is likely to occur.
One prior art solution to the problem of fixed buffer size is to allocate a small buffer to the I/O card and copy data from I/O card memory into printer memory as necessary to free up I/O buffers. However, this solution takes processor time and bandwidth away from other operations, resulting in slower processing of other operations.
During operation, control (ownership) of the buffers moves back and forth between the peripheral and the I/O card. However, once the peripheral assigns buffers to an I/O channel of an I/O card, the peripheral cannot reclaim the buffer without an I/O card reset. Therefore, those buffers which were assigned to an I/O channel are essentially unavailable to other I/O channels that may be operating at reduced efficiency due to smaller buffer size. As a result, each I/O channel must be equipped with enough memory to serve anticipated I/O channel needs. This results in an unneeded duplication of costly memory and a reduced ability to increase memory by the addition of optional memory modules.
The conventional MIO protocol is adequate for peripherals with single I/O channels, but becomes strained under the increasing demands of peripherals with multiple I/O cards (or cards with multiple channels).
Accordingly, objects of the present invention are to provide a new system for managing memory between peripheral devices and I/O cards that overcomes the aforementioned limitations associated with conventional systems, that permits the peripheral devices to (1) allocate memory among I/O channels of the I/O card, based on the needs of each I/O channel; (2) allocate memory among the I/O cards based on the needs of each card; and (3) resize buffers during normal operation, without an I/O card reset.
According to principles of the present invention in a preferred embodiment, a system and method manage peripheral memory, located on a peripheral device, between the peripheral device and at least one input/output (I/O) card. Namely, the present invention comprises (a) a peripheral device having peripheral memory located thereon, (b) at least one I/O card communicating with the peripheral device, and (c) means for managing the peripheral memory between the peripheral device and the at least one I/O card. According to further principles in a preferred embodiment, the means for managing the peripheral memory includes (a) means for determining, during normal operation, an optimum amount of peripheral memory for allocating to each I/O card, and (b) means for allocating, during normal operation, the optimum amount of peripheral memory to each I/O card. Additionally in a preferred embodiment, an optimum amount of peripheral memory is determined for and allocated to each channel of each I/O card.
According to further principles of the present invention, a preferred method comprises (a) determining, during normal operation, an optimum amount of peripheral memory for allocating to each I/O card, and (b) allocating, during normal operation, the optimum amount of peripheral memory to each I/O card.
Other objects, advantages, and capabilities of the present invention will become more apparent as the description proceeds.
FIG. 1 is a block diagram of the present invention showing multiple input/output (I/O) cards attached to a peripheral device.
FIG. 2 is a block diagram showing the memory address locations for the peripheral and the I/O card of FIG. 1.
FIG. 3 is a diagram showing the field structure of a packet header.
FIGS. 4 and 5 are flow charts showing a preferred embodiment of transferring data from the peripheral to the I/O card of FIG. 1 or from the I/O card to the peripheral.
FIG. 1 is a block diagram showing peripheral device 10 communicating with multiple input/output (I/O) cards 15. Although only two I/O cards 15 are shown, any number of I/O cards 15 may be connected to peripheral 10. Each I/O card 15 is provided in an associated host computer (not shown). Each host computer has one or more I/O cards 15 located therein. For illustrative purposes, multiple channels 20 are shown as multiple lines. However, multiple channels 20 may be implemented on a single physical communications path between peripheral 10 and I/O cards 20. Typically peripheral 10 is a printer. Alternatively, peripheral 10 is a scanner or any other peripheral which may communicate with multiple I/O cards or multiple I/O channels.
Located on peripheral 10 are peripheral memory 25, peripheral microprocessor 30, and peripheral Bus Controller ASIC 35. Peripheral memory 25 is allocated among I/O cards 15 and channels 20 for use in communications between peripheral 10 and I/O cards 15. Located on I/O card 15 are card microprocessor 40, card memory 45, and PCI interface ASIC 50. PCI interface ASIC 50 communicates with Bus Controller ASIC 35. PCI interface ASIC 50 contains PCI configuration register 55 and card register block 65.
Referring now to FIG. 2, a block diagram is shown which depicts memory address locations in a preferred embodiment of the present invention. Within PCI configuration register 55 is a base address register 60. Base address register 60 contains the memory address of card register block 65. Card register block 65 contains the following registers: peripheral to card queue base address 70, peripheral producer index 75, card consumer index 80, card to peripheral queue base address 85, card producer index 90, peripheral consumer index 95, queue position size 97, and queue number of positions 98.
Peripheral to card queue base address register 70 and card to peripheral queue base address register 85 contain, respectively, the base addresses for the peripheral to card (outbound) queue 100 and the card to peripheral (inbound) queue 105. Inbound and outbound queues 100, 105 are located on peripheral 10. Each queue 100, 105 contains queue positions 110. Queue positions 110 contain packets of information.
Referring to FIG. 3, each packet contains a packet header 115. In a preferred embodiment of the present invention, each packet header 115 includes packet header fields 120-145 and 155-175. Requester handle packet header field 120 identifies a request made by peripheral 10. I/O card 15 will then send the contents of this field 120 with the response so that peripheral 10 will be able to match the response with the request.
Command packet header field 125 identifies the major action to be performed by I/O card 15. Modifier packet header field 130 identifies the minor action to be performed by I/O card 15. Return status packet header field 135 identifies the result of performing the action(s) specified by command field 125 and modifier field 130.
Packet type packet header field 140 indicates whether the packet is a type which has associated data or does not have associated data. Start of data packet header field 145 contains the address of the first byte of data in the buffer 150 (FIG. 2) associated with the packet header 115. This field 145 is controlled by peripheral 10 and cannot be modified by I/O card 15.
Data length packet header field 155 indicates the number of valid data bytes present in the buffer 150 associated with the packet header 115. Maximum data length packet header field 160 indicates a maximum number of bytes of data that may be placed into the buffer 150 associated with the packet header 115. This field 165 is controlled by peripheral 10 and cannot be modified by I/O card 15.
I/O channel packet header field 165 indicates the logical I/O channel relating to the packet transaction. This field 165 provides a means of addressing packet headers 115 to or from separate I/O cards 15. The means of addressing is referred to as the channel 20 (FIG. 1).
Peripheral unit packet header field 170 indicates the peripheral unit or service relating to the packet transaction. This field 170 provides a means of addressing packet headers 115 to or from separate end points of peripherals 10. Command information packet header field 175 contains auxiliary parameters in the packet header 115 for general request/response command usage. The end points of peripheral 10 are those portions of peripheral 10 which carry out separate functions. Examples of such functions in a printer include 1) printing data and 2) receiving control messages.
Referring again to FIG. 2, peripheral producer index 75 indicates the next queue position 110 to be filled in by the peripheral 10, but not yet filled in. Card consumer index 80 indicates the next queue position 110 to be retrieved by the card, but not yet retrieved. Similarly, card producer index 90 indicates the next queue position 110 to be filled in by the card 15, but not yet filled in. Also, peripheral consumer index 95 indicates the next queue position 110 to be retrieved by the peripheral, but not yet retrieved.
When there is no data in outbound queue 100 for card 15 to process, peripheral producer index 75 and card consumer index 80 are equal. Also, when there is no data in inbound queue 105 for peripheral 10 to process, card producer index 90 and peripheral consumer index 95 are equal. A queue 100 (105) is full when the producer index 75 (90) ⊕ one is equal to the consumer index 80 (95). The symbol ⊕ is used to indicate circular addition, which is defined to wrap around to the first queue position 110 when the last queue position 110 has been passed.
Allocating peripheral memory 25 to I/O cards 15 is accomplished by writing new values to start of data packet header field 145 and/or maximum data length packet header field 160. Since these fields 145, 160 are under the complete control of peripheral 10, changing the location and/or size of buffer 150 is accomplished without any action on the part of I/O cards 15. As a result, peripheral 10 may allocate and reallocate peripheral memory 25 during normal operation, without a protocol reset between peripheral 10 and I/O cards 15. Normal operation is defined in this context as any time after peripheral--I/O card initialization when the peripheral and the I/O card are communicating.
In a preferred embodiment, peripheral 10 initially allocates small buffers to each I/O card and to each channel 20 of each I/O card 15. As I/O cards 15 or channels 20 require more memory, peripheral 10 allocates peripheral memory 25 as required to provide the optimum amount of peripheral memory 25 to each I/O card 15 and each channel 20. As I/O card 15 or channels 20 requires less memory, I/O card 15 returns control of the peripheral memory 25 to peripheral 10. Optionally, peripheral 10 may reclaim the peripheral memory 25 from I/O card 15. Peripheral 10 reclaims peripheral memory 25 by requesting control of the peripheral memory 25 from I/O card 15. As control of the peripheral memory 25 is returned to peripheral 10, peripheral 10 reallocates the peripheral memory 25 to other I/O cards 15 or channels 20 in order to provide the optimum amount of memory to each I/O card 15 and each channel 20.
Peripheral 10 may determine how much peripheral memory 25 is the optimum amount based on any information which is available to peripheral 10. Typical examples of information which peripheral 10 may use include: peripheral memory available, I/O activity, print job status, print job size, print job priority, I/O transmission speed, utilization of previously passed buffers, I/O type, and print job data buffering.
FIGS. 4 and 5 are flow charts showing a preferred embodiment of how packets are transferred from peripheral 10 to card 15 or from card 15 to peripheral 10. Referring to FIG. 4, packets are transferred from peripheral 10 to card 15 in the following manner. Peripheral 10 first determines 205 if the number of outstanding packets is less than the maximum number of outstanding packets determined at initialization by I/O card 15. The maximum number of outstanding packets is the maximum number of packets that I/O card 15 can hold. If the number of outstanding packets is greater than the maximum number, peripheral 10 waits until I/O card 15 has processed some of the packets.
If the number of outstanding packets is less than or equal to the maximum number, peripheral 10 determines 210 if outbound queue 100 has space available. If no space is available in outbound queue 100, peripheral 10 waits until outbound queue 100 has space available. If outbound queue 100 has space available, peripheral 10 begins to store 215 the packets in outbound queue 100 at the position 110 indicated by peripheral producer index 75. After the current queue position 110 has been filled, peripheral producer index 75 is advanced 220 to the next position 110. If packets remain to be stored 225, peripheral 10 again determines 210 if space is available in outbound queue 100, and if so, begins to store 215 packets in the next position 110 indicated by peripheral producer index 75. This process continues until outbound queue 100 is full 210 or the packets have all been stored 225 to outbound queue 100. If outbound queue 100 is full 210, peripheral 10 waits until space is available 210 in outbound queue 100 before storing 215 additional packets to outbound queue 100.
Referring now to FIG. 5, when card 15 recognizes 230 that peripheral producer index 75 and card consumer index 80 are unequal, card 15 begins to retrieve 235 packets from outbound queue 100 at the position 110 indicated by card consumer index 80. After card 15 has finished retrieving packets from queue position 110, card consumer index 80 is advanced 240. If packets remain to be retrieved, card 15 begins to retrieve packets from the next queue position 110 indicated by card consumer index 80. This process continues until all packets have been retrieved 245 from outbound queue 100, which occurs when peripheral producer index 75 and card consumer index 80 are equal once again.
Referring again to FIG. 4, packets are transferred from card 15 to peripheral 10 in a manner similar to the process described for transferring packets from peripheral 10 to card 15, except that step 205 is omitted. I/O card 15 determines 210 if inbound queue 105 has space available. If no space is available in inbound queue 105, card 15 waits until inbound queue 105 has space available. If inbound queue 105 has space available, card 15 begins to store 215 the packets in inbound queue 105 at the position 110 indicated by card producer index 90. After the current queue position 110 has been filled, card producer index 90 is advanced 220 to the next position 110. If packets remain to be stored 225, card 15 again determines 210 if space is available in inbound queue 105, and if so, begins to store 215 packets in the next position 110 indicated by card producer index 90. This process continues until inbound queue 105 is full 210 or the packets have all been stored 225 to inbound queue 105. If inbound queue 105 is full 210, card 15 waits until space is available 210 in inbound queue 105 before storing 215 additional packets to inbound queue 105. This process continues until all packets have been retrieved 245 from inbound queue 105, which occurs when card producer index 90 and peripheral consumer index 95 are equal once again.
Referring again to FIG. 5, when peripheral 10 recognizes 230 that card producer index 90 and peripheral consumer index 95 are unequal, peripheral 10 begins to retrieve 235 packets from inbound queue 105 at the position 110 indicated by peripheral consumer index 95. After peripheral 10 has finished retrieving packets from queue position 110, peripheral consumer index 95 is advanced 240. If packets remain to be retrieved, peripheral 10 begins to retrieve packets from the next queue position 110 indicated by peripheral consumer index 95.
If peripheral 10 has data to send to I/O card 15, peripheral 10 stores a packet to queue position 110 in outbound queue 100 informing I/O card 15 that there is data for I/O card 15 to retrieve. The start of data packet header field 145, the data length packet header field 155, and the maximum data length packet header field 160 define a buffer 150 where I/O card 15 will find the data. I/O card 15 will then retrieve the packet from queue position 110 in outbound queue 100. I/O card 15 then copies the data from the buffer 150 indicated by the packet header fields 145, 155, 160.
Peripheral 10 requests data from I/O card 15 by storing a packet to queue position 110 in outbound queue 110 requesting data from I/O card 15. The start of data packet header field 145, and the maximum data length packet header field 1 60 define a buffer 150 where peripheral 10 will store the data. I/O card 15 then stores data to buffer 150 and copies a packet to queue position 110 in inbound queue 105 informing peripheral 10 that there is data for peripheral 10 to retrieve. The packet will contain the same values for fields 145 and 160 as the packet requesting the data. Data length packet header field 155 will be modified by I/O card 15 to indicate the actual length of the data stored to buffer 150. Peripheral 10 will then retrieve the packet from queue position 110 in outbound queue 100. Peripheral 10 then copies the data from the buffer 150 indicated by the packet header fields 145, 155, 160.
The present invention has the novel advantage of allowing peripheral device 10 to allocate buffers between I/O cards 15 and between channels 20, depending on the needs of the individual I/O cards 15 and their respective channels 20. A further advantage is that peripheral device 10 may dynamically size the buffers during normal operation, without a protocol reset between I/O cards 15 and peripheral 10.
In summary, what has been described above are the preferred embodiments for a system and method of managing memory between a peripheral device and at least one I/O card. While the present invention has been described by reference to specific embodiments, it will be obvious that other alternative embodiments and methods of implementation or modification may be employed without departing from the true spirit and scope of the invention.
Jahr, Steven J., Smith, Kevin N., Wendt, James G., Fulghum, Patrick W., Gale, Thomas S.
| Patent | Priority | Assignee | Title |
| 10073714, | Mar 11 2015 | SanDisk Technologies, Inc | Task queues |
| 10108518, | Apr 07 2016 | International Business Machines Corporation | Device interference detection and remediation |
| 10379903, | Mar 11 2015 | SanDisk Technologies, Inc | Task queues |
| 11061721, | Mar 11 2015 | SanDisk Technologies, Inc | Task queues |
| 6519686, | Jan 05 1998 | Intel Corporation | Information streaming in a multi-process system using shared memory |
| 6600569, | Oct 27 1997 | Canon Kabushiki Kaisha | Printing control apparatus, printing control method, printing control system, and storage medium in which printing control program is stored |
| 6654861, | Jul 18 2001 | SmartMatic International Corporation | Method to manage multiple communication queues in an 8-bit microcontroller |
| 6718415, | May 14 1999 | ACQIS LLC | Computer system and method including console housing multiple computer modules having independent processing units, mass storage devices, and graphics controllers |
| 6983330, | Dec 29 1999 | EMC IP HOLDING COMPANY LLC | Method and apparatus for using multiple paths for processing out of band commands |
| 7089282, | Jul 31 2002 | International Business Machines Corporation | Distributed protocol processing in a data processing system |
| 7146446, | May 14 1999 | ACQIS LLC | Multiple module computer system and method |
| 7200844, | Aug 08 2002 | HEWLETT-PACKARD DEVELOPMENT COMPANY, L P | User installation of imaging device control system |
| 7228366, | Jun 29 2001 | Intel Corporation | Method and apparatus for deterministic removal and reclamation of work items from an expansion bus schedule |
| 7328297, | May 14 1999 | ACQIS LLC | Computer system utilizing multiple computer modules functioning independently |
| 7363415, | May 14 1999 | ACQIS LLC | Computer system utilizing multiple computer modules with serial interface |
| 7363416, | May 14 1999 | ACQIS LLC | Computer system utilizing multiple computer modules with password protection |
| 7376779, | May 14 1999 | ACQIS LLC | Multiple module computer system and method |
| 7404190, | Sep 18 2003 | Hewlett Packard Enterprise Development LP | Method and apparatus for providing notification via multiple completion queue handlers |
| 7581026, | Dec 28 2001 | Intel Corporation | Communicating transaction types between agents in a computer system using packet headers including format and type fields |
| 7617376, | Aug 14 2003 | Hewlett Packard Enterprise Development LP | Method and apparatus for accessing a memory |
| 7676624, | May 14 1999 | ACQIS LLC | Multiple module computer system and method including differential signal channel comprising undirectional serial bit channels |
| 7757232, | Aug 14 2003 | Hewlett Packard Enterprise Development LP | Method and apparatus for implementing work request lists |
| 7818487, | May 14 1999 | ACQIS LLC | Multiple module computer system and method using differential signal channel including unidirectional, serial bit channels |
| 8041873, | May 14 1999 | ACQIS LLC | Multiple module computer system and method including differential signal channel comprising unidirectional serial bit channels to transmit encoded peripheral component interconnect bus transaction data |
| 8150996, | Dec 16 2003 | Hewlett Packard Enterprise Development LP | Method and apparatus for handling flow control for a data transfer |
| 8234436, | May 14 1999 | ACQIS LLC | Computer system including peripheral bridge to communicate serial bits of peripheral component interconnect bus transaction and low voltage differential signal channel to convey the serial bits |
| 8626977, | May 14 1999 | ACQIS LLC | Computer system including CPU or peripheral bridge to communicate serial bits of peripheral component interconnect bus transaction and low voltage differential signal channel to convey the serial bits |
| 8671153, | Aug 20 2010 | ACQIS LLC | Low cost, high performance and high data throughput server blade |
| 8756359, | May 14 1999 | ACQIS LLC | Computer system including CPU or peripheral bridge to communicate serial bits of peripheral component interconnect bus transaction and low voltage differential signal channel to convey the serial bits |
| 8959171, | Sep 18 2003 | Hewlett Packard Enterprise Development LP | Method and apparatus for acknowledging a request for data transfer |
| 8977797, | May 14 1999 | ACQIS LLC | Method of improving peripheral component interface communications utilizing a low voltage differential signal channel |
| 9529768, | May 14 1999 | ACQIS LLC | Computer system including CPU or peripheral bridge directly connected to a low voltage differential signal channel that communicates serial bits of a peripheral component interconnect bus transaction in opposite directions |
| 9529769, | Mar 31 2005 | ACQIS LLC | Computer system including CPU or peripheral bridge directly connected to a low voltage differential signal channel that communicates serial bits of a peripheral component interconnect bus transaction in opposite directions |
| 9703750, | May 14 1999 | ACQIS LLC | Computer system including CPU or peripheral bridge directly connected to a low voltage differential signal channel that communicates serial bits of a peripheral component interconnect bus transaction in opposite directions |
| 9965323, | Mar 11 2015 | Western Digital Technologies, INC | Task queues |
| RE41076, | Oct 30 1998 | ACQIS LLC | Password protected modular computer method and device |
| RE41092, | May 14 1999 | ACQIS LLC | Data security method and device for computer modules |
| RE41294, | Oct 30 1998 | ACQIS LLC | Password protected modular computer method and device |
| RE41961, | Oct 30 1998 | ACQIS LLC | Password protected modular computer method and device |
| RE42814, | Oct 30 1998 | ACQIS LLC | Password protected modular computer method and device |
| RE42984, | May 14 1999 | ACQIS LLC | Data security method and device for computer modules |
| RE43119, | Oct 30 1998 | ACQIS LLC | Password protected modular computer method and device |
| RE43171, | May 14 1999 | ACQIS LLC | Data security method and device for computer modules |
| RE43602, | May 14 1999 | ACQIS LLC | Data security method and device for computer modules |
| RE44468, | May 14 1999 | ACQIS LLC | Data security method and device for computer modules |
| RE44654, | May 14 1999 | ACQIS LLC | Data security method and device for computer modules |
| RE44739, | May 14 1999 | ACQIS LLC | Data security method and device for computer modules |
| RE44933, | Oct 30 1998 | ACQIS LLC | Password protected modular computer method and device |
| RE45140, | May 14 1999 | ACQIS LLC | Data security method and device for computer modules |
| RE46947, | May 14 1999 | ACQIS LLC | Data security method and device for computer modules |
| RE48365, | Dec 19 2006 | Mobile Motherboard Inc. | Mobile motherboard |
| Patent | Priority | Assignee | Title |
| 4378588, | Sep 07 1976 | TCI-DELAWARE INCORPORATED, A CORP OF DEL | Buffer control for a data path system |
| 4591973, | Jun 06 1983 | L-3 Communications Corporation | Input/output system and method for digital computers |
| 4688166, | Aug 03 1984 | Motorola, Inc | Direct memory access controller supporting multiple input/output controllers and memory units |
| 4807121, | Jun 21 1984 | MORGAN STANLEY & CO , INCORPORATED | Peripheral interface system |
| 4839791, | Mar 08 1986 | NEC Corporation | Input/output buffer system |
| 5008808, | Jun 23 1988 | Storage Technology Corporation | Consolidation of commands in a buffered input/output device |
| 5197128, | Mar 04 1991 | Hewlett-Packard Company | Modular interface |
| 5220674, | Jul 17 1987 | HEWLETT-PACKARD DEVELOPMENT COMPANY, L P | Local area print server for requesting and storing required resource data and forwarding printer status message to selected destination |
| 5412781, | Jun 06 1991 | Siemens Aktiengesellschaft | Method and arrangement of buffer allocation in communication systems by employing fixed and dynamic buffer allocation functions |
| 5414816, | Dec 19 1988 | NEC Corporation | Data transfer apparatus having means for controlling the difference in speed between data input/output ports and memory access |
| 5418909, | Dec 30 1988 | International Business Machines Corporation | System for controlling multiple port/multiple channel I/O configuration according to communication request initiation status |
| 5485590, | Jan 08 1990 | Allen-Bradley Company, Inc. | Programmable controller communication interface module which is configurable by a removable memory cartridge |
| 5524214, | Jan 30 1992 | NEC Corporation | System for modification of dynamic buffer allocation by comparing modification request with current allocation and updating allocation based upon comparison discrepancy |
| 5640604, | Mar 16 1994 | Fujitsu Limited | Buffer reallocation system |
| 5687392, | May 11 1994 | Microsoft Technology Licensing, LLC | System for allocating buffer to transfer data when user buffer is mapped to physical region that does not conform to physical addressing limitations of controller |
| 5713041, | Jun 15 1994 | Intel Corporation | Computer system having a host CPU and a logic for integrating peripheral control functions into the host CPU |
| 5784698, | Dec 05 1995 | International Business Machines Corporation | Dynamic memory allocation that enalbes efficient use of buffer pool memory segments |
| 5797042, | Mar 16 1995 | Intel Corporation | Method and apparatus for adjusting the buffering characteristic in the pipeline of a data transfer system |
| 5838994, | Jan 11 1996 | Cisco Technology, Inc | Method and apparatus for the dynamic allocation of buffers in a digital communications network |
| 5907717, | Feb 23 1996 | AVAGO TECHNOLOGIES GENERAL IP SINGAPORE PTE LTD | Cross-connected memory system for allocating pool buffers in each frame buffer and providing addresses thereof |
| Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
| Oct 18 1996 | SMITH, KEVIN N | Hewlett Packard Company | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 008335 | /0311 | |
| Oct 23 1996 | JAHR, STEVEN J | Hewlett Packard Company | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 008335 | /0311 | |
| Oct 23 1996 | WENDT, JAMES G | Hewlett Packard Company | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 008335 | /0311 | |
| Oct 30 1996 | GALE, THOMAS S | Hewlett Packard Company | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 008335 | /0311 | |
| Nov 01 1996 | FULGHUM PATRICK W | Hewlett Packard Company | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 008335 | /0311 | |
| Nov 04 1996 | Hewlett-Packard Company | (assignment on the face of the patent) | / | |||
| May 20 1998 | Hewlett-Packard Company | Hewlett-Packard Company | MERGER SEE DOCUMENT FOR DETAILS | 011523 | /0469 |
| Date | Maintenance Fee Events |
| Mar 26 2003 | ASPN: Payor Number Assigned. |
| Sep 15 2003 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
| Sep 14 2007 | M1552: Payment of Maintenance Fee, 8th Year, Large Entity. |
| Oct 24 2011 | REM: Maintenance Fee Reminder Mailed. |
| Mar 14 2012 | EXP: Patent Expired for Failure to Pay Maintenance Fees. |
| Date | Maintenance Schedule |
| Mar 14 2003 | 4 years fee payment window open |
| Sep 14 2003 | 6 months grace period start (w surcharge) |
| Mar 14 2004 | patent expiry (for year 4) |
| Mar 14 2006 | 2 years to revive unintentionally abandoned end. (for year 4) |
| Mar 14 2007 | 8 years fee payment window open |
| Sep 14 2007 | 6 months grace period start (w surcharge) |
| Mar 14 2008 | patent expiry (for year 8) |
| Mar 14 2010 | 2 years to revive unintentionally abandoned end. (for year 8) |
| Mar 14 2011 | 12 years fee payment window open |
| Sep 14 2011 | 6 months grace period start (w surcharge) |
| Mar 14 2012 | patent expiry (for year 12) |
| Mar 14 2014 | 2 years to revive unintentionally abandoned end. (for year 12) |