CST 334 Week 7

This week in CST 334, I got to learn a lot about how operating systems handle persistence and manage storage devices. The Hardware Interface of a Canonical Device and the Simple Device Model helped me see how the OS talks to hardware using registers like status, command, and data. I also found the I/O Architecture really interesting, especially how buses connect the CPU, memory, and other devices to make everything work together. Understanding how the OS reads and writes to registers, whether through explicit I/O instructions or memory-mapped I/O, made it clear how these interactions are happening. 

One thing that stood out was Direct Memory Access (DMA), which takes over data transfers from the CPU to speed things up. I also learned about polling, where the OS checks a device’s status repeatedly, and how that compares to interrupts. On the storage side, the concept of File System Abstraction was really helpful in showing how the OS organizes and accesses data on disk drives. Overall, it gave me a much clearer picture of how everything works under the hood to keep data safe and accessible.

Comments

Post a Comment

Popular posts from this blog

CST 462S - Learning Journal (service learning)

Working with the American Technology Initiative was really fun, informative, and rewarding. I spent most of my time on their volunteer portal, a prototype level app that makes volunteer reporting way easier. The codebase was almost release ready, so I got to dive in, explore its parts, and see how a familiar tech stack scales up for real users. Since the core features were already in place, I focused on user testing: hunting bugs, suggesting little tweaks, and polishing usability. Even though these were small changes, it felt great knowing they’d make a real difference for volunteers. If there’s one thing I’d change, it’d be the length of the service learning project. 25 hours (over eight weeks) barely gives you time to get comfortable with a new codebase. From my experience, you need at least forty hours just to learn the ropes and even more to add substantial features. I’d love to see future SL programs run at least 120 hours (about six months) so you can really dig in. The highlight...
Read more

CST 300 Week 7

Part 1: Arranging our ultimate research video project was a great experience for us as a team. The entire process was smooth, we all agreed with the concepts that were brought forth and maintained a steady vision during the planning phase. We collaborated mostly during our weekly zoom meetings. With different operating systems, we had to use various tools such as iMovie, powerpoint and Final Cut Pro (which is what I used). Looking back on it now though, what I would suggest is having timelines that allow us to finish the project at least a week early so that we can then look at it and try to improve it. However, our team has a strong bond so sharing each other’s ideas into our projects was easy for us. Part 2: I viewed Lera Boroditsky’s TED Talk “How Language Shapes the Way We Think.” The speaker discusses how much influence languages have on our thoughts and perceptions. She gives examples of different ways in which languages can shape reality, affecting even such basic phenomena as s...
Read more