Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

John R. Ellis

dblp:67/2565 · DBLP profile ↗
← Back
3ranked-venue papers
1as first author
0since 2021 · last 1992
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 3 · 1 first-authorSystems, architecture and hardware · 1

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
2 papers
Concurrent programming · 58% Runtime systems and virtual machines · 33% Operating systems · 9%
Computer architecture, parallel and distributed computing, and storage systems
2 papers
Processor architecture and microarchitecture · 64% Parallel and multicore computing · 36%

Topics — the 5 heaviest of 7, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Concurrent programming › atomicity
atomic operations
0.011992
Fast Mutual Exclusion for Uniprocessors · ASPLOS 1992
Concurrent programming
synchronization
0.011992
Fast Mutual Exclusion for Uniprocessors · ASPLOS 1992
Runtime systems and virtual machines › garbage collection
concurrent garbage collection
0.011988
Real-Time Concurrent Collection on Stock Multiprocessors · PLDI 1988
Runtime systems and virtual machines
garbage collection
0.011988
Real-Time Concurrent Collection on Stock Multiprocessors · PLDI 1988
Parallel and multicore computing › multiprocessor system
shared-memory multiprocessor
0.011988
Real-Time Concurrent Collection on Stock Multiprocessors · PLDI 1988

Methods — techniques the papers use, named apart from their topics

software reservation · 0.0optimistic mechanism · 0.0kernel emulation · 0.0virtual memory · 0.0copying garbage collection · 0.0
YearPublicationVenuePosition
1992 Fast Mutual Exclusion for Uniprocessors
abstract
In this paper we describe restartable atomic sequences, an optimistic mechanism for implementing simple atomic operations (such as Test-And-Set) on a uniprocessor. A thread that is suspended within a restartable atomic sequence is resumed by the operating system at the beginning of the sequence, rather than at the point of suspension. This guarantees that the thread eventually executes the sequence atomically. A restartable atomic sequence has significantly less overhead than other software-based synchronization mechanisms, such as kernel emulation or software reservation. Consequently, it is an attractive alternative for use on uniprocessors that do no support atomic operations. Even on processors that do support atomic operations in hardware, restartable atomic sequences can have lower overhead.
Brian N. Bershad, David D. Redell, John R. Ellis
ASPLOS3
1988 Real-Time Concurrent Collection on Stock Multiprocessors
abstract
We've designed and implemented a copying garbage-collection algorithm that is efficient, real-time, concurrent, runs on commercial uniprocessors and shared-memory multiprocessors, and requires no change to compilers. The algorithm uses standard virtual-memory hardware to detect references to “from space” objects and to synchronize the collector and mutator threads. We've implemented and measured a prototype running on SRC's 5-processor Firefly. It will be straightforward to merge our techniques with generational collection. An incremental, non-concurrent version could be implemented easily on many versions of Unix.
Andrew W. Appel, John R. Ellis, Kai Li 0001
PLDI2
1983 Tools: An Environment for Time-Shared Computing and Programming
abstract
Abstract The Yale Tools environment provides integrated modern computing facilities to a mixed group of programmers and users on time‐shared machines. Hundreds of people use the environment every day for systems and applications programming, word‐processing and university business. The success of the environment is in its integration and engineering detail. Building such a system without a high‐level language and a run‐time library would have been impossible.
John R. Ellis, Nathaniel Mishkin, Mary-Claire Van Leunen, Steven R. Wood
Softw. Pract. Exp.1