Peripheral controller with paged data buffer management

• US 4,888,727 A
• Filed: 01/10/1989
• Issued: 12/19/1989
• Est. Priority Date: 01/10/1989
• Status: Expired due to Term

• Current Assignee: Honeywell Bull Incorporated
• Original Assignee: Bull HN Information Systems Incorporated (Atos SE)
• Inventors: Gardner, Joseph P., Bradley, John W., Votolato, Alfred F., Getson, Edward F. Jr.
• Primary Examiner(s): Smith, Jerry
• Assistant Examiner(s): Kulbaski, James J.
• Application Number:
  US07/295,335
• Time in Patent Office: 343 Days
• Field of Search: 364/200 MS File, 364/900 MS File
• US Class Current: 710/56
• CPC Class Codes: G06F 13/124 where hardware is a sequential transfer control unit, e.g. microprocessor, peripheral processor or state-machine
• CPC Class Codes: G06F 2205/064 Linked list, i.e. structure using pointers, e.g. allowing non-contiguous address segments in one logical buffer or dynamic buffer space allocation
• CPC Class Codes: G06F 2205/066 User-programmable number or size of buffers, i.e. number of separate buffers or their size can be allocated freely
• CPC Class Codes: G06F 5/065 Partitioned buffers, e.g. allowing multiple independent queues, bidirectional FIFO's

Abstract

A controller controls data transfers between a data processing system bus and peripheral devices. In the controller, data buffers are divided into page frames. Paging circuitry provides for allocation and deallocation of pages to and from the data buffer. Included in the page circuitry is a paging RAM. The paging RAM and other paging circuitry components allow contiguously addressed pages of data to be stored in noncontiguous locations in the data buffer. There may be more than one data buffer and these data buffers may be exclusively seized by microprocessors in the controller via seizing logic.

Claims

1. A controller for controlling data transfers between a data processing system bus and peripheral devices comprising:

a. at least one data buffer divided into page frames for temporarily storing pages of data transferred between said data processing system bus and said peripheral devices;

b. a first microprocessor for controlling data transfers between said data processing system bus and said at least one data buffer;

c. a second microprocessor for controlling data transfers between said at least one data buffer and said peripheral devices;

d. a paging means coupled to said first and second microprocessors for identifying page frames of said at least one data buffer which are assigned pages of data by said microprocessors in a non-predetermined order and coupled to said at least one data buffer to address page frames identifies in the paging means.

2. A controller as recited in claim 1 wherein there are at least two data buffers comprising random access memories which may be accessed separately by either the first microprocessor or the second microprocessor.

3. A controller as recited in claim 2 wherein at least one of the data buffers may be exclusively used only for temporarily storing data to be read from the peripheral devices.

4. A controller as recited in claim 2 further comprising seizing means for a microprocessor to exclusively seize a data buffer for as long as it takes to complete a data transfer to or from the data buffer.

5. A controller as recited in claim 1 wherein the page frames of the at least one data buffer are of equal size.

6. A controller as recited in claim 1 further comprising a scratch pad memory for storing interprocessor communications between the microprocessors.

7. A controller as recited in claim 1 wherein the paging means comprises for each data buffer a paging RAM for storing a page address of a page in a data buffer corresponding to the page indicated by an incoming address sent by one of the microprocessors, wherein that page is amongst a set of pages allocated to the peripheral device from which the data originated or to which the data is destined.

8. A controller as recited in claim 7 wherein the paging means further comprises a set of page tables stored in a shared scratch pad memory for keeping track of which pages are free and which are not free.

9. A controller as recited in claim 7 wherein the paging means further comprises for each data buffer an address register for storing incoming addresses from the microprocessors.

10. A controller as recited in claim 9 wherein for each data buffer an address register multiplexer is connected to the address register to determine whether an input address enters the address register and selects which input address in a set of input addresses is allowed to enter the address register.

11. A controller as recited in claim 10 further comprising a means for a microprocessor to exclusively seize a data buffer for as long as it takes to complete a data transfer to or from the data buffer.

12. A controller as recited in claim 9 wherein an address in the address register is divided into two parts with a first part comprising leading bits of the address and a second part comprising trailing bits wherein the leading bits of the address are passed to the paging RAM and used to select a page in the data buffer, and the trailing bits are passed to the buffer segment and used to select a specific memory location within the selected page.

13. A controller as recited in claim 7 wherein the paging RAM stores page addresses at memory addresses indexed by a device from which data to be transferred originated or to which the data to be transferred is destined.

14. A controller as recited in claim 7 further comprising a index register which passes to the paging RAM an index indicative of a device from which data to be transferred originated or to which data to be transferred is destined.

15. In a controller which controls data transfers between a data processing system bus and peripheral devices, a method of managing data transfers to and from a data buffer comprising the steps of:

a. loading an address into an address register;

b. passing leading bits of the address in the address register to a paging RAM;

c. passing to the paging RAM a device identifier that identifies a device from which data to be transferred originated or to which data to be transferred is destined;

d. using the leading bits and the device identifer to locate a page frame address stored in the paging RAM;

e. passing the page frame address to a data buffer to locate an addressed page;

f. locating a specific memory location sought within the located page by trailing bits of the address in the address register;

g. performing a data transfer to or from the addressed location.

16. A method of controlling data transfers between a data processing system bus and peripheral devices comprising the steps of:

a. dividing a data buffer into page frames;

b. dividing data to be transferred into blocks using a first microprocessor;

c. transferring the pages of data into page frames of the data buffer using the first microprocessor;

d. retrieving the pages of data stored in the page frames of the data buffer using a second microprocessor;

e. transferring the retrieved pages using the second microprocessor.

17. A method of managing a paged data buffer located in a controller comprising the steps of:

a. loading a page table into a scratch pad memory wherein each page in the page table is initially marked free;

b. making a request to either read data from or write data to the data buffer;

c. if a write request,

checking for a free page in the page table;

checking to see if any pages have been marked no longer free for this write request;

if no other pages have been marked no longer free for this write request, repeating the steps beginning with checking for a free page;

if other pages have been marked no longer free for this write request, performing the write for the pages already allocated and performing no further steps;

marking a page no longer free;

updating a page RAM to store the page frame address of a page being marked no longer free in a location in the paging RAM;

checking to see that enough pages have been allocated to handle the entire write request;

if not enough pages have been allocated, repeating the above steps;

if enough pages have been allocated, performing the write request; and

d. if a read request,

performing the read; and

marking pages which were read free in the page table.