From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4BB5B64B.6040803@domain.hid> Date: Fri, 02 Apr 2010 11:18:03 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <20100401230843.GF3755@domain.hid> <4BB53566.3010601@domain.hid> <4BB53643.2080604@domain.hid> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigE4B89364C3D262B97FF7CC85" Sender: jan.kiszka@domain.hid Subject: Re: [Xenomai-help] New scheduler class List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Henri Roosen Cc: xenomai@xenomai.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigE4B89364C3D262B97FF7CC85 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Henri Roosen wrote: > We have the same requirement for which we also have no solution. One > of our threads has a configurable priority of which at the lowest > priority the thread should behave like an idle task that is only > scheduled when all xenomai threads are idle and also the Linux domain > is idle. The thread might use rtdm-drivers and xenomai mutexes and > therefore has to be moved to the Xenomai domain. But then it always > has higher priority than any threads scheduled in linux. That's not true, Xenomai threads can run in non-RT scheduling classes as well. They may just gain RT priority while holding some lock that is requested by a RT thread as well. >=20 > Actually, when seen from the first domain, this requirement would be > solved when we could set a first domain priority for the second > domain... Gilles, is that what is meant by the SCHED_IDLE policy for > Linux? "nice +20", thus a very small CPU share if other task are runnable. Note that "true" SCHED_IDLE, ie. no CPU share if some other task is runnable, could only work if we forbid access to Linux syscalls for such tasks - not feasible. Jan --------------enigE4B89364C3D262B97FF7CC85 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAku1tksACgkQitSsb3rl5xTLHACgrxsABRiTJhy73C+mKQxkMotd aD8AoIZOnGU8cT6gIBxgmu1/BnavmaMj =Cy/B -----END PGP SIGNATURE----- --------------enigE4B89364C3D262B97FF7CC85--