Copy-on-write technique in Operating Systems - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the Copy-on-write (COW) technique?

Copy-on-write is a memory management technique where multiple processes share the same resource (like memory) until one process modifies it. At that point, a copy is made for the modifying process, avoiding unnecessary duplication.

beginner

Why is Copy-on-write useful in operating systems?

It saves memory and improves performance by delaying copying until it is necessary, such as when a process writes to shared data.

intermediate

How does Copy-on-write work during process creation?

When a new process is created (like with fork), it shares the parent's memory pages marked as read-only. Only when the child or parent writes to a page, a copy is made for that process.

intermediate

What happens if a process tries to write to a shared page in Copy-on-write?

The operating system detects the write attempt on a read-only shared page, creates a private copy of that page for the writing process, and then allows the write.

advanced

Name a common use case of Copy-on-write outside process memory management.

Copy-on-write is also used in file systems and data structures to efficiently manage copies without duplicating data until changes occur.

What triggers the actual copying of data in Copy-on-write?

A When a process writes to the shared data

B When the data is deleted

C When the system boots

D When a process reads the data

Copying happens only when a process writes to the shared data, not when it reads.

During a fork, how does Copy-on-write help?

A It duplicates all memory immediately

B It deletes the parent's memory

C It shares memory pages until a write occurs

D It prevents the child from accessing memory

Copy-on-write allows the child and parent to share memory pages until one writes, saving memory.

What kind of page is used to mark shared memory in Copy-on-write?

A Read-only page

B Writable page

C Executable page

D Hidden page

Shared pages are marked read-only to detect writes and trigger copying.

Which of these is NOT a benefit of Copy-on-write?

A Improved performance

B Immediate data duplication

C Memory savings

D Reduced unnecessary copying

Copy-on-write delays copying; immediate duplication is not a benefit.

Copy-on-write is commonly used in which of the following?

A Process memory management

B File systems

C Data structures

D All of the above

Copy-on-write is used in process memory, file systems, and data structures to optimize resource use.

Explain how Copy-on-write works when a process tries to modify shared memory.

Think about what happens when a process writes to memory shared with another.

Describe the advantages of using Copy-on-write in operating systems.

Consider why delaying copying can be helpful.

Practice

1. What is the main idea behind the copy-on-write technique in operating systems?

easy

A. Data is copied only when it is modified, not when initially shared

B. Data is copied immediately when a process is created

C. Data is never copied, only referenced

D. Data is copied multiple times to improve speed

Solution

1. Step 1: Understand the purpose of copy-on-write

   Copy-on-write delays copying data until a modification is made, saving resources.

2. Step 2: Compare options with the concept

   Only Data is copied only when it is modified, not when initially shared correctly states that copying happens only on modification, not immediately.

3. Final Answer:

   Data is copied only when it is modified, not when initially shared -> Option A

4. Quick Check:

   Copy-on-write = Copy on modification [OK]

Hint: Copy happens only when data changes, not before [OK]

Common Mistakes:

• Thinking data copies immediately on sharing
• Believing data is never copied
• Assuming multiple copies improve speed

2. Which of the following best describes when a copy is made in a copy-on-write system?

easy

A. When the original data is read

B. When the data is modified

C. When the system boots

D. When the data is deleted

Solution

1. Step 1: Identify the trigger for copying in copy-on-write

   Copy-on-write means copying happens only when data is changed or written to.

2. Step 2: Match the correct event

   Only When the data is modified correctly states copying occurs on modification.

3. Final Answer:

   When the data is modified -> Option B

4. Quick Check:

   Copy-on-write triggers on modification [OK]

Hint: Copy only on write, not on read [OK]

Common Mistakes:

• Confusing read with write triggers
• Thinking copy happens at system start
• Assuming copy on deletion

3. Consider a process creation using copy-on-write. If the parent process has 100MB of memory, and the child process is created but does not modify any data, how much memory is used by both processes together?

medium

A. 0MB

B. 200MB

C. 50MB

D. 100MB

Solution

1. Step 1: Understand memory sharing in copy-on-write

   Initially, both processes share the same memory pages without copying.

2. Step 2: Calculate total memory usage

   Since no modifications occur, memory is shared, so total used is 100MB, not doubled.

3. Final Answer:

   100MB -> Option D

4. Quick Check:

   Shared memory means total = original size [OK]

Hint: No changes mean no extra memory used [OK]

Common Mistakes:

• Assuming memory doubles immediately
• Thinking child process uses zero memory
• Confusing copy-on-write with full copy

4. A system uses copy-on-write for file snapshots. A snapshot is taken, but later the original file is modified. What is the likely error if the snapshot also changes unexpectedly?

medium

A. Copy-on-write was not properly implemented, causing shared data to change

B. Snapshot was created after modification

C. The file system does not support snapshots

D. The snapshot was deleted accidentally

Solution

1. Step 1: Analyze snapshot behavior with copy-on-write

   Snapshots should remain unchanged because copy-on-write protects original data by copying on modification.

2. Step 2: Identify cause of snapshot changing

   If snapshot changes, it means copy-on-write failed and data was shared incorrectly.

3. Final Answer:

   Copy-on-write was not properly implemented, causing shared data to change -> Option A

4. Quick Check:

   Snapshot changes mean copy-on-write failure [OK]

Hint: Snapshot changes mean copy-on-write error [OK]

Common Mistakes:

• Assuming snapshot created after modification
• Blaming unsupported file system without evidence
• Confusing deletion with modification

5. In a system using copy-on-write, a parent process forks a child. The child modifies a small 1MB part of a 500MB memory space. How much additional memory is used after the modification?

hard

A. 500MB

B. 501MB

C. 1MB

D. 0MB

Solution

1. Step 1: Understand copy-on-write memory allocation on modification

   Only the modified part is copied, so only 1MB is newly allocated.

2. Step 2: Calculate total additional memory used

   The rest of the 499MB remains shared, so additional memory is exactly 1MB.

3. Final Answer:

   1MB -> Option C

4. Quick Check:

   Copy-on-write copies only changed data [OK]

Hint: Only changed data uses extra memory [OK]

Common Mistakes:

• Assuming entire memory is copied
• Adding modified size to total incorrectly
• Thinking no memory is used on modification