Demo Data from VLDB 2026 / reviewers in the wild / expert
Robert S. Fabry
dblp:31/5053
· DBLP profile ↗
3ranked-venue papers
2as first author
0since 2021 · last 1984
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 2 · 2 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.
| Computer architecture, parallel and distributed computing, and storage systems
1 paper |
Storage systems · 50% Performance modeling and evaluation · 50% | |
| Software engineering, system software, and programming languages
3 papers |
Operating systems · 63% Software maintenance and evolution · 28% Requirements engineering and software design · 8% |
Topics — the 8 heaviest of 9, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Storage systems
file systems |
0.0 | 1 | 1984 | A Fast File System for UNIX · ACM Trans. Comput. Syst. 1984 |
Performance modeling and evaluation › workload characterization
locality analysis |
0.0 | 1 | 1984 | A Fast File System for UNIX · ACM Trans. Comput. Syst. 1984 |
Software maintenance and evolution › software evolution › software adaptation
dynamic reconfiguration |
0.0 | 1 | 1976 | How to Design a System in Which Modules Can Be Changed on the Fly · ICSE 1976 |
Operating systems › resource management › storage management › file systems
file system interface |
0.0 | 1 | 1984 | A Fast File System for UNIX · ACM Trans. Comput. Syst. 1984 |
Operating systems › system security › operating system security › protection mechanism
capability-based protection |
0.0 | 1 | 1973 | The Case for Capability-Based Computers · SOSP 1973 |
Operating systems › system security
operating system security |
0.0 | 1 | 1973 | The Case for Capability-Based Computers · SOSP 1973 |
Requirements engineering and software design
software architecture |
0.0 | 1 | 1976 | How to Design a System in Which Modules Can Be Changed on the Fly · ICSE 1976 |
Authentication and access control
access control |
0.0 | 1 | 1973 | The Case for Capability-Based Computers · SOSP 1973 |
Methods — techniques the papers use, named apart from their topics
throughput measurement · 0.0block allocation policy design · 0.0software design · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1984 | A Fast File System for UNIXabstractA reimplementation of the UNIX TM file system is described.The reimplementation provides substantially higher throughput rates by using more flexible allocation policies that allow better locality of reference and can be adapted to a wide range of peripheral and processor characteristics.The new file system clusters data that is sequentially accessed and provides two block sizes to allow fast access to large files while not wasting large amounts of space for small files.File access rates of up to ten times faster than the traditional UNIX file system are experienced.Long-needed enhancements to the programmers' interface are discussed.These include a mechanism to place advisory locks on files, extensions of the name space across file systems, the ability to use long file names, and provisions for administrative control of resource usage. Marshall K. McKusick, William N. Joy, Samuel J. Leffler, Robert S. Fabry |
ACM Trans. Comput. Syst. | 4 |
| 1976 | How to Design a System in Which Modules Can Be Changed on the Fly
Robert S. Fabry |
ICSE | 1 |
| 1973 | The Case for Capability-Based ComputersabstractThe idea of a capability which acts like a ticket authorizing the use of some resource was developed by Dennis and Van Horn as a generalization of addressing and protection schemes such as the code- words of the Rice computer, the descriptors of the Burroughs machines, and the segment and page tables in computers such as the GE-645 and IBM 360/67. Dennis and Van Horn generalized the earlier schemes by extending them to include not just memory, but all systems resources: memory, processes, input/output devices, and so on; and by stressing the explicit manipulation of access control by nonsystem programs. The idea is that a capability is a special kind of address for an object, that these addresses can be created only by the supervisor, and that in order to use any object, one must address it via one of these addresses. The name comes from the fact that having one of these special kinds of addresses for a resource provides one with the capability to use the resource. Robert S. Fabry |
SOSP | 1 |