Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.arch.embedded > #29036

Re: Task priorities in non strictly real-time systems

Path csiph.com!fu-berlin.de!uni-berlin.de!news.dfncis.de!not-for-mail
From Hans-Bernhard Bröker <HBBroeker@t-online.de>
Newsgroups comp.arch.embedded
Subject Re: Task priorities in non strictly real-time systems
Date Mon, 6 Jan 2020 18:01:33 +0100
Lines 45
Message-ID <h7h7fdFr0f8U1@mid.dfncis.de> (permalink)
References <qung9m$m79$1@dont-email.me> <qunihq$450$1@dont-email.me> <quradg$h90$1@dont-email.me> <qutd6p$om0$3@dont-email.me> <quttqq$vhf$1@dont-email.me>
Mime-Version 1.0
Content-Type text/plain; charset=iso-8859-15
Content-Transfer-Encoding 7bit
X-Trace news.dfncis.de BHHL0gi0osVLp3eVQu+6NgAJihBozMy1NLTTrr1CgdsECyCU9fCPWgqb9y
Cancel-Lock sha1:Ulr8B47s2Hgf0c0z2lQPXE5Xe20=
Autocrypt addr=HBBroeker@t-online.de; keydata= mQINBFu0018BEAC34KXenx8N+WV5OOk0YGkpMbnplVar2DFCNTIDEYA6d8S84mD2IB6/R29G gmE0NNKwt5C0vFvETkF1K8iZlI6TxzmtmTMqQk5lGWnxbv02EsSJu4drIwQssCfYoZ0y3XhL gUlZa2PrLvrEDI4HHeYCd87xagdsDX2+fBjMMBqnvYgyAU5UOhhG+R6s/8UtHlzyeJTLYXQQ zYcOFpcX3Q7BsDQukVAhh8RW2ss44TrNmyxbd63dWlG7ZgW525PaA02PsHVSLQz7uIg38S/a /wtB6VqzudvYwcekMyM/XSn/bxaUCHcGGfW81Nd2YtxH5HuqGddHuuQF2vFuVrF+8dA/rPdS xUd8ENaP5bueFWg2hWJb7m/uTGHOPNUeITDNLXpIElGZmqchb3j2kkzsebVlsa2BoYWdK4Aa 16gS0TzcgbAaPE5QRyKQlG/KEgUn6NzI2MSMJBilExtqJtw0fdXZzbOE/73XzfGNVCUk+M9l cXi5QLbYz0jSR2vvR/LXMYrnnl5jZ1Kc3ZNQU/8qaIMVreMybnDWaFYkFDscLPva51w04l6g VXDAxnV90YKJVzXJeTZhzNfa8MkNwKOmCTGew3ICP9sxIiodB/Qvgb9IkuYSqE+fGvl+IQzU W5/XhNH3VSyez4gJyluyE3U46CavSBUMAWp18Uy2M3KnlhC5zwARAQABiQI2BCABCAAgFiEE 3P5ZnvmTrXPVietWQAlHONaGBV0FAlu007UCHQIACgkQQAlHONaGBV0sYw//fgA6tFZHIitC slwmSba67gOMgm2PCOipiORpPmZbBYLiaDbfAD9fvO+h6l1+FV2bA/suvUdGrHz+8hEQCiu9 y499OkqgD75+i0JH15kgKlGU8UqXYuC05koPNsiRlpws/xDvg1eLhZaU/gZ/fue5yA6x3uV4 yiWZQ07Y3nSwMe1s3qfjeuCNUbR0ye3up/KG/zvOcVA5fY4hfFvOlHgEineRmGs4UJV2xGpF N7EOF8nk73Je5VnfTat+hZl3xYwCh6P/1ZTWr838kWgekFgZjK/xLzcSZQ6RA5iaCNiWS5sn tMcSKx5Z8nDuD5h9JjCp8BqicIC2jy48idhV5/8+W/WfjPsp1AtrEL+lCdl7/SNRd+pmnJd8 pjpsSLsNYBWSfaIsy4zQZVRhQeRGyNFzX2U4dSjefZLHPwckeMAyEWv7HkMEYztE0+q7lswJ 6hDwroS0ZHxjldZwJywvk7XzhZoePjY6d3ItdoOGNxes4AfIb5KK4maN+RGfw3KlGEmyCvzT Tg/wo7sSci3P7pyQGH9X6kIwstf3yGFYxywMsBnHTJZ8sAyDeSzusH34Eumsbe0/IQhwTbEz UYXP57GKtUzQAIFJWCfbUcjEEr7/jdrC5Jh1U+X5TI655DMb1923TbiACOQ7kz3D/EbizTLD BNL6S8pzo0K8ySa4Rl7GaW60LUhhbnMtQmVybmhhcmQgQnLDtmtlciA8SEJCcm9la2VyQHQt b25saW5lLmRlPokCVAQTAQgAPhYhBNz+WZ75k61z1YnrVkAJRzjWhgVdBQJbtNNfAhsjBQkJ ZgGABQsJCAcCBhUKCQgLAgQWAgMBAh4BAheAAAoJEEAJRzjWhgVdDEAQAIvsqQWAsxStEOHg CNVW+VdQ9qrGuEE3W4y6dgcEZPdZ5GYd8bo2KsasK+Tw/AyNngZF1DaQMiLlCMMO0lfBhiO+ PJl2obGCr60Le7lF3CRPIPFXhSkAnbJm78JWRBbsjURr1SV33zxaru7HBa2CzWBgKRPmxLBx kMMTY1BmK8BcCMJZHlYAmI8mviHqjIMAzal/Aj9buPTTEi7nG4ZzRYp3FPY92Qgr+2QIYyC4 QDwAoXK8k7CgobQgiGwvG25Uc1+crq4b8Y4oidTR7B0vtvsdYjr0Gf+kN2543QLpYZxukTSI Ql3NXbeIyQDcjtbolCK32dQmB/mRNrH926t5BFpVXrBL2rSFm6GHFgnsWDo1ni3aD3dJ1bzq VdQep+6hg37mlvnMY6rf6R+nfR8X+seVwGUjD/NWHjiTqd0r4/ksGsziTMdbBNbd1xyYXjnS x8Le5v0/Kj7VHeJtthJoTqMNiyP9MNmIW6BJ1asLq0zXF54xXYmAKuP8EulXNjRdbq3bU8IA XHMIaWwGAF06M0osMriepc/ZxIUUTiJrZdebKYtwP0OjFQzjppXCey6hsy+YPBGllpB5oqVW JL+v6WuSV4QX9FkG8xo3gUKthVNL6CZGJd0OUdVKO9Qs2IW+hJDWgzZv8fr35llAYfaytMTM 32cebrY51TDin/C0FebruQINBFu0018BEAC5U4t9NV1KNfztf4A0Orbwd0Ws46fXd5EcyQJl 6S15o9NxW0ztyvjwIQg0AK9OjjSTWU4266+dDnfIoM/sP1I/5G3KNtE911Tp4zG022HhxznA e6XsNaNy3MxJOvA7J0faFyHfP3Pqyw6v4f8InLzfJieGwJTc7kgj96J/uwYwLRNsKDiGR+Ns sBzav13GhZuZ55/olxwRdai3AkEpE1tqUel5Z4s05/oIN+jM5WjVyfqJgOOMc7K5rXTmFm/m heNT40g/p+n/U6OX5PEbVH27zj4ytsDRQ5CTf4he4zO+vVeTeW1Z937XZDqkDxNmFwWCMIYw PCLZkodMmgsOlX+JMzjbrHIAAdreUFBwU8RxV3++y7QrWaf0dJmt6VXSFp8KzwL3vOFDdAwk OCw2Nxg6e9InztARkecuEbmouVIrNZ+DOwwx1f5qpkzaoAso8fyy5m+lVASAEwwg8DdaDpoK bo96e/HAmU1uND1N3F1bn8h0ivbkV6JMlJVqABl6nosZVuNW7k8U3XMxyQhXNzrCaQCEU3y/ 0sSl8rOdlgQOns+VYDInbv3n0t0UtMdNHFSPQqi+U4jUzLo/b62dc3LrMbA+GBaE9a2lDjJ3 o1x0P3i8oD3Ag7yWDr3uDWDqf9YILTjS4/GzDuAk56rQVc4QWtmUjRWQhj8XJCrWtQkXGwAR AQABiQI8BBgBCAAmFiEE3P5ZnvmTrXPVietWQAlHONaGBV0FAlu0018CGwwFCQlmAYAACgkQ QAlHONaGBV18shAAo+6lVAJkN8oe3rUMLx0uqQtqdskcQw3s2I9z9zsJQv24bMzTv7LYPcJa pu+JkdAVUe1CeQoNQaef8ec9B16Lidpt395LWKESoMasxSP/3DII1uuoyo6wouwIW1PsbBWV /4rdCjDdjqJFo/iTs+PKjZnrGmfwnOgr1OmbbwfCjNbgtHnEQ5UmSJ8B3LrY5+Oyav0wXb4j SlsEGzfPDwkcu4o5lBA0DUBGZgrj1GLpxbqRIvLWl8MbOWBukWFpXxs+Jmi2hZxBBSHc9u4z BVXf+YUejY9/DGsx38MP1O7FIX5dGrYxqnQIjsGtqDvgBQ5ctOufsU4VU+4Sw1JQmE02/4xa 02kfokDzlNF148WCyg5k+0rE+XkAFbVjy4TWHS2IYa9agSQnWc8GXV4jjDCeRMwZKOJq0Bux ExlUPGmviALMovHnE0V4RhheTPbaIIrvErL0vNZ/C5Ef69ciy/09ilyigYv5Kf9P59T7sv3E O/Jx+VWs2ZHTmIOI5RggTZfh1jqjHVf/DDGcwDLWFwEtefg8jO8CnF/K3XGVdjRYBOnKL4ao tqDMPJrR5d0JKgzxrCCkp76fz9pZB60XhZaEM8iZkUknulrSOVS+RQfatpLtc6I4laf39mNi gJAx91jvpaTwvVMGZIcA3S+710LmNl+X+lWyymh9srSllmrjmCM=
User-Agent Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.3.1
In-Reply-To <quttqq$vhf$1@dont-email.me>
Content-Language de-DE
Xref csiph.com comp.arch.embedded:29036

Show key headers only | View raw

Am 06.01.2020 um 01:08 schrieb Don Y:

> Preemptive frameworks can be implemented in a variety of ways.
> It need NOT mean that the processor can be pulled out from under
> your feet at any "random" time.

I think I have to disagree with that.

Let's start with linguistics.  To "preempt" means: to get in ahead of
someone (or something) else.

In the RT world, that something is a running task, and preemption
happens when some other task gets to use the CPU before that task is
done with it.  I.e. a preemptive framework, pretty much by definition of
the words, does pull the CPU out from under you, and that _will_ happen
at, essentially, random times.

If the running task can routinely (as opposed to exceptionally) avoid
that happening to itself, that means it's essentially the other type of
framework: a cooperative one.

In other words: for the distinction of preemptive vs. cooperative
multitasking to make any sense at all, it has to be about who routinely
gets to decide whether task switching is allowed at any given time.  If
the decision normally is with individual tasks, that's cooperative.  If
it's centralized in the OS, that's preemptive.

Now we in c.a.embedded don't usually get to make that distinction quite
so cleanly of course, because for us, ISRs are a fact of life, and those
are always preemptive.  So purely cooperative multitasking is out.  We
only get to decide between largely cooperative systems with some
preemptive task disturbing the "clean" picture, and almose purely
preemptive system setups, with all the extra cost in terms of data
exchange synchronization between tasks that entails.


> So, barring "events" signalled by an ISR, you can conceivably
> execute code inside a single task for DAYS and never lose control of
> the processor.

And still, when eventually you do lose it, the time when that happens
is, for all practical intents and purposes, random.  Because otherwise
you wouldn't "lose" control, you'ld be "giving it up".   In other words,
in such a case the used RTOS framework may be preemptive, but you're not
using it that way.

Back to comp.arch.embedded | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Task priorities in non strictly real-time systems pozz <pozzugno@gmail.com> - 2020-01-03 14:41 +0100
  Re: Task priorities in non strictly real-time systems David Brown <david.brown@hesbynett.no> - 2020-01-03 15:19 +0100
    Re: Task priorities in non strictly real-time systems pozz <pozzugno@gmail.com> - 2020-01-05 01:25 +0100
      Re: Task priorities in non strictly real-time systems Les Cargill <lcargill99@comcast.com> - 2020-01-05 13:32 -0600
        Re: Task priorities in non strictly real-time systems Richard Damon <Richard@Damon-Family.org> - 2020-01-05 16:49 -0500
          Re: Task priorities in non strictly real-time systems Les Cargill <lcargill99@comcast.com> - 2020-01-05 21:05 -0600
        Re: Task priorities in non strictly real-time systems Don Y <blockedofcourse@foo.invalid> - 2020-01-05 17:08 -0700
          Re: Task priorities in non strictly real-time systems Les Cargill <lcargill99@comcast.com> - 2020-01-05 21:26 -0600
            Re: Task priorities in non strictly real-time systems Don Y <blockedofcourse@foo.invalid> - 2020-01-05 22:10 -0700
              Re: Task priorities in non strictly real-time systems Les Cargill <lcargill99@comcast.com> - 2020-01-06 07:37 -0600
                Re: Task priorities in non strictly real-time systems Don Y <blockedofcourse@foo.invalid> - 2020-01-06 17:21 -0700
                Re: Task priorities in non strictly real-time systems Les Cargill <lcargill99@comcast.com> - 2020-01-07 19:23 -0600
              Re: Task priorities in non strictly real-time systems Richard Damon <Richard@Damon-Family.org> - 2020-01-06 20:36 -0500
                Re: Task priorities in non strictly real-time systems Les Cargill <lcargill99@comcast.com> - 2020-01-07 01:38 -0600
                Re: Task priorities in non strictly real-time systems Richard Damon <Richard@Damon-Family.org> - 2020-01-07 06:53 -0500
            Re: Task priorities in non strictly real-time systems George Neuner <gneuner2@comcast.net> - 2020-01-06 07:13 -0500
            Re: Task priorities in non strictly real-time systems David Brown <david.brown@hesbynett.no> - 2020-01-07 10:11 +0100
              Re: Task priorities in non strictly real-time systems Richard Damon <Richard@Damon-Family.org> - 2020-01-07 07:05 -0500
              Re: Task priorities in non strictly real-time systems Les Cargill <lcargill99@comcast.com> - 2020-01-07 19:34 -0600
          Re: Task priorities in non strictly real-time systems upsidedown@downunder.com - 2020-01-06 10:44 +0200
            Re: Task priorities in non strictly real-time systems Don Y <blockedofcourse@foo.invalid> - 2020-01-06 02:51 -0700
              Re: Task priorities in non strictly real-time systems upsidedown@downunder.com - 2020-01-06 15:39 +0200
                Re: Task priorities in non strictly real-time systems George Neuner <gneuner2@comcast.net> - 2020-01-06 13:29 -0500
                Re: Task priorities in non strictly real-time systems Don Y <blockedofcourse@foo.invalid> - 2020-01-06 14:38 -0700
                Re: Task priorities in non strictly real-time systems upsidedown@downunder.com - 2020-01-07 07:05 +0200
                Re: Task priorities in non strictly real-time systems George Neuner <gneuner2@comcast.net> - 2020-01-07 13:09 -0500
                Re: Task priorities in non strictly real-time systems Dimiter_Popoff <dp@tgi-sci.com> - 2020-01-07 20:53 +0200
                Re: Task priorities in non strictly real-time systems Clifford Heath <no.spam@please.net> - 2020-01-08 08:43 +1100
                Re: Task priorities in non strictly real-time systems upsidedown@downunder.com - 2020-01-08 00:33 +0200
                Re: Task priorities in non strictly real-time systems Dimiter_Popoff <dp@tgi-sci.com> - 2020-01-08 15:26 +0200
                Re: Task priorities in non strictly real-time systems upsidedown@downunder.com - 2020-01-08 00:08 +0200
                Re: Task priorities in non strictly real-time systems David Brown <david.brown@hesbynett.no> - 2020-01-07 10:37 +0100
                Re: Task priorities in non strictly real-time systems Don Y <blockedofcourse@foo.invalid> - 2020-01-06 16:10 -0700
                Re: Task priorities in non strictly real-time systems upsidedown@downunder.com - 2020-01-07 07:37 +0200
                Re: Task priorities in non strictly real-time systems Les Cargill <lcargill99@comcast.com> - 2020-01-07 01:49 -0600
                Re: Task priorities in non strictly real-time systems Don Y <blockedofcourse@foo.invalid> - 2020-01-07 06:43 -0700
                Re: Task priorities in non strictly real-time systems upsidedown@downunder.com - 2020-01-07 10:21 +0200
                Re: Task priorities in non strictly real-time systems Don Y <blockedofcourse@foo.invalid> - 2020-01-07 06:42 -0700
                Re: Task priorities in non strictly real-time systems Richard Damon <Richard@Damon-Family.org> - 2020-01-07 22:23 -0500
                Re: Task priorities in non strictly real-time systems upsidedown@downunder.com - 2020-01-09 22:07 +0200
                Re: Task priorities in non strictly real-time systems upsidedown@downunder.com - 2020-01-07 10:54 +0200
                Re: Task priorities in non strictly real-time systems Don Y <blockedofcourse@foo.invalid> - 2020-01-07 06:43 -0700
          Re: Task priorities in non strictly real-time systems Hans-Bernhard Bröker <HBBroeker@t-online.de> - 2020-01-06 18:01 +0100
            Re: Task priorities in non strictly real-time systems Niklas Holsti <niklas.holsti@tidorum.invalid> - 2020-01-06 19:47 +0200
    Re: Task priorities in non strictly real-time systems pozz <pozzugno@gmail.com> - 2020-01-05 01:58 +0100
      Re: Task priorities in non strictly real-time systems Clifford Heath <no.spam@please.net> - 2020-01-05 14:26 +1100
        Re: Task priorities in non strictly real-time systems upsidedown@downunder.com - 2020-01-05 11:21 +0200
          Re: Task priorities in non strictly real-time systems David Brown <david.brown@hesbynett.no> - 2020-01-05 14:07 +0100
            Re: Task priorities in non strictly real-time systems upsidedown@downunder.com - 2020-01-05 17:46 +0200
              Re: Task priorities in non strictly real-time systems David Brown <david.brown@hesbynett.no> - 2020-01-05 19:08 +0100
        Re: Task priorities in non strictly real-time systems David Brown <david.brown@hesbynett.no> - 2020-01-05 13:56 +0100
        Re: Task priorities in non strictly real-time systems Les Cargill <lcargill99@comcast.com> - 2020-01-05 13:39 -0600
          Re: Task priorities in non strictly real-time systems Clifford Heath <no.spam@please.net> - 2020-01-06 07:44 +1100
            Re: Task priorities in non strictly real-time systems Les Cargill <lcargill99@comcast.com> - 2020-01-05 21:00 -0600
              Re: Task priorities in non strictly real-time systems Clifford Heath <no.spam@please.net> - 2020-01-06 14:50 +1100
                Re: Task priorities in non strictly real-time systems Les Cargill <lcargill99@comcast.com> - 2020-01-06 07:12 -0600
      Re: Task priorities in non strictly real-time systems Paul Rubin <no.email@nospam.invalid> - 2020-01-04 22:34 -0800
        Re: Task priorities in non strictly real-time systems David Brown <david.brown@hesbynett.no> - 2020-01-05 14:12 +0100
          Re: Task priorities in non strictly real-time systems Niklas Holsti <niklas.holsti@tidorum.invalid> - 2020-01-05 18:00 +0200
        Re: Task priorities in non strictly real-time systems Les Cargill <lcargill99@comcast.com> - 2020-01-05 13:44 -0600
      Re: Task priorities in non strictly real-time systems George Neuner <gneuner2@comcast.net> - 2020-01-06 14:52 -0500
      Re: Task priorities in non strictly real-time systems George Neuner <gneuner2@comcast.net> - 2020-01-06 15:05 -0500
        Re: Task priorities in non strictly real-time systems gtwrek@sonic.net (gtwrek) - 2020-01-06 22:41 +0000
        Re: Task priorities in non strictly real-time systems Don Y <blockedofcourse@foo.invalid> - 2020-01-06 19:50 -0700
          Re: Task priorities in non strictly real-time systems George Neuner <gneuner2@comcast.net> - 2020-01-07 13:26 -0500
  Re: Task priorities in non strictly real-time systems Niklas Holsti <niklas.holsti@tidorum.invalid> - 2020-01-03 16:28 +0200
    Re: Task priorities in non strictly real-time systems pozz <pozzugno@gmail.com> - 2020-01-05 01:37 +0100
      Re: Task priorities in non strictly real-time systems Les Cargill <lcargill99@comcast.com> - 2020-01-05 13:46 -0600
        Re: Task priorities in non strictly real-time systems Niklas Holsti <niklas.holsti@tidorum.invalid> - 2020-01-05 22:44 +0200
  Re: Task priorities in non strictly real-time systems Rick C <gnuarm.deletethisbit@gmail.com> - 2020-01-03 11:49 -0800
  Re: Task priorities in non strictly real-time systems upsidedown@downunder.com - 2020-01-03 22:51 +0200
    Re: Task priorities in non strictly real-time systems pozz <pozzugno@gmail.com> - 2020-01-05 01:48 +0100
  Re: Task priorities in non strictly real-time systems Joe Chisolm <jchisolm6@earthlink.net> - 2020-01-03 15:34 -0600
  Re: Task priorities in non strictly real-time systems Richard Damon <Richard@Damon-Family.org> - 2020-01-03 21:46 -0500

csiph-web