Robust I/O package Chapter 11 practice problems

Slides:



Advertisements
Similar presentations
1. I/O. I/O Unix I/O RIO (robust I/O) package Metadata, sharing, and redirection Standard I/O Conclusions and examples.
Advertisements

Carnegie Mellon 1 System-Level I/O : Introduction to Computer Systems 14 th Lecture, Oct. 12, 2010 Instructors: Randy Bryant and Dave O’Hallaron.
System-Level I/O November 4, 2003 Topics Unix I/O Robust reading and writing Reading file metadata Sharing files I/O redirection Standard I/O “The.
System-Level I/O Topics Unix I/O Robust reading and writing Reading file metadata Sharing files I/O redirection Standard I/O.
System-Level I/O October 8, 2008 Topics Unix I/O Robust reading and writing Reading file metadata Sharing files I/O redirection Standard I/O class14.ppt.
Rings This chapter demonstrates how processes can be formed into a ring using pipes for communication purposes.
System-Level I/O May 28, 2008 Topics Unix I/O Robust reading and writing Reading file metadata Sharing files I/O redirection Standard I/O.
System-Level I/O November 11, 2004 Topics Unix I/O Robust reading and writing Reading file metadata Sharing files I/O redirection Standard I/O “The.
System-Level I/O Nov 14, 2002 Topics Unix I/O Robust reading and writing Reading file metadata Sharing files I/O redirection Standard I/O class24.ppt
System-Level I/O Topics Unix I/O Robust reading and writing Reading file metadata Sharing files I/O redirection Standard I/O.
I/O April 16, 2002 Topics Files Unix I/O Standard I/O Reading: (Beta) or (New) Problems: 12.9 (Beta) or 12.4 (New) class24.ppt
System-Level I/O May 22, 2006 Topics Unix I/O Robust reading and writing Reading file metadata Sharing files I/O redirection Standard I/O.
Recitation 11: I/O Problems Andrew Faulring Section A 18 November 2002.
Introduction to Operating Systems File I/O Most of the following slides are adapted from slides of Gregory Kesden and Markus Püschel of Carnegie Mellon.
System-level I/O Alan L. Cox Some slides adapted from CMU slides.
Shell (Part 1). Process r A process is an instance of an application running r If there are two instances of an application running then there are two.
Input and Output Topics I/O hardware Unix file abstraction Robust I/O File sharing io.ppt CS 105 “Tour of the Black Holes of Computing”
System-Level I/O Topics Unix I/O Robust reading and writing
Carnegie Mellon 1 System-Level I/O / : Introduction to Computer Systems 15 th Lecture, Oct. 18, 2012 Instructors: Dave O’Hallaron, Greg Ganger,
Recitation 9: Error Handling, I/O, Man Andrew Faulring Section A 4 November 2002.
Shell (Part 2). Example r What if we want to support something like this: m ps –le | sort r One process should execute ps –le and another should execute.
Recitation 11: 11/18/02 Outline Robust I/O Chapter 11 Practice Problems Annie Luo Office Hours: Thursday 6:00 – 7:00 Wean.
Pipes A pipe is a simple, synchronized way of passing information between processes A pipe is a special file/buffer that stores a limited amount of data.
CS252: Systems Programming Ninghui Li Based on Slides by Prof. Gustavo Rodriguez-Rivera Topic 8: Opening Files and Starting Processes.
Carnegie Mellon 1 System-Level I/O / : Introduction to Computer Systems 15 th Lecture, Oct. 16, 2014 Instructors: Greg Ganger, Greg Kesden,
Shell (Addendum). Example r What if we want to support something like this: m ps –le | sort r One process should execute ps –le and another should execute.
Carnegie Mellon 1 System-Level I/O / : Introduction to Computer Systems 15 th Lecture, June 25, 2013 Instructors: Gregory Kesden.
1 IT 252 Computer Organization and Architecture Interaction Between Systems: File Sharing R. Helps.
System-Level I/O March 25, 2004 Topics Unix I/O Robust reading and writing Reading file metadata Sharing files I/O redirection Standard I/O “The.
Lee CSCE 312 TAMU 1 System Level I/O Instructor: Dr. Hyunyoung Lee Based on slides provided by Randy Bryant and Dave O’Hallaron.
Input and Output Topics I/O hardware Unix file abstraction Robust I/O File sharing CS 105 “Tour of the Black Holes of Computing”
System-Level I/O.
Recitation 11 (Nov. 22) Outline Lab 6: interposition test Error handling I/O practice problem Reminders Lab 6: Due Tuesday Minglong Shao
Input and Output Topics I/O hardware Unix file abstraction Robust I/O File sharing CS 105 “Tour of the Black Holes of Computing”
Recitation: Signaling S04, Recitation, Section A Debug Multiple Processes using GDB Debug Multiple Processes using GDB Dup2 Dup2 Signaling Signaling.
CS 105 “Tour of the Black Holes of Computing”
Recitation 9: Error Handling, I/O, Man Anubhav Gupta Section D.
1 System-Level I/O. 2 Outline Unix I/O Reading File Metadata Sharing Files & I/O redirection Robust I/O Standard I/O Suggested Reading –10.1~10.3, 10.5~10.7,
File I/O open close lseek read and write – unbuffered I/O dup and dup2.
Recitation 9: 11/04/02 Outline Error Handling I/O Linux man pages Annie Luo Office Hours: Thursday 6:00 – 7:00 Wean 8402.
Carnegie Mellon 1 Bryant and O’Hallaron, Computer Systems: A Programmer’s Perspective, Third Edition System-Level I/O : Introduction to Computer.
Carnegie Mellon /18-243: Introduction to Computer Systems Instructors: Bill Nace and Gregory Kesden (c) All Rights Reserved. All work.
System-Level I/O Topics Unix I/O Robust reading and writing Reading file metadata Sharing files I/O redirection Standard I/O.
Carnegie Mellon 1 System-Level I/O / : Introduction to Computer Systems 15 th Lecture, June 24, 2014 Instructors: Gregory Kesden.
Error handling I/O Man pages
Week 3 Redirection, Pipes, and Background
CS 3305A Process – Part II Lecture 4 Sept 20, 2017.
System-Level I/O.
System-Level I/O : Introduction to Computer Systems
Introduction to Operating Systems File I/O
Extending echo server HTTP Broken pipe error Feedback and evaluation
Files CMSC 15400: Introduction to Computer Systems Chapter 10
CS 105 “Tour of the Black Holes of Computing”
System-Level I/O Topics Unix I/O Robust reading and writing
Pipes A pipe provides a one-way flow of data example: who | sort| lpr
System-Level I/O October 9, 2008
Unix Directories unix etc home pro dev motd snt unix ... slide1 slide2
Programming Assignment # 2 – Supplementary Discussion
Virtual Memory CSCI 380: Operating Systems Lecture #7 -- Review and Lab Suggestions William Killian.
File I/O (1) Prof. Ikjun Yeom TA – Mugyo
Reference: Advanced Programming in the UNIX Environment, Third Edition, W. Richard Stevens and Stephen A. Rago, Addison-Wesley Professional Computing Series,
IPC Prof. Ikjun Yeom TA – Hoyoun
System-Level I/O.
CSCI 380: Operating Systems William Killian
CS 105 “Tour of the Black Holes of Computing”
Instructors: David Trammell
File I/O & UNIX System Interface
Low-Level I/O – the POSIX Layer CSE 333 Winter 2019
Unix Directories unix etc home pro dev motd snt unix ... slide1 slide2
Presentation transcript:

Robust I/O package Chapter 11 practice problems 15213 Recitation Section C Shimin Chen Nov. 18, 2002 Outline Robust I/O package Chapter 11 practice problems

Important Dates Lab 6 Malloc: due on Thursday, Nov 21 Lab 7 Proxy: due on Thursday, Dec 5 Final Exam: Tuesday, Dec 17

Robust I/O: RIO csapp.c and csapp.h Why? Two parts: Handles interrupted system calls Handles short counts Good for network programming Two parts: Unbuffered I/O Buffered I/O

Rio: Unbuffered Input/Output Use Unix I/O No internal buffering Useful for reading/writing binary data to/from networks ssize_t rio_readn(int fd, void* usrbuf, size_t n) reads n bytes from fd and put into usrbuf only returns short count on EOF ssize_t rio_writen(int fd, void* usrbuf, size_t n) writes n bytes from usrbuf to fd never returns short count

RIO: Buffered Input Internal buffers #define RIO_BUFSIZE 8192 typedef struct { int rio_fd; int rio_cnt; char *rio_bufptr; char rio_buf[RIO_BUFSIZE]; } rio_t; void rio_readinitb(rio_t* rp, int fd); ssize_t rio_readlineb(rio_t* rp, void* usrbuf, size_t maxlen); ssize_t rio_readnb(rio_t* rp, void* usrbuf, size_t n);

Rio: Buffered Input void rio_readinitb(rio_t* rp, int fd); called only once per open descriptor associate fd with a read buffer rio_t structure pointed to by rp ssize_t rio_readlineb(rio_t* rp, void* usrbuf, size_t maxlen); for reading text lines read a line (until ‘\n’) or maxlen-1 chars from file rp to usrbuf terminate the text line with null (zero) character returns number of chars read ssize_t rio_readnb(rio_t* rp, void* usrbuf, size_t n); reads n bytes from rp into usrbuf Result string is NOT null-terminated! Returns number of bytes read

rio_readlineb ssize_t rio_readlineb(rio_t *rp, void *usrbuf, size_t maxlen) { int n, rc; char c, *bufp = usrbuf; for (n = 1; n < maxlen; n++) { if ((rc = rio_read(rp, &c, 1)) == 1) { *bufp++ = c; if (c == '\n') break; } else if (rc == 0) { if (n == 1) return 0; /* EOF, no data read */ else break; /* EOF, some data was read */ return -1; /* error */ *bufp = 0; return n;

Interleaving RIO Read Functions Do not interleave calls on the same fd between the buffered and unbuffered functions Within each set it is ok Why? buffered unbuffered rio_readinitb rio_readlineb rio_readnb rio_readn rio_writen

Rio Error Checking RIO functions handle Short counts interrupted system calls All functions have upper case equivalents Rio_readn, Rio_writen, Rio_readlineb, Rio_readnb,etc. call unix_error if the function encounters an error But EPIPE errors! for Lab 7, EPIPE should not terminate the process

Problems from Chapter 11 11.1 ~ 11.5

Problem 11.1 What is the output of the following program? #include "csapp.h" int main() { int fd1, fd2; fd1 = Open("foo.txt", O_RDONLY, 0); Close(fd1); fd2 = Open("baz.txt", O_RDONLY, 0); printf("fd2 = %d\n", fd2); exit(0); }

Answer to 11.1 stdin (descriptor 0) stdout (descriptor 1) stderr (descriptor 2) open always returns lowest unopened descriptor First open returns 3. close frees it. So second open also returns 3. Program prints: "fd2 = 3"

File Sharing Descriptor table File Table V-node table Each process has its own Child inherits from parents File Table set of all open files Shared by all processes Reference count of number of file descriptors pointing to each entry File position V-node table Contains information in the stat structure

Problem 11.2 Suppose that foobar.txt consists of the 6 ASCII characters "foobar". Then what is the output of the following program? #include "csapp.h" int main() { int fd1, fd2; char c; fd1 = Open("foobar.txt", O_RDONLY, 0); fd2 = Open("foobar.txt", O_RDONLY, 0); Read(fd1, &c, 1); Read(fd2, &c, 1); printf("c = %c\n", c); exit(0); }

Answer to 11.2 The descriptors fd1 and fd2 each have their own open file table entry, so each descriptor has its own file position for foobar.txt. Thus, the read from fd2 reads the first byte of foobar.txt, and the output is c = f and not c = o as you might have thought initially. Draw diagram on board

Problem 11.3 As before, suppose foobar.txt consists of 6 ASCII characters "foobar". Then what is the output of the following program? #include "csapp.h" int main() { int fd; char c; fd = Open("foobar.txt", O_RDONLY, 0); if(Fork() == 0) {Read(fd, &c, 1); exit(0);} Wait(NULL); Read(fd, &c, 1); printf("c = %c\n", c); exit(0); }

Answer to 11.3 Child inherit’s the parent’s descriptor table. So child and parent share an open file table entry (refcount = 2). Hence they share a file position. c = o

Problem 11.4 How would you use dup2 to redirect standard input to descriptor 5? int dup2(int oldfd, int newfd); copies descriptor table entry oldfd to descriptor table entry newfd

Answer to 11.4 dup2(5,0); or dup2(5,STDIN_FILENO);

Problem 11.5 Assuming that foobar.txt consists of 6 ASCII characters “foobar”. Then what is the output of the following program? #include "csapp.h" int main() { int fd1, fd2; char c; fd1 = Open("foobar.txt", O_RDONLY, 0); fd2 = Open("foobar.txt", O_RDONLY, 0); Read(fd2, &c, 1); Dup2(fd2, fd1); Read(fd1, &c, 1); printf("c = %c\n", c); exit(0); }

Answer to 11.5 We are redirecting fd1 to fd2. (fd1 now points to the same open file table entry as fd2). So the second Read uses the file position offset of fd2. c = o