From: "Paul Kraus" <pkraus@pelsupply.com>
To: 'Stephen Samuel' <samuel@bcgreen.com>,
'Girish Kale' <girish.kale@nevisnetworks.com>,
linux-newbie@vger.kernel.org
Subject: RE: Basic questions on the kernel
Date: Fri, 30 May 2003 14:17:51 -0400 [thread overview]
Message-ID: <001001c326d7$cba92570$64fea8c0@pkraus> (raw)
In-Reply-To: <3ED7A000.80103@bcgreen.com>
I unsubbed from this list a month ago and I still get messages. Not as
many but I still get them.
-----Original Message-----
From: linux-newbie-owner@vger.kernel.org
[mailto:linux-newbie-owner@vger.kernel.org] On Behalf Of Stephen Samuel
Sent: Friday, May 30, 2003 1:17 PM
To: Girish Kale; linux-newbie@vger.kernel.org
Subject: Re: Basic questions on the kernel
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.
You can only get "deterministic" performance if you're using a real-time
patch. I'm not sure what the timing is, but I believe that it's in the
sub-milisecond range.
You might be able to get near-realtime (but no absolute guarantees) by
setting the process that needs fast response to nice -20 this gives it
highest priority, so that it gets CPU pretty much whenever it wants it
(after device drivers).
>
> 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?
Linux generally wants an MMU. Embeded kernels MAY be able to survive
without one (dunno).
Check the setrlimit call, or the ulimit bash built=in for info on how to
set resource usage limits.
You can also set limits on a system-wide basis by using the /proc
mechanisms. (your system probably has a formalized way of doing that
automatically on boot.. for RedHat, that would be the file
/etc/sysctl.conf )
--
Stephen Samuel +1(604)876-0426 samuel@bcgreen.com
http://www.bcgreen.com/~samuel/
Powerful committed communication, reaching through fear, uncertainty and
doubt to touch the jewel within each person and bring it to life.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie"
in the body of a message to majordomo@vger.kernel.org More majordomo
info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2003-05-30 18:17 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 [this message]
2003-05-30 18:56 ` Ray Olszewski
2003-05-30 20:10 ` oford
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='001001c326d7$cba92570$64fea8c0@pkraus' \
--to=pkraus@pelsupply.com \
--cc=girish.kale@nevisnetworks.com \
--cc=linux-newbie@vger.kernel.org \
--cc=samuel@bcgreen.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.