public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <dada1@cosmosbay.com>
To: "Zhao Xiaoming" <xiaoming.nj@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ZONE_NORMAL memory exhausted by 4000 TCP sockets
Date: Mon, 6 Nov 2006 09:48:42 +0100	[thread overview]
Message-ID: <200611060948.43918.dada1@cosmosbay.com> (raw)
In-Reply-To: <f55850a70611060010q3ce9d6d2h4026259d688c6db1@mail.gmail.com>

On Monday 06 November 2006 09:10, Zhao Xiaoming wrote:
>
> Thanks for the answer. I know it's more likely relats to netdev.
> However, it's always a strange thing to have 400~500M bytes LOWMEM
> 'gone' while it's not reported to be occupied by slab. Both meminfo
> and buddyinfo tell the same.
>
> with traffics of 2000 concurrent sessions:

Slab:           293952 kB
So 292 MB used by slab for 2000 sessions.

Expect 600 MB used by slab for 4000 sessions.

So your precious LOWMEM is not gone at all. It *IS* used by SLAB.

You forgot to send 
cat /proc/slabinfo

>
> cat /proc/meminfo
> MemTotal:      4136580 kB
> MemFree:       3298460 kB
> Buffers:          4096 kB
> Cached:          21124 kB
> SwapCached:          0 kB
> Active:          47416 kB
> Inactive:        12532 kB
> HighTotal:     3276160 kB
> HighFree:      3214592 kB
> LowTotal:       860420 kB
> LowFree:         83868 kB
> SwapTotal:           0 kB
> SwapFree:            0 kB
> Dirty:              12 kB
> Writeback:           0 kB
> Mapped:          42104 kB
> Slab:           293952 kB
> CommitLimit:   2068288 kB
> Committed_AS:    58892 kB
> PageTables:       1112 kB
> VmallocTotal:   116728 kB
> VmallocUsed:      2940 kB
> VmallocChunk:   110548 kB
> HugePages_Total:     0
> HugePages_Free:      0
> Hugepagesize:     2048 kB
>
>

  reply	other threads:[~2006-11-06  8:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-06  6:07 ZONE_NORMAL memory exhausted by 4000 TCP sockets Zhao Xiaoming
2006-11-06  7:34 ` Eric Dumazet
2006-11-06  8:10   ` Zhao Xiaoming
2006-11-06  8:48     ` Eric Dumazet [this message]
2006-11-06  9:03       ` Zhao Xiaoming
2006-11-06  8:59   ` Zhao Xiaoming
2006-11-06  9:22     ` Eric Dumazet
2006-11-06  9:46       ` Zhao Xiaoming
2006-11-06  9:49         ` Zhao Xiaoming
2006-11-06 13:33         ` Eric Dumazet
2006-11-07  2:48           ` Zhao Xiaoming
2006-11-07  5:53             ` Eric Dumazet
2006-11-07  6:08               ` Zhao Xiaoming
2006-11-06 16:36   ` Stephen Hemminger
2006-11-07  2:50     ` Zhao Xiaoming
2006-11-07  6:00       ` Zhao Xiaoming
2006-11-06 10:13 ` Arjan van de Ven
2006-11-06 10:21   ` Zhao Xiaoming
2006-11-06 10:21     ` Zhao Xiaoming
  -- strict thread matches above, loose matches on Subject: below --
2006-11-07  8:06 Al Boldi

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=200611060948.43918.dada1@cosmosbay.com \
    --to=dada1@cosmosbay.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xiaoming.nj@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox