|
November 29: | Reminder: There are still many open slots for giving the demo. Let me re-iterate, TA will not take any demos beyond December 07.
So if you do not signup for demo asap, after December 07, the TA will run the project himself and if something is not clear the TEAM will not get
a chance to refute the grades awarded. So it is in your own interest to make sure you do give demo on or before December 07 by signing up for one
of the available slots.
|
|
November 27: | Demo signup sheet for on-campus teams /
individuals has
been posted on Dr. Newman's door. There are a total of 18 slots each of 20
minutes duration. Please take only 1 slot per team. You can bring your own
laptop for giving the demo. Grades has to be awared for project 3 by
December 07 2006 hence do make sure you do find a suitable slot for your
team. All demos to be held in CSE 309. Also all the slots are on
wednesdays and thursdays only on these dates: Nov 29, 30 and Dec 06, 07
2006. Remember no demos will be taken after December 07
2006.
|
|
November 22: | Project 3 deadline has been extended by 2 days. It is now due on November 28 for
on campus students and on November 29 for EDGE students.
|
|
November 16: | Most of Quiz 6 grades have been posted. Solution to the quiz will be posted soon once TA receives all quiz solutions from EDGE students.
Also Quiz 5 grades will be posted within 1 week. It has not yet been graded.
|
|
November 08: | It is highly recommended that all teams regularly check with the posted specification because there might be possible
minor changes going on throughout the remaining duration of the project. The project specification link on the class webpage will always
point to the latest version of the protocol specification.
|
|
November 08: | Project 3 deadline extended by 1 week. It is now due November 26 for On Campus students and November 27 for EDGE.
|
|
November 08: | New policy regarding in class quiz:: +1 additional point to be given to all those who shows up for the quiz from now onwards.
|
|
November 08: | In addition to the bonus awarded to team whose protocol was selected, Dr. Nemo has agreed to award upto 5 bonus points
to all other teams / students who takes/has taken active participation in the specification shaping / finalization. In addition original
authors of the selected protocol are required to frequently visit the wiki and update if needed the spec. or suggest a workaround for the
issues entered in the wiki by other teams to claim full bonus originally awarded. All these communications have to be preferably done
through the wiki.
|
|
November 08: | A new wiki has been created to keep track of new issues and proposed workarounds / solutions. This wiki can be
accessed at http://www.cise.ufl.edu/class/cop5615fa06/wiki/. You will need
username and password to make changes in this wiki which have been emailed to all the students. Check your gatorlink inbox.
|
|
October 29: | Project 3.2 has been posted. Refer to Project 3.1 pdf description of the basic goals and the finalized standard made
available in Project 3.2 section to implement your code. Due dates are approx 3 weeks from October 30.
|
|
October 26: | Peer reviews analysis has been compiled and posted at this link. Team04 specification
seems to be the most likely candidate for selection. Team 4 members are requested to go through feedback on their specification by
other teams and improve if possible their specification based on the feedbacks. Team 4 is also requested to email the TA the
final version by Saturday 12:00 pm EST (noon). Each member of team 4 will be given 10% extra credit towards project 3 grades.
|
|
October 25: | Peer reviews for protocol revision 2 has been published online. It can be accessed here:
http://www.cise.ufl.edu/class/cop5615fa06/reviews/ver_2/
|
|
October 24: | Quiz 4 has been graded and the solution posted. Also please send your feedback regarding protocol revision 2 for project 3 positively
by Wednesday 4:59 pm at cop5615@gmail.com, please check your gatorlink email for more details.
|
|
October 24: | Here are the averages: [Quiz1,0.96] [Quiz2,2.25] [Quiz3,0.54] [Quiz4,1.32] [Proj1,83.58] [Proj2,92.98] Project 2 average will change
because there are still some projects yet to be graded.
|
|
October 18: | Dr. Nemo will hold class discussion and review of the four selected protocol specification tomorrow (Thursday October 19). All on-campus
students are expected to come prepared to take part in the discussion. Please read carefully and understand the four protocols making notes of any
shortfalls in their description. You can email the TA your preference choice after taking part in the class discussion.
|
|
October 18: | Every team should email TA [cop5615@gmail.com] indicating which one of the four selected protocol specification they would prefer to be made as the final
project 3 protocol standard. Do review these carefully, if you believe some additional modification is needed for the specification you choose, do include
those comments as well in your e-mail. Use subject 'FINAL PROTOCOL CHOICE'. Make sure you send your emails by Thursday October 19 11:59 pm EST at the latest.
PLEASE ONLY 1 EMAIL PER TEAM. Note: Those students who have not formed team till now, please indicate your team to the TA asap.
|
|
October 18: | Peer protocol reviews have been analyzed and the ratings have been compiled. Compiled ratings and updated team information
can be checked here. Out of 19 submitted (18 reviewed) protocol submissions, 4 candidate protocol specifications have
been selected on the basis of peer feedback. Those can be found here. Also
you can check the peer feedback at this link.
|
|
October 14: | EXAM 1 will cover chapters 1 to 4 plus class notes. It will be a closed book and closed notes exam.
One two-sided 8.5" by 11" crib sheet allowed. Bring 8.5" by 11" paper and pen. Past exams can be accessed HERE. Time and Place for On-Campus students: Tuesday 10/17 5:30-7:30 in
CSE-118/120. EDGE students should plan to take it within 1 week from October 17.
|
|
October 12: | Protocol Drafts submitted by on-campus students till today morning have been made available online at
http://www.cise.ufl.edu/class/cop5615fa06/protocols for peer reviews.
Please review all the other teams' submissions and send an email at cop5615@gmail.com providing a rating from 1 - 5 [5 = max] for each
submission along with comments on Pros and Cons of each approach. Please do so before Saturday October 14th 2006 12:00 noon EST.
ONE EMAIL PER TEAM ONLY & USE 'PROTOCOL REVIEW' AS EMAIL SUBJECT.
|
|
October 10: | Team Details have been compiled in this pdf file based on emails received till today. Students who
have not sent in their team details must do so at the earliest. Listed are also students' names whose team informations have not yet been emailed
to the TA.
|
|
October 09: | Quiz 3 grades and solution has been posted. Only 5 on-campus students got points other than zero [Max 3, Min 0]
|
|
October 05: | Quiz 2 grades and solution has been posted. Log on to UF-IBA to check your scores.
|
|
October 04: | Demo Signup sheet for On-Campus students will be posted on Dr Newman's office door at 10 am on Thursday October 05, 2006.
Slots will be taken on a first come first served basis. There are a total of 28 slots. Remaining students who could not get slots must wait till
October 12, 2006 for a new demo signup sheet to be posted. Students who have already given the demo must not signup again.
There are 8 slots for tomorrow Thursday October 05, 2006. 8 slots for Monday October 09, 2006 and 12 slots for Wednesday October 11, 2006.
|
|
September 21: | Project 2 has been assigned. Due dates October 02 (on campus) and October 05 (EDGE).
|
|
September 14: | Read 3.5-3.9 carefully by Tues 9/19, also Homework 2 has been posted
|
|
September 12: | One way to double check if your submission of projects on UF-IBA system went OK or not is to immediately try to download back
the file after the system generates the confirmation number and then seeing if the downloaded file untars properly or not. If it does then no further
action is needed. If it does not, try uploading again.
|
|
September 11: | Homeworks are not to be submitted and will not be graded. However please do the problems as they will be later discussed
in class most likely within 2 weeks of the date assigned.
|
|
September 07: | Quiz 1 grades have been posted online, log on to UF-IBA to check your grade. Max=2.5 and Min=0 out of 5.
|
|
August 31: | Project 1 has been assigned. Due dates September 13 (on campus) and September 18 (EDGE).
|
|
August 29: | Read Chapter 1 by Tuesday 8/29, Read Chapter 2 by Thursday 8/31 and Read Chapter 3 sections 1-4 by Tuesday 9/5.
|
|
August 29: | All reading assignments and homeworks refer to Chow and Johnson.
|
|
August 24: | Do not use the URLs shown in the video recording while the TA was giving the demo on IBA system, it was only for demonstration
purposes. Use the links and the login form available from the course webpage only.
|
|
August 24: | Please create your UF-IBA coursetool account as soon as possible and familiarize yourself with the system and your password
set. Try to do multiple and frequent logins during first few weeks to make sure you fully understand the system.
|
|
SOLUTION TO QUIZ PROBLEMS:
Quiz 1:
1. Define & distinguish (a) Hardware Coupling Degree and (b) Software Coupling Degree
->H/W ~ Time for local access / Time for remote access
->S/W ~ Centralization of data (state) and control
Quiz 2:
List and explain 4 differences between kernel threads and user-level threads. Note advantages and disadvantages
->User Level threads: (1)Process Time is multiplexed between various threads from same process (2)Context Switching done in user space (3)Blocking call by one thread
does not block the process (4)Context Switching is very fast
->Kernel Level threads: (1)Assigning Thread priority and preemption is very flexible and easy(2)Context Switching done in Kernel space (3)Blocking call
on thread does not block
the whole process but the two level abstraction is lost (4)Context switching is slow
Quiz 3:
Quiz 4:
->Multivalued Semaphore using LINDA
---------------------------------------
Starter:: int S = N; eval(OUT("S", N));
---------------------------------------
P("S", k)
{
int k;
int x; x=0;
while(x < k) {
RD("S", ?x);
if(x >= k) {
IN("S", ?x);
if(x >= k) {
x -= k;
OUT("S", x);
x += k;
}
else {
OUT("S", x);
}
}
}
}
----------------------------------------
V("S", k)
{
int k;
int x;
IN("S", ?x);
OUT("S", x + k);
}
Quiz 6:
1. What are similarities / differences between weak access consistency & barrier synchronization?
-> Weak access consistency is only a guarantee for the process that calls synch(s) that all its writes / reads
issued prior to the call have completed before it continues, and that no new acceses wil be allowed to start
until the synch call completes. Barrier synch requires all procs that call it to wait until all procs reach
that point. Accesses are assumed to complete sequentially ...
|
