Methodology

We should probably have our work verified by at least one group member before posting to the actual page

To Do

Right now

Improve the grammar/structure of the paper section
Background Concepts -fill in info (fii)
Research problem -fii
Contribution -fii
Critique -fii
References fii

Done

This is a (mostly) chronological order of changes

I added an outline to the paper, feel free to change it, just put a reason for any changes here. -Rannath
Paper section now has all required information, feel free to add -Rannath

Paper

The paper's title, authors, and their affiliations. Include a link to the paper and any particularly helpful supplementary information.

Authors in order presented: Silas Boyd-Wickizer, Austin T. Clements, Yandong Mao, Aleksey Pesterev, M. Frans Kaashoek, Robert Morris, and Nickolai Zeldovich

An Analysis of Linux Scalability to Many Cores

Background Concepts

Explain briefly the background concepts and ideas that your fellow classmates will need to know first in order to understand your assigned paper.

Ideas to explain:

thread (maybe)
Linux's move towards scalability precedes this paper. (assert this, no explanation needed, maybe a few examples)
Summarize scalability tutorial (Section 4.1 of the paper)
Describe the programs tested (what they do, how they're programmed (serial vs parallel), when were they originally released wrt multi-core processing, significant updates wrt scalability not from this paper)

Research problem

What is the research problem being addressed by the paper? How does this problem relate to past related work?

Problem being addressed: scalability of current generation OS architecture, using Linux as an example. (?)

Summarize related works (Section 2, include links, expand information to have at least a summary of each related work)

Contribution

What was implemented? Why is it any better than what came before? What does that mean in terms of the potential scalability of modern OSs?

Summarize info from Section 4.2 onwards, maybe put graphs from Section 5 here to provide support for improvements (if that isn't unethical/illegal)?

Conclusion: we can make a traditional OS architecture scale (at least to 48 cores), we just have to remove bottlenecks.

Critique

What is good and not-so-good about this paper? You may discuss both the style and content; be sure to ground your discussion with specific references. Simple assertions that something is good or bad is not enough - you must explain why.

Since this is a "my implementation is better then your implementation" paper the "goodness" of content can be impartially determined by its fairness and by how relevant presented changes are.

Relevance criterion:

how popular is the program used to test?
does the test accurately describe real-world use-cases (or some set there-of)?

Fairness criterion:

does the test put all tested implementations through the same test? (or their implementation through a harder test)

Style Criterion (feel free to add I have no idea what should go here):

does the paper present information out of order?
does the paper present needless information?
does the paper have any sections that are inherently confusing?

References

You will almost certainly have to refer to other resources; please cite these resources in the style of citation of the papers assigned (inlined numbered references). Place your bibliographic entries in this section.