Project: Data Encapsulation Title: Give, as a minimum, the name of the layer you are presenting and your own name.
The layer's data unit: Give the name of the layer's data unit and include information about the header and footer (if there is one).
Diagram: Include a diagram (using squares, circles, arrows, etc.) showing the data unit and what its headers and footers do.
Encapsulation/decapsulation: Show where in the process the layer sits. List the layers that are encapsulated before your layer. List the layers that are decapsulated before your layer.
Security: List one or two security risks at your layer and how to guard against them.

It dont need to be nothin fancy lol

When making changes to optimize part of a processor, it is often the case that speeding up one type of instruction comes at the cost of slowing down something else. for example, if we put in a complicated fast floating-point unit, that takes space, and something might have to be moved farther away from the middle to accommodate it, adding an extra cycle in delay to reach that unit. the basic amdahl's law equation does not take into account this trade-off. a. if the new fast floating-point unit speeds up floating-point operations by, on average, 2ă—, and floating-point operations take 20% of the original program's execution time, what is the overall speedup (ignoring the penalty to any other instructions)? b. now assume that speeding up the floating-point unit slowed down data cache accesses, resulting in a 1.5ă— slowdown (or 2/3 speedup). data cache accesses consume 10% of the execution time. what is the overall speedup now? c. after implementing the new floating-point operations, what percentage of execution time is spent on floating-point operations? what percentage is spent on data cache accesses?