Demo Data from EDBT 2026 / reviewers in the wild / expert
Frank Mehnert
dblp:62/7027
· DBLP profile ↗
2ranked-venue papers
1as first author
0since 2021 · last 2005
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Human-computer interaction and ubiquitous computing · 1Applied, interdisciplinary, general and emerging computing · 1 · 1 first-author
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 |
Embedded and real-time systems · 100% | |
| Software engineering, system software, and programming languages
1 paper |
Operating systems · 100% |
Topics — the 3 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Embedded and real-time systems
real-time operating systems |
0.0 | 1 | 2002 | Cost and Benefit of Separate Address Spaces in Real-Time Operating Systems · RTSS 2002 |
Operating systems › kernel › kernel design
microkernel |
0.0 | 1 | 2002 | Cost and Benefit of Separate Address Spaces in Real-Time Operating Systems · RTSS 2002 |
Embedded and real-time systems › real-time operating systems
interrupt latency |
0.0 | 1 | 2002 | Cost and Benefit of Separate Address Spaces in Real-Time Operating Systems · RTSS 2002 |
Methods — techniques the papers use, named apart from their topics
measurement-based comparison · 0.1
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2005 | The Nizza secure-system architectureabstractThe trusted computing bases (TCBs) of applications running on today's commodity operating systems have become extremely large. This paper presents an architecture that allows to build applications with a much smaller TCB. It is based on a kernelized architecture and on the reuse of legacy software using trusted wrappers. We discuss the design principles, the architecture and some components, and a number of usage examples. Hermann Härtig, Michael Hohmuth, Norman Feske, Christian Helmuth, Adam Lackorzynski, Frank Mehnert, Michael Peter |
CollaborateCom | 6 |
| 2002 | Cost and Benefit of Separate Address Spaces in Real-Time Operating SystemsabstractThe combination of a real-time executive and an off-the-shelf time-sharing operating system has the potential of providing both predictability and the comfort of a large application base. To isolate the real-time section from a significant class of faults in the (ever-growing) time-sharing operating system, address spaces can be used to encapsulate the time-sharing subsystem. However, in practice, designers seldom use address spaces for this purpose, fearing that the extra cost induced limits the system's predictability. To analyze this cost, we compared in detail two systems with almost identical interfaces-both are a combination of the Linux operating system and a small real-time executive. Our analysis revealed that for interrupt-response times, the delay and jitter caused by address spaces are similar to or even smaller than those caused by caches and blocked interrupts. As a side effect of our analysis, we observed that published figures on predictability must be carefully checked whether or not such hardware features are included in the analysis. This paper is a follow-up of an earlier publication at the 3rd Real-Time Linux workshop. It is different in that we have further optimized our microkernel and examined more hardware. Frank Mehnert, Michael Hohmuth, Hermann Härtig |
RTSS | 1 |