• Aucun résultat trouvé

)(EI~.OX

N/A
N/A
Protected

Academic year: 2022

Partager ")(EI~.OX "

Copied!
3
0
0

Texte intégral

(1)

To: W. C. Lynch From: H. C. Laucr

Subject: Progress report: Pilot

)(EI~.OX

IlUSINESS SYSTEiVIS Systems Developmellt Departmellt

Date: February 22. 1979

Org: SOD Systems Softwarc

Filed: [I ris]<Latlcr)rebl1lary79.progress

Reference: Pilot (Teak) Developmellt Schedule (version 2), memo of Febl1l:lry ] 5, 1979 from H. Lauer.

Tasksforl'ilut 3.0 and beyond (VersionS). memo of January 25, 1979 from H. Lauer.

Pilot and Teak

Planning

The memo Tasks/or Pilot 3.0 lIlid beyond (Version 8) was circulated on January 25 defining the task list and priorities fbr the Teak release of Pilot. No substantial changes are cxpected to be made to this list.

The memo Pilot (Teak) De l'rlOIJII 1 ell I Sclirdulc (l'ersioll 2) dated Fehruary 15 is the current work plan and schedule for the development of Pilot J.O. This itemizes the detailed tasks for the five major milestones reflecting internal releases of Pilot.

Progress

Pilot A, originally scheduled Ihr February 15, was not released Oil time. This is primarily due to

the Jack of microcode and .1 DO with which to begin the development of Pilot B. Development is therefore continuing on Pilot A-including several tasks scheduled «)r later versiolls of Pilot, a large Humber of CR's. and some miscellaneous performance improvements-unlil il is feasible lo convert to Mesa 5.0 and begin Pilot B development Pilot A is now likely to be released during the week of February 26. In addition, the ft)lIowing tasks originally scheduled ror Pilot A will bc deferred:

Free Storage Package

Driver for Display/Keyboard/Mouse, implementing a permanent Mesa interface for these on the IUTFP and Dallas display.

An eSlimate ror the complelion of Pilot B, baseu on the best estimates (tH· microcode and DO availability, will he made during the Pilot group meeting 011 February 2(1. The principle items upon which we depend are: (I) A Ito compatihle Mesa 5 microcode for the DO; {2} a DO in building )J which is availahk full-lime n)r lhl~ Pilot group and capahle of running Mesa 5: and (3) Microcode J.O (as defined in the Pilof ('/'('ok) /)cl'eloplJI('1I1 .)'('/ict/uld slipPOrling the t\·1l~sa process facilities and soil ware hooting.

(2)

Progress report: Pilot 2

Technical

TIle new rigid disk driver includes several meters and counters which have provided substantial insight into Pilot's performance in handling page faults. These and subsequent measurements indicate that the compute time per page is several times longer than the disk transfer time per sector. This performance bug is being aggressively pursued.

Several known performance bugs reported previously have been corrected, including those in the real memory allocator and in Space.Create.

Common Software

Peter Bishop has joined the Pilot group on loan for the purpose of implementing the transaction file package- specified in his Transactioll, Virtual 1\1 e11101), Sharing. and Locking FUllctional Specification of January 23. The ground 11I1e of this implementation is that it support the Star File System and that it be done within the time scale of Teak.

Peter has made available a 'facade' ""hieh itnplements the interface of his FUllctional Specification without actually implementing the substance of this system. This allows clients to develop software whieh uses this interface while the actual common software package is under development.

Staffing mHI :EquiIllllcnt

Bob Ladner will report on rvIarch 1 to become the common software coordinator.

The Pilot group is still short by one person. Several good candidates have been interviewed and an offer is expected to be made SOOl1. l-.fowevcr, I do not expect that a new person can come on board and get liP to speed soon enough to contribute to Teak in any significant way.

As a result of the Pilot group assuming partial responsibility for utilities, an offer is being made to a person to implement these.

Altos will be needed for all new people.

Other

H. C. Lauer and E. H. Satterthwaite have completed a paper entitled The Impact of ,.lesa 011 System Design. This has been suhmilled to the Fourth International Conference on Soilwtlre Engineering to be held in Munich in September.

T. Horsley and W. Lynch have (nearly) completed a paper entitled PiI(H: A Sojiware Ellgineering Case .)'tlldy. This will be submitted to the same conference.

IsslIes

It is becoming apparent that the arc a lot of different ideas about what kind of support is required for the I )isplay, Keyboard, and MOllse. It is also apparent that no one has a clear, coherent pietlt"re of what f~lcililies mllst be provided in microcode, Pilot. antl client-level software. I propose that"

User Terminal \Vorking Group be convened to resolve these isstles. Until stich a working group provides a report, I do not believe that it witl be possible to assign implementation responsibilities in slIch a way that everyone has confidence that the right thing is being done.

In the interim, the Pilot group wilt defIne a Mesa interface for the Display, Keyboard. and MOllse which rellects the style .1Ilt! general character or the U'('VFC and UTLF. These will be implemented on the I UTI''!' and Dallas I )isplay in order to support the Debugger, test programs, etc.

(3)

Progrcss rClwrt: Pilot . 3

Assignmcnts

Bishop-implcmcnt the Transaction/VM Sharing package.

Redell-complcLe I.ogical volume support, implcmented PrincOps process llwchinery for Pilot B.

serve 011 Architccture Board

tvIc.Jones-provicic Nlesa-Ievcl support for software booting, convert Pilot to Pilot

n

Horsley-reconfigure Pilot for Pilot kit, release Pilot A, come up to speed on managing microcode

releases .

Gobbel-jmplement interim Display, Keyboard, and ivlouse drivcr for IUTFP, convert DeS to usc it

L1dncr-comc up to speed

L1uel'-attencl lvlanagement Action Workshop, make Technical Rcview Presentation, present Duality paper at Louisiana Computer Confcrence, manage Pilut implementation

In addition, we are counting on the following assistance in implemcnting Pilot

n

and converting the DO to something more closely rcsembling the architecture defined by the Processor Prillciples of Operation:

Pitts Jm'vis to update microcoded device controllers to move the magic memory locations to the PriJlcOps 110 page.

Rich Johnssoll and/or Jim Sandman to make the debugger track conversion to PrillcOps architecture.

Dick Snow and/or Rich .Tohnsson to convert process microcode to PrincOps data structures.

c: n. Redell. P. I\kJollcs. T. Horsley, R. Gobbet, P. Bishop

Références

Documents relatifs

The signalling exchanges and local information passed between MARS entity and NBMA signalling entity with these functions are outside the scope of this document..

The description of command syntax provided by the fields can be used by mail client applications to provide simplified and consistent user access to email distribution

attribute, matching rule, matching rule use and syntax referenced in a value of ldapSchemas MUST either be defined in one of the schemas referenced in the &#34;IMPORTS&#34;

Client and application implementers must consider that the existence of a given value in the vendorName or vendorVersion attribute is no guarantee that the server was

subarea1 cannot get its zone keys properly signed as its parent zone, region1, is not secured.. The colloquial phrase describing the collection of contiguous secured zones at

identifier of the registrar that performed the last update, the date and time of last completed transfer (if any), the current status of the domain, authorization

The IRON uses the existing IPv4 and IPv6 global Internet routing systems as virtual NBMA links for tunneling inner network protocol packets within outer IPv4 or IPv6

In contrast, emerging IPv6-capable home networks are very likely to have multiple internal subnets, e.g., to facilitate private and guest networks, heterogeneous link layers,