Scribd
Upload
42 views

CS87 Spring 2010 Readings 7

This document outlines the reading schedule and requirements for a distributed systems course. It includes: 1) Instructions for writing reaction notes for each assigned research paper, including summarizing key points, answering specific questions, and listing any questions. 2) Details on submitting and self-evaluating reaction notes. 3) A reading list that assigns specific papers for each weekly topic and provides related references. 4) Guidance on viewing and printing the electronic papers. The schedule is divided into weekly topics covering areas like parallel programming models, distributed systems, security, and distributed file systems.

Uploaded by

Sadiholic
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
42 views

CS87 Spring 2010 Readings 7

This document outlines the reading schedule and requirements for a distributed systems course. It includes: 1) Instructions for writing reaction notes for each assigned research paper, including summarizing key points, answering specific questions, and listing any questions. 2) Details on submitting and self-evaluating reaction notes. 3) A reading list that assigns specific papers for each weekly topic and provides related references. 4) Guidance on viewing and printing the electronic papers. The schedule is divided into weekly topics covering areas like parallel programming models, distributed systems, security, and distributed file systems.

Uploaded by

Sadiholic
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

Reading Schedule for CS87, Spring 2010

Contents:

Reaction Notes

Submitting Reaction Notes

Reading List of Papers

Reaction Notes

For most papers we read, you will write reaction notes prior to our
class meeting to help prepare you for
discussing the paper. You should bring a print out of your reaction notes and the paper to class with you.
Reaction notes can be written in ascii or Word, or latex, or
... whatever you want.

Reaction notes should should reflect your critical reading of the paper. Some questions to think about as
you read:
Did the authors do what they said they were going to do? What are the important ideas (just
because an author says something is important doesn't mean it necessarily is)? Do their results make
sense? Are their methods sound? Are there weaknesses in their solution? What assumptions are they
making? How does their work fit in with other similar work? What improvements and/or extensions to the
area do they contribute? Are there terms, ideas, techniques, that you don't understand?

some tips for reading research papers

Reaction notes should be no more than one page in length and structured in the following way:

1. Summary:
A 1 paragraph summary of the paper. A summary of what the work is, what problem(s) it
addresses, and the results or new technique (if applicable). Also, include a short list of the
strengths and weaknesses of the work, and list how it is related to other work we have read (when
applicable).

2. Answer to Specific Question(s):


A 1-2 paragraph answer to the specific question(s) associated with this paper.

You are welcome to discuss other parts of the paper in addition


to answering the specific question.
However, it is not required that
you do so.

3. A list of questions you have about this paper:


If there are terms, ideas, techniques that you don't understand, list them here. However, for terms
you don't understand,
also try to find the answer yourself by using on-line sources such as
whatis.techtarget.com.
If you find an answer, please leave the listing of the term on your
reaction notes; it is helpful to me to see which terms are new to students so that I can make sure
that we discuss their meaning.

Submitting Reaction Notes

Bring to class a printout of your reaction notes and the paper to


discuss. You will hand in your reaction
notes at the end of class.

Self-Evaluation and Summary


After each class discussion, you will complete a self-evaluation of
your participation in discussion and you
will write a 1 paragraph summary
of the class' critical evaluation of the paper as we discussed it. Here is a
sample evaluation form (it may change): discussion evaluation form

Viewing and Printing Papers

You can view most postscript files (and gziped postscript files) using gv on our system:

$ gv file.ps.gz

gv cannot handle some version of postscript, in this case you should save a copy of the paper.ps.gz file,
gunzip it, and
then either view it using gs or convert it to pdf and view it using acroread:

$ gunzip file.ps.gz

$ gs file.ps

$ ps2pdf file.ps

$ acroread file.pdf

You can print postscript using lpr, or print 2-up postscript files using mpage
and lpr:

$ lpr file.ps

$ mpage -2 -M-10 -dp file.ps | lpr

You can print double sided to TheDicer:

$ lpr -PTheDicer file.ps

$ mpage -2 -M-10 -dp file.ps | lpr -TheDicer

You can view (and print) pdf files using acroread:

$ acroread file.pdf

Reading List
In addtion to the assigned readings, there are some related paper references here: Additional Cluster
and Distributed Computing Papers

Week 5

For Friday OpenMP:

OpenMP: An Industry-Standard API for Shared-Memory Programming


by Leonardo Dagum
and Ramesh Menon, in IEEE Computational Science and Engineering, January 1998
(this may only be accessable on the Swarthmore network)

Reaction Notes Question: What is ment by data parllelism and task parallelism? What makes
pthreads
a task parallel programming model?

Week 6:

For Fri MPI

A message passing standard for MPP and workstations


J. J. Dongarra, S. W. Otto, M. Snir,
and D. Walker,
CACM, 39(7), 1996, pp. 84-90
Reaction Notes Question: What are the target systems for MPI and OpenMP? How well does each fit
for programming on a cluster of SMPs? Explain the strengths and weakness of each for such a
system.

Week 7:

Week 8:

For Monday Distributed Systems

Paper handed out in class on Friday week 6. Also available outside


my office door.

Do not do the Summary part of reaction notes for this paper. Instead answer
the Reaction Notes
Question and list any questions you have.

Reaction Notes Question: Pick one of scalability, transparency, or single-system image, and define
what it is and why it is desirable in a distributed system, and discuss some of the issues associated
with supporting it.

For Friday Map Reduce

MapReduce: simplified data processing on large clusters


by Jeffrey Dean and Sanjay
Ghemawat,
Communications of the ACM , Volume 51 Issue 1 January 2008

Reaction Notes Question: Discuss the scalability of the Map Reduce


Implementation. How well is it
designed to scale to large-sized systems and
large-sized applications? Explain/support your answer.

Week 9: Distributed Coordination, Security

For Monday: Time and Agreement

Lecture in classroom.

For Wednesday:

End-To-End Arguments in System Design


J.H. Saltzer, D.P. Reed and D.D. Clark. ACM
Transactions on Computer Systems,
4(4):277-288, November 1984

Reaction Notes Question: What is ment by an endpoint? Is there


any benefit to puting a function
not at an endpoint (in a lower-level or intermediate point)? If yes, explain what is gained by doing
so and if any guarantee about the functionality can be made by doing so. If no, explain why not.
You may want to use an example to explain your answer.

Week 10: Distributed File Systems

For Monday:

Serverless Network File Systems, Thomas E. Anderson, Michael D. Dahlin, Jeanna M. Neefe,
Drew S. Roselli, Randolph Y. Wang and David A. Patterson, EECS Department, University of
California, Berkeley, Tech. Rep. UCB/CSD-98-983, 1998.

Do not get too bogged down into the details of LFS, Zebra, cleaning, and RAID. Just try to get the
general idea. Focus mainly on sections 3 and 5.
Reaction Notes Question: How is logging used in XFS? Pick one example and explain how and why it
is used.

For Friday: Security

"The Internet Worm: Crisis and Aftermath", Eugene H. Spafford, Communications of the ACM,
32 (6): 678-687, June 1989

Reaction Notes Question: No reaction notes for this one.

Week 11: Distributed File Systems

For Monday:

The Google File System,


Sanjay Ghemawat, Howard Gobioff, Shun-Tak Leung,
Proceedings of the
nineteenth ACM symposium on Operating systems principles,
olton Landing, NY, 2003

Reaction Notes Question: In what ways did the intended use


of the file system lead to its design?
Pick one of these ways to discuss
in more details (include explaination of why the resulting design
choice
fits its intended use, and critic the design choice in terms of how well it meets its goal (and
explain why)).

Wednesday and Friday: Project Progress Report Presentations

Wednesday Friday
Janis and Ross Jake
Andrew and Ryan Jon and Ben
Geoff and Cyrus Nick and Doug
Alex and Maria Greg and Yannick
Colin

Week 12:

For Monday and Wednesday: DSM

TreadMarks: Shared Memory Computing on Networks of Workstations, C. Amza, A. L. Cox,


S. Dwarkadas, P. Keleher, H. Lu, R. Rajamony, W. Yu, and W. Zwaenepoel, IEEE Computer, February
1996.

Reaction Notes Question: Describe Lazy Consistency. What data consistency guarentees does it
make? Evaluate Lazy Consistency
for DSM systems (why? what are the trade-offs? explain.)

For Friday:

Project Work Day. Class will meet in the Robot Lab.

Week 13:

For Monday:

Project Work Day. Class will meet in the Robot Lab.


Wednesday and Friday: Final Project Presentations

Wednesday Friday
Alex and Maria Cyrus and Geoff
Jake

Week 14:

Final Project Presentations

Monday Wednesday Friday


Janis and Ross Colin Jon and Ben
Andrew and Ryan Yannick and Greg Nick and Doug

 
 
 
 
 
 
 
 

You might also like