Lions本読書会合宿成果発表
Upcoming SlideShare
Loading in...5
×
 

Lions本読書会合宿成果発表

on

  • 927 views

 

Statistics

Views

Total Views
927
Views on SlideShare
927
Embed Views
0

Actions

Likes
1
Downloads
2
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Lions本読書会合宿成果発表 Lions本読書会合宿成果発表 Presentation Transcript

  • @oracchaLions’ Commentary on UNIX 2011 2011 10 16
  • •1 •2 10:30 Prezi • ←http://prezi.com/zm2fff4l-ia1/data-structure-of-the-unix-v6/
  • user file descriptor table file table inode table 0 file[100] inode[100] fd -> inode am^/etc/passwd) count D j Read u_ofile[15] „ k 0011111 «J , inode -> Disk4.2 STRUCTURE OF A REGULAR FILE 69 j Rd-Wrf ^ (local) f_inode Data Inode Blocks direct „ (buffers[]) 1 i count 1 1 i Write direct Figure 5.3. Data Structures after Open i_addr[8] fdl - open("/etc/passwd", OJRDONLY); fd2 - open ("local", 0_RDWR); 28 Process -> memory INTRODUCTION TO THE KERNEL direct , fd3 - open ("/etc/passwd", OJWRONLY); per process Figure 5.3 shows the relationship between the inode table, file table, and user file direct descriptor data structures. Bach open returns a file descriptor to the process, and the corresponding entry in the user file descriptor table points to a unique entry in direct, direct programmers to encode only two parameters. u_procp does not check the third parameter unless the second parameter indicates that it must, allowing proc[50] 8 direct, single indirect p_addr? double indirect coremap[100]? triple indirect Figure 4.6. Direct and Indirect Blocks in Inode
  • User ProgramUser level trap Libraries (libc) System call interface Process File system IPC control subsystem Buffer cache Scheduler char block Memory Device drivers mng.Kernel level Hardware controlHardware level Hardware Bach
  • User ProgramUser level trap Libraries (libc) System call interface Section 1 ( ) Process File system IPC control subsystem Buffer cache Scheduler char block Memory Device drivers mng.Kernel level Hardware controlHardware level Hardware Bach
  • User Program Section 2User level trap Libraries (libc) System call interface Process File system IPC control subsystem Buffer cache Scheduler char block Memory Device drivers mng.Kernel level Hardware controlHardware level Hardware Bach
  • User ProgramUser level trap Libraries (libc) System call interface Process File system IPC control Section 3 subsystem Buffer cache Scheduler char block Memory Device drivers mng.Kernel level Hardware controlHardware level Hardware Bach
  • User ProgramUser level trap Libraries (libc) System call interface Section 4 Process File system IPC control subsystem Buffer cache Scheduler char block Memory Device drivers mng.Kernel level Hardware controlHardware level Hardware Bach
  • User ProgramUser level trap Libraries (libc) System call interface Process File system IPC control Section 5 subsystem Buffer cache Scheduler char block Memory Device drivers mng.Kernel level Hardware controlHardware level Hardware Bach
  • 162 THE STRUCTURE OF PROCESSESFigure 6.1. Process State Transition Diagram
  • 3.44720 512 514