A typical US college student who is asked to name people who have made significant contributions to computing will likely produce a short, predictable, fairly homogeneous list. To help increase awareness of the diversity of people involved in computing, we introduced a biography project into an introductory non-majors course at a small liberal arts college. With each student exploring and presenting on the life and contributions of a less well-known contributor to computing, the class is exposed to a number of people that students likely haven't heard of previously. Moreover, with fairly open-ended requirements for the assignment, we can learn what students find interesting and noteworthy about these individuals, perhaps finding ways to more broadly increase awareness.

Since its inception half a century ago, DRAM has required dynamic/active refresh operations that block read requests and decrease performance. We propose refreshing DRAM in the background without stalling read accesses to refreshing memory blocks, similar to the static/background refresh in SRAM. Our proposed Nonblocking Refresh works by refreshing a portion of the data in a memory block at a time and uses redundant data, such as Reed-Solomon codes, in the block to compute the block's refreshing/unreadable data to satisfy read requests. For proof of concept, we apply Nonblocking Refresh to server memory systems, where every memory block already contains redundant data to provide hardware failure protection. In this context, Nonblocking Refresh can utilize server memory system's existing per-block redundant data in the common-case when there are no hardware faults to correct, without requiring any dedicated redundant data of its own. Our evaluations show that on average across five server memory systems with different redundancy and failure protection strengths, Nonblocking Refresh improves performance by 16.2% and 30.3% for 16gb and 32gb DRAM chips, respectively.