Segmentation in Operating Systems - Step-by-Step Execution

Concept Flow - Segmentation

Program divided into segments

↓

Each segment has a base address and length

↓

Segment table stores base and length for each segment

↓

CPU uses segment number and offset to access memory

↓

Check if offset < segment length?

No→Error: Invalid memory access

Yes↓

Physical address = base + offset

↓

Access memory at physical address

Segmentation divides a program into logical parts called segments, each with its own base address and length, allowing memory access by segment number and offset.

Execution Sample

Operating Systems

Segment Table:
0: base=1000, length=500
1: base=2000, length=300
Access: segment=0, offset=450

This example shows accessing memory at segment 0 with offset 450 using the segment table.

Analysis Table

Step	Segment Number	Offset	Check Offset < Length	Physical Address Calculation	Result
1	0	450	450 < 500 = True	1000 + 450 = 1450	Access memory at 1450
2	1	350	350 < 300 = False	N/A	Error: Invalid memory access

💡 Step 2 stops because offset 350 is not less than segment length 300, causing an invalid access error.

State Tracker

Variable	Start	After Step 1	After Step 2
Segment Number	N/A	0	1
Offset	N/A	450	350
Segment Length	N/A	500	300
Base Address	N/A	1000	2000
Physical Address	N/A	1450	N/A

Key Insights - 2 Insights

Why do we check if the offset is less than the segment length?

Because accessing memory beyond the segment length causes an error. As shown in execution_table step 2, offset 350 is not less than length 300, so access is invalid.

How is the physical address calculated from segment and offset?

Physical address is the sum of the segment's base address and the offset. In step 1, base 1000 plus offset 450 equals physical address 1450.

Visual Quiz - 3 Questions

Look at the execution table, what is the physical address calculated at step 1?

A 1450

B 1000

C 450

D 500

💡 Hint

Check the 'Physical Address Calculation' column in execution_table row for step 1.

At which step does the offset exceed the segment length causing an error?

A Step 1

B Step 2

C Neither step

D Both steps

💡 Hint

Look at the 'Check Offset < Length' column in execution_table to find where the condition is false.

If the offset in step 2 was 250 instead of 350, what would happen?

A Access memory at physical address 350

B Error: Invalid memory access

C Access memory at physical address 2250

D No change, still error

💡 Hint

Refer to variable_tracker for base address 2000 and compare offset 250 with segment length 300.

Concept Snapshot

Segmentation divides a program into logical segments.
Each segment has a base address and length.
Memory access uses segment number + offset.
Check offset < segment length to avoid errors.
Physical address = base + offset.

Full Transcript

Segmentation is a memory management technique where a program is split into segments like code, data, and stack. Each segment has a base address and length stored in a segment table. When accessing memory, the CPU uses a segment number and an offset. It first checks if the offset is less than the segment length to ensure valid access. If valid, the physical address is calculated by adding the base address of the segment to the offset. If the offset is too large, an error occurs. This method helps organize memory logically and protects against invalid memory access.

Practice

1. What is the main purpose of segmentation in operating systems?

easy

A. To increase the CPU clock speed

B. To divide a program's memory into logical parts like code and data

C. To compress files on the disk

D. To manage network connections

Solution

1. Step 1: Understand segmentation concept

   Segmentation divides a program's memory into meaningful parts such as code, data, and stack.

2. Step 2: Identify the main purpose

   This division helps organize and protect memory efficiently.

3. Final Answer:

   To divide a program's memory into logical parts like code and data -> Option B

4. Quick Check:

   Segmentation = dividing memory logically [OK]

Hint: Segmentation splits memory by program parts, not hardware speed [OK]

Common Mistakes:

• Confusing segmentation with CPU or disk functions
• Thinking segmentation compresses data
• Mixing segmentation with network management

2. Which of the following correctly describes a segment in segmentation?

easy

A. A logical unit like code, data, or stack with base and length

B. A network packet

C. A fixed-size block of memory

D. A CPU register

Solution

1. Step 1: Define a segment in segmentation

   A segment is a logical unit of a program such as code, data, or stack.

2. Step 2: Understand segment properties

   Each segment has a base address and length to locate it in memory.

3. Final Answer:

   A logical unit like code, data, or stack with base and length -> Option A

4. Quick Check:

   Segment = logical unit with base and length [OK]

Hint: Segments are logical parts, not fixed-size blocks [OK]

Common Mistakes:

• Thinking segments are fixed-size blocks
• Confusing segments with network or CPU terms
• Ignoring base and length properties

3. Consider a program with segments: code (base=1000, length=300), data (base=2000, length=500), stack (base=3000, length=200). What is the physical address for logical address (data segment, offset 450)?

medium

A. 450

B. 2455

C. 2450 + 2000

D. 2450

Solution

1. Step 1: Identify base and offset for data segment

   Data segment base = 2000, offset given = 450.

2. Step 2: Calculate physical address

   Physical address = base + offset = 2000 + 450 = 2450.

3. Final Answer:

   2450 -> Option D

4. Quick Check:

   Physical address = base + offset = 2450 [OK]

Hint: Add segment base to offset for physical address [OK]

Common Mistakes:

• Adding offset twice
• Using offset alone as physical address
• Confusing segment base with offset

4. A segmentation system has a segment with base address 500 and length 100. Which logical address will cause a segmentation fault?

medium

A. Segment offset 100

B. Segment offset 50

C. Segment offset 99

D. Segment offset 0

Solution

1. Step 1: Understand valid offset range

   Valid offsets are from 0 up to length-1, so 0 to 99.

2. Step 2: Identify invalid offset

   Offset 100 is outside the segment length and causes segmentation fault.

3. Final Answer:

   Segment offset 100 -> Option A

4. Quick Check:

   Offset ≥ length causes fault = 100 [OK]

Hint: Offsets must be less than segment length [OK]

Common Mistakes:

• Allowing offset equal to length
• Confusing offset with base address
• Ignoring segment length limits

5. In a segmented memory system, how does segmentation help in sharing code between processes?

hard

A. By encrypting the code segment for each process

B. By copying the entire code segment to each process's memory

C. By allowing multiple processes to use the same code segment base and length

D. By merging all segments into one large segment

Solution

1. Step 1: Understand code sharing in segmentation

   Segmentation allows processes to share segments by referencing the same base and length for code.

2. Step 2: Identify how sharing works

   Multiple processes can point to the same code segment without copying it, saving memory.

3. Final Answer:

   By allowing multiple processes to use the same code segment base and length -> Option C

4. Quick Check:

   Shared base and length enable code sharing [OK]

Hint: Sharing uses same segment base and length, no copying needed [OK]

Common Mistakes:

• Thinking code is copied for each process
• Believing segments merge for sharing
• Confusing sharing with encryption