Real-Time Support for Software Transactional Memory Toufik Sarni, Audrey Queudet, Patrick Valduriez

Real-Time Support for Software Transactional Memory Toufik Sarni, Audrey Queudet, Patrick Valduriez

Real-Time Support for Software Transactional Memory Toufik Sarni, Audrey Queudet, Patrick Valduriez To cite this version: Toufik Sarni, Audrey Queudet, Patrick Valduriez. Real-Time Support for Software Transactional Memory. IEEE International Conference on Embedded and Real-Time Computing Systems and Ap- plications (RTCSA), Aug 2009, Beijing, China. pp.477-485. hal-00422596 HAL Id: hal-00422596 https://hal.archives-ouvertes.fr/hal-00422596 Submitted on 7 Oct 2009 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. 1 Real-Time Support for Software Transactional Memory Toufik Sarni∗, Audrey Queudet∗, Patrick Valduriez† University of Nantes∗ LINA and INRIA, Nantes, France∗† emails: {[email protected]}∗ [email protected] Abstract—Transactional memory is currently a hot research the issue has not yet been addressed for TM. Most of existing topic, having attracted the focus of both academic researchers solutions for real-time scheduling consider either tasks in and development groups at companies. Indeed, the concept multiprocessor systems or transactions in database systems, of transactional memory has recently attracted much interest for multicore systems as it eases programming and avoids but not both together. Therefore, we have turned our attention the problems of lock-based methods. However, up to now, the towards the design of a real-time STM in which we have scheduling of real-time transactions within software transactional formalized the introduction of a real-time model. We have memories has not been studied. To address this issue, we present implemented a new real-time scheduler of transactions for in this paper a real-time software transactional memory, namely resolving conflicts between concurrent soft real-time trans- RT-STM. We focus on the scheduling of concurrent soft real-time transactions. In particular, we explore a new heuristic for conflict actions. The transaction model combines concepts found for resolution that reduces the number of deadline violations when the management of real-time transactions in databases and scheduling soft real-time transactions. After having discussed the real-time tasks on multiprocessors. The main characteristic of scalability of various classical STMs under a real-time operating this model is that it considers deadlines for transactions. This system, we present experimental results that show that RT-STM deadline is used by the scheduler either to abort or to help a can improve the performance of transactional memory-based applications on multicore platforms. transaction to complete. To the best of our knowledge, this paper is the first to introduce real-time scheduling of transactions into STM. The I. INTRODUCTION rest of the paper is organized as follows. Section II discusses With the advent of multicore systems, the transactional related work. Section III introduces the models of both tasks memory (TM) concept has attracted much interest from both and transactions and presents the various STMs used in our academy [1], [2] and industry [3] as it eases programming experiments. Section IV presents our real-time transaction and avoids the problems of lock-based methods. By supporting model and its implementation within transactional memory. the ACI (Atomicity, Consistency and Isolation) properties of Section V gives an experimental analysis of STMs under transactions, TM relieves the programmer from dealing with several real-time scheduling policies of tasks and shows the locks to access resources. More important, it avoids the severe advantages of our solution. Finally, Section VI draws the main problems of lock-based methods such as deadlock situations. conclusions and discusses future works. While lock-based methods systematically block all accesses to shared resources, transactional memory allows several trans- II. RELATED WORK actions to access resources in parallel. A transaction is either Brandenburg et al. [13] compare wait-free and lock-free aborted when a conflict is detected, or committed in case algorithms with spin-based and suspension-based synchroniza- of successful completion. Conflicts are handled with non- tion mechanisms. They conducte experiments1 using the real- blocking synchronization which offers a stronger guarantee time operating system LITMUSRT . The four approaches are of forward progress. compared on the basis of both schedulability and tardiness There are three kinds of implementations for transactional bounds, by evaluating their respective overheads with respect memory: hardware-based (HTM) [1], [4], software-based ones, to job release, scheduling and context-switching. One of the denoted as software transactional memories (STM) [2], [5], major conclusions of this work is that non-blocking algorithms [6], [7] and hybrid schemes (HyTM) that combine both are generally preferable for small, simple shared objects. hardware and software supports [8], [9]. HTM researchers Among non-blocking approaches, the authors conclude that mainly focus on the implementation with less attention to wait-free algorithms are preferable to lock-free algorithms. performance. On the contrary, STM researchers take care about Regarding scheduling policies, they show that, unlike parti- performance issues on TM, and several policies [10], [11] have tioned EDF, the global EDF policy does not scale for lock-free been proposed to manage conflicts between transactions. algorithms when the access to shared objects occurs at high There is an early attempt towards hard real-time for HTM frequency. [12]. However, up to now, no real-time transaction model has been specially defined for STM. While real-time scheduling 1The hardware platform used was a four 32-bit Intel Xeon(TM) processors of transactions has been widely studied in real-time databases, running at 2.7 GHz 2 The wait-free algorithms are primarily of interest in hard real- by ui,m= Ci/Pi. We assume that at any time, a processor time transactions [14]. However, implementing a wait-free- executes at most one job, and a job is executed at most on based STM is very difficult since fair access to memory is one processor. usually not guaranteed. Riegel et al. [15] deal with time-based transactional memory Scheduling of tasks. On multiprocessor systems, two that uses time to reason about the consistency of the data alternative paradigms for scheduling collections of tasks accessed by transactions and the order in which transactions are considered: partitioned and global scheduling. For the commit. Usually, implementations like [16], [17] rely upon partitioned approach, the tasks are statically assigned to shared counters which can quickly become bottlenecks as the processors and are always executed on a single processor. number of concurrent threads grows. Each processor has its own scheduling queue of tasks which Riegel et al. [15] show how a time base can affect transac- is independent of other processors and the migration of tional memory performance. They rely on experiments2 which jobs or tasks on other processors is not allowed. Feasibility compare the use of a shared integer counter with that of a analysis under the partitioned paradigm which is comparable MMTimer which is a real-time clock with an interface similar to a bin-packing problem, is NP-Hard. Indeed it consists to the High Precision Event Timer widely available in x86 ma- in placing k objects with different sizes in m boxes which chines. Their main observation is that this enhanced hardware respectively represent the tasks and the processors in our case. support can ensure a much better clock synchronization than First-Fit and Best-Fit algorithms and their variants [20] are mechanisms that require communication via shared memory. usually used to assign tasks to processors with an appropriate As part of their work, the authors introduce the Real-Time Lazy condition in accordance with the schedulability analysis. In Snapshot Algorithm (LSA-RT) which is a timestamp-based contrast, under the global scheduling approach, inter-processor algorithm using a real-time clock. Moreover it uses a helper migrations are allowed. A single queue and only one policy mechanism to help committing transactions to complete. are applied to tasks. A known result for uniprocessors is However, the timestamp mechanism is not suitable for real- that the scheduling algorithm Earliest Deadline First (EDF) time transactions. Indeed, the timestamp represents the arrival is optimal [21]. Unfortunately, EDF is not optimal on time of a transaction but does not provide any information multiprocessors either under the partitioned or the global about its time constraint. In addition, the conflict resolution is approaches [22], called respectively P-EDF and G-EDF. performed according to the evaluation of the timestamp-based Another class of scheduling algorithms, which differs from age of the transactions and yet, in a real-time context, a recent the previous ones, gathers the Pfair algorithms (namely PD transaction may be of higher priority than an older one. and PD2) [23]. These are based on

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    10 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us