> Generally real-time applications should not be doing mlock calls during
> their real-time execution for that reason. The required memory regions
> should be locked during startup so that this kind of execution delay can
> be avoided at runtime.
Total agreement on this.
.
Regards,
Bud Da
-Original Message-
From: Andy Lutomirski [mailto:l...@amacapital.net]
Sent: Wednesday, March 26, 2014 7:40 PM
To: Davis, Bud @ SSG - Link; umgwanakikb...@gmail.com
Cc: oneu...@suse.de; artem_fetis...@epam.com; pet...@infradead.org;
kosaki.motoh...@jp.fujitsu.com; linux-kernel@vger.kerne
From: Mike Galbraith [umgwanakikb...@gmail.com]
Sent: Friday, March 21, 2014 9:41 AM
To: Davis, Bud @ SSG - Link
Cc: oneu...@suse.de; artem_fetis...@epam.com; pet...@infradead.org;
kosaki.motoh...@jp.fujitsu.com; linux-kernel@vger.kernel.org
Subject: RE: B
From: Mike Galbraith [umgwanakikb...@gmail.com]
Sent: Friday, March 21, 2014 8:14 AM
To: Davis, Bud @ SSG - Link
Cc: artem_fetis...@epam.com; pet...@infradead.org;
kosaki.motoh...@jp.fujitsu.com; linux-kernel@vger.kernel.org
Subject: RE: Bug 71331 - mlock
From: Oliver Neukum [oneu...@suse.de]
Sent: Friday, March 21, 2014 8:35 AM
To: Davis, Bud @ SSG - Link
Cc: umgwanakikb...@gmail.com; artem_fetis...@epam.com; pet...@infradead.org;
kosaki.motoh...@jp.fujitsu.com; linux-kernel@vger.kernel.org
Subject: Re: Bu
>How is that different from any other time a task has to yield the CPU
>for a bit? While your high priority task is blocked for whatever
>reason, a lower priority task gets to use the CPU.
As the submitter of the bug, let me give you my perspective. SCHED_FIFO means
run my task until it bl
6 matches
Mail list logo
