Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

IIT Multilevel virtualization of I/O traffic of multiple Processing Units with the same or different OS via a Supervisory OS

IP.com Disclosure Number: IPCOM000177855D
Original Publication Date: 2009-Jan-06
Included in the Prior Art Database: 2009-Jan-06
Document File: 6 page(s) / 98K

Publishing Venue

IBM

Abstract

Multiple O/S's in a single integrated circuit do not share I/O ports without interruptions. With our solution, Supervisory Operating System (SOS) will manage the packet flows to I/O ports and/or execution unit without stopping them.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 70% of the total text.

Page 1 of 6

IIT Multilevel virtualization of I/O traffic of multiple Processing Units with the same or

different OS via a Supervisory OS
Cloverleaf route manager will act like a router which threads instructions intelligently to

O/S's. By changing the packet header information by the SOS, the packets can be

rerouted by using cloverleaf method. A full time multi O/S's system can process

everything using its resources effectively and not idle because one device is tied up. Figure 1 and 2 show the high level view of the SOS structure including the cloverleaf

method handling I/O port and execution unit routing.

Figure 1.

Figure 2.

1

[This page contains 1 picture or other non-text object]

Page 2 of 6

Figure 3 shows how the packets are structured. Each packet has a unique ID for the

packet as well as the OS ID. Loop count is introduced to keep track of how many

iterations it has been in the cloverleaf for priority setting. Figure 3.

2

[This page contains 1 picture or other non-text object]

Page 3 of 6

Figure 4 shows how the packets are being routed in the cloverleaf. Figure 4.

3

[This page contains 1 picture or other non-text object]

Page 4 of 6

Figure 5 shows how packets are managed in the case of a collision. Figure 5.

4

[This page contains 1 picture or other non-text object]

Page 5 of 6

Figure 6 shows a timeline table to demostrate packet handling. Figure 6....