lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <BANLkTimoubhOk3tDwzgAek644C0AUCxN4w@mail.gmail.com>
Date:	Fri, 1 Apr 2011 09:57:12 -0500
From:	Rafael Fernandez <rafaelefernandez@...il.com>
To:	limp <johnkyr83@...mail.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Minimum time slice for relaible Linux execution

Also, how is this different than placing a starvation limit around the
RT set of tasks?

On Fri, Apr 1, 2011 at 9:19 AM, Rafael Fernandez
<rafaelefernandez@...il.com> wrote:
> Hi,
>
> This is pretty interesting to me. How would your framework handle an
> RT application that does quite a bit of I/O? Does it block and go to
> Linux, get serviced, and come back?
>
> Thank you,
> Rafael
>
> On Thu, Mar 31, 2011 at 7:13 AM, limp <johnkyr83@...mail.com> wrote:
>> Dear all,
>>
>> I have developed a framework similar to a hypervisor that switches between
>> Linux and a RT domain.
>> As RT priority is of highest importance, I want to give more time to the RT
>> domain *but* I also want to give Linux adequate time for being able to
>> operate.
>>
>> Could anyone advise me on how to determine the minimum possible time slice
>> that I can give to Linux so that it doesn't crash?
>>
>> That is, if I periodically execute my RT domain every ms and then I switch
>> to Linux, what's the minimum time that should be given to Linux, until the
>> next RT domain execution?
>>
>> NOTE: The RT domain and Linux are not executed concurrently, i.e. the RT
>> domain is executed first and then Linux executes until the next RT domain
>> execution.
>>
>> Thank you all in advance.
>>
>> John K.
>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to majordomo@...r.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at  http://www.tux.org/lkml/
>>
>



-- 
Rafael E. Fernández
B.S. Computer Science
University of Illinois at Urbana-Champaign
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ