DOC PREVIEW
MIT 6 033 - Lecture Notes

This preview shows page 1-2-3 out of 10 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 10 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 10 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 10 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 10 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

L1: Intro to Computer Systems:Controlling ComplexityFrans Kaashoek6.033 Spring 2007http://web.mit.edu/6.033Logistics: http://web.mit.edu/6.033• Schedule has all assignments• Every class meeting has preparation/assignment• First deliverable is due Tuesday 2/13.• To help you: read the Therac paper before Friday’s writing recitation.• Fill out sign up sheet and return at the end of lecture(if you didn’t do so yesterday)• We will post sections assignment tonightEmergent Property Example• Experimental Ethernet design: 3Mbit/s• All senders share single cable• Send successful when there is no collision• Must send for 2*5 µseconds = 30 bits• Header is: 5 bytes = 40 bits• First Ethernet standard: 10 Mbit/s• Must send for 2*20 µseconds = 400 bits• Header is: 14 bytes Need to pad packets to at least 50 bytes Minimum packet size!Propagation of Effects Example(C. Cole 1969)• WHO attempted to control malaria in North Borneo• Sprayed villages with DDT• Wiped mosquitos, but ….• Roaches collected DDT in tissue• Lizards ate roaches and became slower• Easy target for cats• Cats didn’t deal with DDT well and died• Forest rats moved into villages• Rats carried the bacillus for the plague WHO replaced malaria with the plagueGalileo in 1638“To illustrate briefly, I have sketched a bone whose natural length has been increased three times and whose thickness has been multiplied until, for a correspondingly large animal, it would perform the same function which the small bone performs for its small animal. From the figures here shown you can see how out of proportion the enlarged bone appears. Clearly then if one wishes to maintain in a great giant the same proportion of limb as that found in an ordinary man he must either find a harder and stronger material for making the bones, or he must admit a diminution of strength in comparison with men of medium stature; for if his height be increased inordinately he will fall and be crushed under his own weight. Whereas, if the size of a body be diminished, the strength of that body is not diminished in the same proportion; indeed the smaller the body the greater its relative strength. Thus a small dog could probably carry on his back two or three dogs of his own size; but I believe that a horse could not carry even one of his own size.”Incommensurate scaling• Scaling mouse to size of an elephant (Haldane 1928)• Volume ~ O(n3)• Bone strength ~ cross section ~ O(n2)• Scaling the Internet• IPv4 has 32 bit addresses; limited networks (216)• Network Address Translators and IPv6• Scaling Ethernet from 10Mbit/s to 1Gbit/s• Minimum packet size: 40x100Mbit/s = 4,000 bits• 100 Mbit/s: shorten the maximum cable length to 250m• 1 Gbit/s: increase minimum packet size to 512 bytes• Switched architecture: don’t share cableExample: more goals, more complexityoperating systemsMillions of lines of source code0102030405060NASAspaceshuttlectrlWindows3.1(1992)WindowsNT(1992)Solaris(1998)Windows95Windows98WindowsNT 5.0(1998)RedHatLinux 6.2(2000)RedHatLinux 7.1(2001)WindowsXPVistaExample: interacting features, more complexity• Call forwarding• Call Number Deliver blocking• Automatic callback• Itemised billingA CB??ABCNDBACB + IB• A calls B, B is busy• Once B is done, B calls A• A’s number on appears on B’s billPrinciples• Principle escalating complexity• Avoid excessive generality• Law of diminishing returns• ….. Many more to come ….Class plan• Next lecture: computer systems are different• Naming: glueing modules together• Client/server: enforced modularity• Networks: hard boundaries between modules• Reliability and transactions: handing failures• Security: handling malicious


View Full Document

MIT 6 033 - Lecture Notes

Documents in this Course
TRIPLET

TRIPLET

12 pages

End Layer

End Layer

11 pages

Quiz 1

Quiz 1

4 pages

Threads

Threads

18 pages

Quiz I

Quiz I

15 pages

Atomicity

Atomicity

10 pages

QUIZ I

QUIZ I

7 pages

Load more
Download Lecture Notes
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Lecture Notes and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Lecture Notes 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?