Skip to contentSkip to conversation

Do I need kswapd if I don't have swap?

DISCUSSION David Wuertele 3 participants 3 messages Nov 23, 2003

lore
Share & tools
lore
#0 lore raw

Using 2.4.18 on my 32MB RAM embedded MIPS system, malloc() goes bye-bye:

  /* Malloc as much as possible, then return */
  #include <stdio.h>
  #define UNIT 1024		/* one kilobyte */
  int main ()
  {
    unsigned int j, totalmalloc=0, totalwrote=0, totalread=0;
    while (1) {
      unsigned char *buf = (unsigned char *) malloc (UNIT);
      if (!buf) return 0;
      totalmalloc += UNIT; fprintf (stderr, "%u ", totalmalloc);
      for (j=0; j<UNIT; j++) buf[j] = j % 256;
      totalwrote += UNIT; fprintf (stderr, "%u ", totalwrote);
      for (j=0; j<UNIT; j++) if (buf[j] != (j % 256)) return -1;
      totalread += UNIT; fprintf (stderr, "%u\n", totalread);
    }
  }

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 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?

Thanks,
Dave

#1 lore raw
Quoted 9 lines · David Wuertele

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.

Quoted 11 lines

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.

Signature · 2 lines
Måns Rullgård
[email protected]
#2 lore raw
In reply to David Wuertele
Quoted 10 lines · David Wuertele
    while (1) {
      unsigned char *buf = (unsigned char *) malloc (UNIT);
      if (!buf) return 0;
      totalmalloc += UNIT; fprintf (stderr, "%u ", totalmalloc);
      for (j=0; j<UNIT; j++) buf[j] = j % 256;
      totalwrote += UNIT; fprintf (stderr, "%u ", totalwrote);
      for (j=0; j<UNIT; j++) if (buf[j] != (j % 256)) return -1;
      totalread += UNIT; fprintf (stderr, "%u\n", totalread);
    }
Quoted 3 lines

M26916864
W26916864
R26916864

Hmm.. the output doesn't match the fprintf()s. Doesn't give me warm fuzzies...

Quoted 1 line

The malloc call isn't even returning. What could explain that?

Alternate theory - the last time through the loop, you get to the fprintf() of totalread, you go INTO that call, the output makes it out, but some final malloc() call *within fprintf* or something fails due to being out of memory (or any number of other failure modes due to being almost but not totally out of memory), so you never return to start the next iteration of the loop.