From: mru@kth.se (Måns Rullgård)
To: linux-kernel@vger.kernel.org
Subject: Re: Do I need kswapd if I don't have swap?
Date: Sun, 23 Nov 2003 03:10:21 +0100 [thread overview]
Message-ID: <yw1xd6bjbzsi.fsf@kth.se> (raw)
In-Reply-To: m3d6bj3lz6.fsf@bfnet.com
David Wuertele <dave-gnus@bfnet.com> writes:
> I expected this program to malloc most of my embedded MIPS's 32MB of
> system RAM, then eventually return with a -1 or a -2. Unfortunately,
> it hangs having finally printed:
>
> M26916864
> W26916864
> R26916864
>
> The malloc call isn't even returning. What could explain that?
I can't help you there.
> I don't have swap space configured, and I notice several kernel
> threads that I figure might be assuming I have swap. For example:
>
> 3 root S [ksoftirqd_CPU0]
> 4 root S [kswapd]
> 5 root S [bdflush]
> 6 root S [kupdated]
> 7 root S [mtdblockd]
>
> Do I need any of these if I don't have swap? Are there any special
> kernel configs I should be doing if I don't have swap?
Swap space is really just special case of disk caching. Many pages
will be backed by regular files, such as the text segment of most
processes. Swap is used for pages that don't have a corresponding
disk file. Not configuring any swap is perfectly normal, and
shouldn't cause any problems. After all, swap is normally enabled by
some system boot script, so it has to be able to start without any
swap space. For the record, I've been running without swap for a long
time on a system with enough real RAM.
--
Måns Rullgård
mru@kth.se
next prev parent reply other threads:[~2003-11-23 2:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-23 1:35 Do I need kswapd if I don't have swap? David Wuertele
2003-11-23 2:10 ` Måns Rullgård [this message]
2003-11-23 3:22 ` Valdis.Kletnieks
[not found] <URy0.Sx.3@gated-at.bofh.it>
2003-11-24 7:37 ` Ihar 'Philips' Filipau
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=yw1xd6bjbzsi.fsf@kth.se \
--to=mru@kth.se \
--cc=linux-kernel@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