Notice: We have migrated to GitLab launching 2024-05-01 see here: https://gitlab.rtems.org/

Opened on 03/07/16 at 07:22:11

Closed on 11/29/17 at 07:16:52

#2628 closed enhancement (wontfix)

Avoid home-grown condition variable implementation in the Classic Regions

Reported by: Sebastian Huber Owned by: Sebastian Huber
Priority: normal Milestone: 5.1
Component: score Version:
Severity: normal Keywords:
Cc: Blocked By:
Blocking:

Description

The Classic Region manager enables users to wait until memory is available to satisfy an allocation request. This is done through special purpose code that basically implements a condition variable.

Change History (5)

comment:1 Changed on 03/07/16 at 07:29:10 by Sebastian Huber

Depends on #2629.

comment:2 Changed on 05/11/17 at 07:31:02 by Sebastian Huber

Milestone: 4.12 → 4.12.0

comment:3 Changed on 05/11/17 at 07:42:40 by Sebastian Huber

Milestone: 4.12.0 → 5.0

comment:4 Changed on 08/14/17 at 00:47:54 by Chris Johns

Milestone: 5.0 → Indefinite
Version: 4.10

comment:5 Changed on 11/29/17 at 07:16:52 by Sebastian Huber

Milestone: Indefinite → 5.1
Resolution: → wontfix
Status: new → closed

The region can be configured to let threads wait in FIFO or priority order. The self-contained condition variables do not support this. Keep this special case implementation as is.

Note: See TracTickets for help on using tickets.