YOUR C LEARNING COMPANION

Kahan se padhein?

Learning path
C se pehleChapter 3 of 73

CPU, memory, storage aur operating system

Ordinary computer par program run hone mein involved parts ka practical model banayein, aur usko C ke rules se alag rakhein.

5 min readFoundationsComputing concepts
Offline reading
Is chapter mein9 sections
0% through this chapter

Application kholne par computer ke kai parts saath kaam karte hain. Processor, working memory, storage aur operating system ke jobs alag samjhte hain. Example ek typical laptop ka hai; doosre C environments alag ho sakte hain.

1. Processor machine operations perform karta hai

CPU ka full form central processing unit hai. Woh arithmetic, comparison aur data move karne jaise machine instructions execute karta hai. Registers naam ki chhoti storage locations current work ki information hold karti hain. Devices aur doosre components bhi work karte hain; CPU system ka ek part hai.

CPU inherently C variable name apples ko recognize nahi karta. Language implementation source-level concepts ko target-supported operations se jodti hai. Source names debugging tools ki help kar sakte hain, lekin har named object ka permanently visible alag physical location hona language requirement nahi.

2. Working memory active computation ko support karti hai

Typical laptop mein RAM running programs ki kaafi working storage deti hai. Ordinary RAM ka data power loss par nahi bachta. Processor registers aur caches bhi use karta hai, isliye har operation ko directly RAM se read karna zaroori nahi.

Address address space mein location identify karta hai. Common operating systems virtual addresses ko resources se map karte hain. Abhi location ka idea rakhein; use universal physical RAM coordinate na samjhein. Aage pointer types, valid targets aur lifetimes ke C rules jodenge.

3. Persistent storage sessions ke beech files rakhti hai

SSD ya hard drive application close hone ke baad bhi files store rakhti hai. Inmein source code, executable programs aur saved documents ho sakte hain. Program run karne ke liye system needed code aur data available karta hai. Har related file poori ki poori ek saath RAM mein copy hona zaroori nahi.

Is difference se saving ka importance samajh aata hai. Document edit karna application ki current state badalta hai; file write karna us working state ke bahar persistence request karta hai. Buffering, failures aur durable storage mein aur care chahiye. Abhi “screen par visible hai” aur “successfully saved hai” ko same fact na samjhein.

PartPehla useful sawaal
CPU aur registersKaun-se operations execute ho rahe hain aur kaun-si immediate information par?
Working memoryRunning program ke liye abhi kaun-si information available hai?
Persistent storageFile ya persistent record ke roop mein kya stored hai?
Operating systemResources, permissions, devices aur processes ka coordination kaun karta hai?

4. Operating system access coordinate karta hai

Operating system processes, memory, files aur devices jaise facilities manage karta hai. Applications interfaces se services request karti hain, aksar libraries ke through. C output call ka text dikhne se pehle kai layers se guzar sakta hai. Woh directly display electronics ko command nahi karta.

OS isolation aur permissions mein bhi role nibhata hai. C aane se doosre process ki memory ya har device access karne ki permission automatically nahi milti. Language feature aur system privilege alag hain. File missing, access denied ya resource exhaustion se program fail ho sakta hai, chahe C syntax correct ho.

5. Program file aur process alag hain

Program file code aur related information store karti hai. Common systems par process running instance hota hai, jiske execution state aur resources hote hain. Do instances ki current values alag ho sakti hain. Running instance ki value badalne se program file automatically rewrite nahi hoti.

Desk analogy useful ho sakti hai: storage filing cabinet jaisi aur working memory desk par current material jaisi. Lekin limits important hain. Information encode hoti hai, physical sheet ki tarah move nahi; mappings, caches, shared resources aur optimizations ek literal desk jaise nahi. Analogy ke roles rakhein, har physical detail nahi.

6. C ko desktop operating system required nahi

C hosted aur freestanding execution environments distinguish karti hai. Hosted environment mein main wale familiar startup forms aur full hosted library requirements specified hain. Firmware jaise settings ki freestanding implementations mein startup aur library provisions alag hain. Laptop diagram ko har C implementation ki requirement na banayein.

Thoda sochkar dekhein

Running application mein counter badla aur successful save operation ke bina close kar diya. Kya executable file mein ab woh counter value zaroor hogi?

Explanation padhein

Nahi. Execution state aur stored program file ke roles alag hain. Persistence ke liye appropriate successful operation chahiye; working value badalne se executable automatically rewrite nahi hota.

Primary references aur aage ki reading

Aage badhne se pehle

  • Processor, working memory, storage aur operating system ke roles alag hain.
  • Running process ki state stored executable file se alag hai.
  • Working value badalne ke alawa data save karne ke liye suitable successful operation chahiye.
In ideas ko alag rakhein
Working memory / Persistent storage
Program end hone par working data ja sakta hai; persistence storage aur successful save policy par depend karti hai.
Apne words mein samjhaayein

Same program ki do running copies different current values kyun dikha sakti hain?

Optional: bolkar samjhein ya note rakhein. Tayyar hon toh aage badh sakte hain.

Apni understanding check karein

Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.

Unsaved work kyun gayab ho sakta hai, yeh kis distinction se samajh aata hai?
Har choice ki explanation padhein
  1. RAM aur persistent storage interchangeable hain.

    Working memory aur persistent storage ke roles aur persistence alag hain.

  2. Working memory aur persistent storage ke roles alag hain.

    ✓ Sahi reasoning. Save karna normally persistent storage mein data likhta hai; working memory mein value rakhna alag operation hai.

  3. CPU har intermediate value permanently save karta hai.

    Operations execute hone se har value ki persistent copy automatically nahi banti.

General

Agla idea padhne ke liye tayyar?

Mark this chapter as read whenever you feel ready.

CHAPTER 03 / 73

Is chapter mein

CPU, memory, storage aur operating system

Search all 73 chapters in both languages.EN + HG

Try “pointer”, “why int”, or “undefined behavior”.

Concepts connect. Follow your curiosity.↑ ↓ to explore · Enter to open
MAKE YOURSELF COMFORTABLE

Your reading space

Appearance

A clear canvas with balanced contrast.

Text size

100%
AA

Reading tools

Your data stays in this browser

Export a backup before changing browsers or replacing an older version of the reader.

YOUR PERSONAL MARGINS

My notebook

Saved on this device
A LITTLE CLARITY

The glossary

A starting meaning, then a chapter to go deeper.

A QUICK DEFINITION

A little clarity

Read the full explanation →

A thought worth keeping