April 23-26, 2024, Athens, Greece
Call for Papers
The European Conference on Computer Systems (EuroSys) is a premier international forum for presenting computer systems research. EuroSys 2024 seeks papers on all areas of computer systems research, including:
Cloud computing and datacenter systems
File and storage systems
Language support and runtime systems
Systems security and privacy
Analysis, testing and veriﬁcation of systems
Database systems and data analytics frameworks
Virtualization and virtualized systems
Systems for machine learning/machine learning for systems
Mobile and pervasive systems
Parallelism, concurrency, and multicore systems
Real-time, embedded, and cyber-physical systems
Systems for emerging hardware
We encourage papers that span multiple topics and communities. Papers will be judged on novelty, significance, correctness, and clarity. The program committee seeks papers that address a significant problem with an interesting and compelling solution whose validity and practicality are clearly demonstrated. A good paper will draw appropriate conclusions, honestly present related prior work, acknowledge its own limitations, and clearly articulate the advances it offers over prior work.
Full paper submissions due: May 24, 2023
Author Response Period
Reviews available: August 5, 2023
Author responses due: August 7, 2023
Notification to authors: September 12, 2023
Camera-ready deadline: October 12,2023
Full paper submissions due: October 19, 2023
Author Response Period
Reviews available: January 9, 2024
Author responses due: January 14, 2024
Notification to authors: February 7, 2024
Camera-ready deadline: March 7, 2024
EuroSys '24 offers authors the choice of two submission deadlines. Any paper submitted to one of these deadlines and accepted during the subsequent reviewing period will be presented at the conference and will appear as part of the proceedings. In the meantime, authors are permitted to advertise their papers as accepted by EuroSys, for example listing them on CVs.
A paper submitted at the spring deadline for EuroSys '24 and rejected may not be submitted again until the spring deadline for EuroSys '25. A paper submitted at the fall deadline for EuroSys '24 and rejected may not be submitted again until the fall deadline for EuroSys '25.
Each paper may be accepted, rejected, or given the option of one-shot revision. If offered a revision option, authors can choose to revise and resubmit the paper for the subsequent EuroSys deadline. This will be the EuroSys ‘24 fall deadline if offered a revision from a spring submission. If offered a revision from the fall submission, authors may revise and resubmit to the subsequent (EuroSys ‘25) spring deadline for publication (if accepted) and presentation at EuroSys ‘25.
Authors offered a revision option will be given detailed instructions about how to re-submit. These will include the list of necessary changes for the paper to be accepted. These may include larger changes than during the shepherding process for accepted papers, e.g. additional results or performance comparisons. The re-submission should include the revised paper, a version of the paper in which the differences from the first submission are clearly marked, and a separate high-level summary of the differences between the two versions.
A revision option is not a guarantee of acceptance. The revised and resubmitted paper will be re-evaluated by the PC. The paper can still be rejected if the revision instructions have not been fully addressed; if new assertions are made without adequate support; or if the revised version unveils significant new concerns that were hidden in the original submission. Revised and resubmitted papers will receive either an accept or a reject decision; there will be no further revision options offered.
Note: at least one full registration fee (member or non-member) will be required for each paper accepted at the plenary conference, even if the presenter is eligible for a student fee.
Resubmission and concurrent submission
Authors submitting to EuroSys must adhere to ACM’s policy on Prior Publication and Simultaneous Submissions. If a revision option is offered and accepted, the paper is still considered under submission to EuroSys and still subject to this policy until it is explicitly withdrawn or rejected. If a revision option is offered and declined, the same policy applies as for a rejection.
If a paper is rejected after a revise-and-resubmit, it may not be submitted again to EuroSys until 11 months after the deadline to which the revised version was submitted.
Spring submission URL: https://eurosys24.hotcrp.com
Anonymity: Reviewing is double-blind, meaning that the authors‘ identities will be hidden from the reviewers and vice versa. Authors must make a good faith effort to anonymize their submissions, and they should not identify themselves either explicitly or by implication (e.g., through the references or acknowledgments). Authors should be listed as:
Submission Id: <Paper-ID> where the <Paper-ID> is the ID assigned after abstract registration.
Use care in referring to your own related work. Do not omit references to your prior work, as this would make it difficult for reviewers to place your submission in its proper context. Instead, reference your past work in the third person, just as you would any other piece of related work. For example, you might say “Our system modifies the XYZ operating system built by Smith et al. ”.
A submission may extend a previous workshop paper, or it may relate to a submission currently under review. In these cases, you must still explain the differences between your present submission and the other work, but you should cite the other work anonymously and e-mail the deanonymized work to the PC chairs.
Authors are permitted to post drafts of their submission on e.g. arxiv or as technical reports on their institution’s website. However, the submitted version should have a substantially different title, and a different system/tool name (if it uses one) from the draft version.
Submissions violating the detailed formatting and anonymization rules will not be considered for review. EuroSys applies ACM‘s policies for plagiarism, conflicts of interest, submission confidentiality, reviewer anonymity, and prior and concurrent paper submission. If you are uncertain about how to anonymize your submission, whether or not your submissions meet these guidelines, or have specific questions about the guidelines, please contact the program co-chairs, email@example.com, well in advance of the submission deadline.
Conflicts: When registering and submitting your paper, you will need to provide information about conflicts with PC members. Use the following guidelines to determine conflicts:
Institution: You are currently employed at the same institution, have been previously employed at the same institution within the past two years, or are going to begin employment at the same institution.
Advisor or Collaboration: You have a past or present association as thesis advisor or advisee, or you have a collaboration on a project, publication, grant proposal, or editorship within the past two years (2020 or later), or reasonably expect one within the next year.
More details on the conflict of interest policy can be found at the ACM website.
The PC chairs will review paper conflicts to ensure the integrity of the reviewing process, adding conflicts if necessary. Similarly, if there is no basis for conflicts provided by authors, such conflicts will be removed. Improperly identifying PC members as a conflict in an attempt to avoid having an individual review your paper may lead to the submission being rejected without review. If you have any questions about conflicts, please contact the program co-chairs (firstname.lastname@example.org).
Page limit and formatting: Submissions may have at most 12 pages of technical content, including all text, figures, tables, etc. Bibliographic references are not included in the 12-page limit. In addition, submissions may include as many additional pages as needed for supplementary material in appendices. The paper should stand alone without the supplementary material, but authors may use this space for content that may be of interest to some readers but is peripheral to the main technical contributions of the paper. Note that members of the program committee are free to not read this material when reviewing the paper.
Use A4 or US letter paper size, with all text and figures fitting inside a 178 x 229 mm (7 x 9 in) block centered on the page, using two columns separated by ≥8 mm (0.33″) of whitespace. Use ≥10-point font (typeface Times Roman, Linux Libertine, etc.) on ≥12-point (single-spaced) leading for all text including figure and table captions. Graphs and figures should be readable when printed in grayscale, without magnification. All pages should be numbered. Authors are encouraged to hyperlink their references.
Most of these rules are automatically applied when using the official SIGPLAN Latex (\documentclass[sigplan, … ]) or MS Word templates from here. For any paper parameters not defined above, assume that the required value is the one used in these templates.
Any papers that deviate significantly from the formatting instructions will be administratively rejected.
For Latex, we recommend you use (where <PAPER_ID> is the paper ID you received after abstract registration):
% Optional: Remove the ACM reference between the abstract and the main text.
% Optional: Comment out the CCS concepts and keywords.
If you are submitting a revised paper because you received a revise-and-resubmit decision from the previous deadline, you should already have received instructions by e-mail on how to prepare the revision submission. At submission time please tick the appropriate box in HotCRP for the fall submission, and also provide the required additional information (spring submission paper #, supplemental material, and summary of revision).
For any further information, please contact the PC chairs: email@example.com
Mark Silberstein, Technion
Bianca Schroeder, University of Toronto
PC Members for both deadlines
Aishwarya Ganesan, University of Illinois Urbana-Champaign and VMware Research
Amir Yazdanbakhsh, Google Research, Brain Team
Andreas Haeberlen, University of Pennsylvania / Roblox
Andrew Quinn, University of California, Santa Cruz
Ang Chen, Rice University
Animesh Trivedi, VU Amsterdam
Anton Burtsev, University of Utah
Arif Merchant, Google
Baptiste Lepers, Université de Neuchâtel
Chia-Che Tsai, Texas A&M University
Daehyeok Kim, University of Texas at Austin and Microsoft
Daniel S. Berger, Microsoft Research
David Cock, ETH Zurich
Deepak Narayanan, Microsoft Research
Divya Mahajan, Microsoft Research
Eleanor Birrell, Pomona College
Evangelia Kalyvianaki, University of Cambridge
Fernando Pedone, University of Lugano, Switzerland
Haggai Eran, NVIDIA
Iqbal Mohomed, Samsung AI Centre Toronto
Ishai Menache, Microsoft Research
Jia-Ju Bai, Beihang University
Jian Huang, UIUC
Jiri Schindler, IonQ
john wilkes, Google
Jongsoo Park, Meta
Kaveh Mahdaviani, University of Toronto
Kevin Hsieh, Microsoft Research
Laurent Bindschaedler, MPI-SWS
Linhai Song, Pennsylvania State University
Liuba Shrira, Brandeis University
Lluís Vilanova, Imperial College London
Lorenzo Alvisi, Cornell University
Malte Schwarzkopf, Brown University
Manuel Costa, Azure Research, Microsoft
Marc Shapiro, Sorbonne-Université–LIP
Marco Canini, KAUST
Marcos K. Aguilera, VMware Research
Maria Carpen-Amarie, Huawei Research
Marios Kogias, Imperial College London & Azure Research
Mark Silbersteinc chair, Technion
Marko Vukolić, IBM Research - Zurich
Matteo Interlandi, Microsoft
Matthew Burke, Cornell University
Meni Orenbach, NVIDIA
Michio Honda, University of Edinburgh
Minsoo Rhu, KAIST / Meta
Neeraja J. Yadwadkar, UT Austin and VMware Research
Nils Asmussen, Barkhausen Institut
Nuno Preguica, Universidade Nova de Lisboa
Onur Mutlu, ETH Zurich
Pascal Felber, University of Neuchatel, Switzerland
Pedro Fonseca, Purdue University
Pierre Olivier, The University of Manchester
Pramod Bhatotia, TU Munich
Qizhen Zhang, University of Toronto
Ramnatthan Alagappan, University of Illinois Urbana-Champaign and VMware Research
Reto Achermann, University of British Columbia
Rodrigo Rodrigues, Instituto Superior Técnico (ULisboa) / INESC-ID
Rüdiger Kapitza, Friedrich-Alexander-Universität
Sanydhya Kashyap, EPFL
Saurabh Bagchi, Purdue University
Saurabh Kadekodi, Google
Shai Bergman, Technion
Shivaram Venkataraman, University of Wisconsin-Madison
Somali Chaterji, Purdue University
Tanvir Ahmed Khan, University of Michigan
Thaleia Dimitra Doudali, IMDEA Software Institute
Tianzheng Wang, Simon Fraser University
Tyler Hunt, Katana Graph
Umesh Deshpande, IBM Research - Almaden
Vasily Tarasov, IBM Research
Y. Charlie Hu, Purdue University
Yang Wang, Meta/The Ohio State University
Yossi Gilad, Hebrew University of Jerusalem
Youngjin Kwon, KAIST
Yubin Xia, Shanghai Jiao Tong University
Zsolt István, TU Darmstadt
PC Members for the fall deadline only
André Brinkmann, Johannes Gutenberg University Mainz
Boris Köpf, Azure Research, Microsoft
Eddie Kohler, Harvard University
Eiko Yoneki, University of Cambridge
Lydia Y. Chen, TU Delft
Moshe Gabel, York University
Naama Ben-David, VMware Research
Panos Kalnis, King Abdullah University of Science and Technology
Sara Bouchenak, INSA Lyon
Wenjun Hu, Yale University, Google
Copyright © EuroSys 2024