CSE 123 Study Guide - Fall 2018, Comprehensive Midterm Notes - Transmission Control Protocol, Memory Bandwidth, Master Sergeant
12 Oct 2018
School
Department
Course
Professor
CSE 123
MIDTERM EXAM
STUDY GUIDE
Fall 2018
This Class in One Slide
1. Protocols & Layering
- decomposing tasks
- standardizing syntax & semantics
2. Naming
- agree on how to describe a host, application, network, etc.
3. Switching & Routing
- deciding how to get from here to there
- forward messages across multiple physical components
4. Resource Allocation
- sharing finite bandwidth, memory, etc.
find more resources at oneclass.com
find more resources at oneclass.com
P1 due 6pm Oct, 29th (right before Midterm!)
OH: Mon 10:30am - 12pm
End-to-End Argument - functionality should be implemented at a LOWER layer iff it can be
correctly and completely implemented there
- performance optimizations are NOT a violation
Sliding Window Protocol - single mechanism that supports:
- multiple outstanding packets
- reliable delivery
- in-order delivery
- flow control - prevent “overrunning” the receiver
Often used in the Data Link layer (2)
Project 1
struct Frame_t //packets
struct Sender_t //add more fields to implement SWP
- can add your own global variables!
Main.c - handle command line options and initializing data structures
Communicate.c - transporting messages between the sender and receiver threads
Input.c - handling messages inputted by the user
- These first three files you DO NOT NEED TO CHANGE
Common.h - houses commonly used data structures
SWP between threads
- spawn an input thread to receive your input command
- puts input command into a “input cmd queue”
- for Sender, you just read the command
- also needs to HANDLE the incoming msg from the Receiver in order to update your DS
- construct your own frame
- put to the output queue (automatically sends to receiver)
- create an acknowledgement frame and SEND it back to the Sender
Ex: ./tritontalk -s 1 -r 2
- initializes 1 sender and 2 receivers
msg 0 1 hello
- sender 0 messages receiver 1 “hello”
- 1 on 1 relationship!
HW
Bit Stuffing - how do we identify each frame?
find more resources at oneclass.com
find more resources at oneclass.com
Document Summary
This class in one slide: protocols & layering. Agree on how to describe a host, application, network, etc: switching & routing. Deciding how to get from here to there. Forward messages across multiple physical components: resource allocation. P1 due 6pm oct, 29th (right before midterm!) End-to-end argument - functionality should be implemented at a lower layer iff it can be correctly and completely implemented there. Sliding window protocol - single mechanism that supports: Flow control - prevent overrunning the receiver. Often used in the data link layer (2) Main. c - handle command line options and initializing data structures. Communicate. c - transporting messages between the sender and receiver threads. Input. c - handling messages inputted by the user. These first three files you do not need to change. Spawn an input thread to receive your input command. Puts input command into a input cmd queue . For sender, you just read the command.
