From mboxrd@z Thu Jan 1 00:00:00 1970 References: From: Jan Kiszka Message-ID: <571E312A.9040903@siemens.com> Date: Mon, 25 Apr 2016 17:00:58 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai] Philippe Gerum : lib/cobalt: add config switch to enable lazy setsched update mode List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: xenomai@xenomai.org, Philippe Gerum On 2016-04-12 18:45, git repository hosting wrote: > Module: xenomai-3 > Branch: wip/dovetail > Commit: 867070475384652b4e3d4a25f5ad983732a59a7e > URL: http://git.xenomai.org/?p=xenomai-3.git;a=commit;h=867070475384652b4e3d4a25f5ad983732a59a7e > > Author: Philippe Gerum > Date: Sun Mar 20 17:58:33 2016 +0100 > > lib/cobalt: add config switch to enable lazy setsched update mode > > --enable-lazy-setsched should be given for enabling lazy propagation > of scheduling parameters upon calls to pthread_setschedparam*(), > sched_setscheduler(). Defaults to off. Missed this so far: Is there particular reason to keep it off by default? Regression concerns (i.e. this will be only off in the beginning) or downsides of the lazy implementation? Jan -- Siemens AG, Corporate Technology, CT RDA ITP SES-DE Corporate Competence Center Embedded Linux