Linux Newbie help
 help / color / mirror / Atom feed
From: oford <oford@ev1.net>
To: Girish Kale <girish.kale@nevisnetworks.com>
Cc: linux-newbie <linux-newbie@vger.kernel.org>
Subject: Re: Basic questions on the kernel
Date: 30 May 2003 15:10:42 -0500	[thread overview]
Message-ID: <1054325442.12558.43.camel@spider.hotmonkeyporn.com> (raw)
In-Reply-To: <36993D449C7FA647BF43568E0793AB3E061CD9@nevis_pune_xchg.pune.nevisnetworks.com>

[-- Attachment #1: Type: text/plain, Size: 1403 bytes --]

On Fri, 2003-05-30 at 08:00, Girish Kale wrote:
> Hi,
> 
> I have a few basic questions on the kernel performance:
> 
> 1) For embedded systems, even though standard linux may not have hard
> real-time performance unless real-time patch, low latency patch are
> applied, I would like to know if linux can give "deterministic"
> performance. Meaning can we be guaranteed that a particular process will
> be scheduled after a particular time. What are the these times or where
> do I find this data.  
> 
> 2) When we are using linux on an embedded system, will there a memory
> management unit for this, since there will not be any swapping in/out of
> pages? Can we avoid a process from keeping on allocating memory thereby
> starving other applications? 

1) I think your best source of info here is going to be the scheduler
code itself.  You can find lots of information on it by searching the
linux-kernel mailing list archives.  Here is the link:
http://marc.theaimsgroup.com/?l=linux-kernel&r=1&w=2

2) There are MMUs for almost every architecture.  My advice is to email
the kernel maintainer of the architecture you wish to use.  Seek out any
lists that the embedded community uses and I'm sure they will be glad to
assist you.

3) Be prepared to make modifications to the kernel source code to fit
the needs of your specific device.
-- 
Owen Ford <oford@ev1.net>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2003-05-30 20:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-30 13:00 Basic questions on the kernel Girish Kale
2003-05-30 15:21 ` Burton Samograd
2003-05-30 18:16 ` Stephen Samuel
2003-05-30 18:17   ` Paul Kraus
2003-05-30 18:56     ` Ray Olszewski
2003-05-30 20:10 ` oford [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1054325442.12558.43.camel@spider.hotmonkeyporn.com \
    --to=oford@ev1.net \
    --cc=girish.kale@nevisnetworks.com \
    --cc=linux-newbie@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox