Talk:CSC/ECE 506 Spring 2014/7b ks: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
Changes begin with the section entitled, "TLB coherence problem in multiprocessing," nicely dovetailing with one of the other rewrites, which only modified the Background section. The new prose is generally good, but there are several typos, which the next revision could fix. | Changes begin with the section entitled, "TLB coherence problem in multiprocessing," nicely dovetailing with one of the other rewrites, which only modified the Background section. The new prose is generally good, but there are several typos, which the next revision could fix. | ||
Lazy devaluation could have been explained more completely ... as could some of the other approaches in that section. "This approach works well unless processes run in parallel in the same address space" is a sentence in need of further elucidation. | |||
Your separation into software and hardware schemes amounted to simply putting the unimplemented UNITD scheme into a new category. Thus, I don't think this adds a great deal of value to the organization. | |||
Latest revision as of 03:29, 29 April 2014
Changes begin with the section entitled, "TLB coherence problem in multiprocessing," nicely dovetailing with one of the other rewrites, which only modified the Background section. The new prose is generally good, but there are several typos, which the next revision could fix.
Lazy devaluation could have been explained more completely ... as could some of the other approaches in that section. "This approach works well unless processes run in parallel in the same address space" is a sentence in need of further elucidation.
Your separation into software and hardware schemes amounted to simply putting the unimplemented UNITD scheme into a new category. Thus, I don't think this adds a great deal of value to the organization.