From: "Zhao Xiaoming" <xiaoming.nj@gmail.com>
To: "Eric Dumazet" <dada1@cosmosbay.com>
Cc: linux-kernel@vger.kernel.org,
"Linux Netdev List" <netdev@vger.kernel.org>
Subject: Re: ZONE_NORMAL memory exhausted by 4000 TCP sockets
Date: Tue, 7 Nov 2006 14:08:31 +0800 [thread overview]
Message-ID: <f55850a70611062208l214c1a62vc8ec9133eaca2e5e@mail.gmail.com> (raw)
In-Reply-To: <45501F60.4070606@cosmosbay.com>
On 11/7/06, Eric Dumazet <dada1@cosmosbay.com> wrote:
> Zhao Xiaoming a écrit :
> > On 11/6/06, Eric Dumazet <dada1@cosmosbay.com> wrote:
> >> In fact, your kernel has CONFIG_4KSTACKS, kernel thread stacks use 4K
> >> instead
> >> of 8K.
> >>
> >> If you want to increase LOWMEM, (and keep 32bits kernel), you can chose a
> >> 2G/2G user/kernel split, instead of the 3G/1G default split.
> >> (see config : CONFIG_VMSPLIT_2G)
> >>
> >> Eric
>
> > Thank you for your advice. I know increase LOMEM could be help, but
> > now my concern is why I lose my 500M bytes memory after excluding all
> > known memory cost.
>
> Unfortunatly you dont provide very much details.
> AFAIK you didnt even gave whcih version of linux you run, which programs you
> run...
> You keep answering where you 'lost' your mem, it's quite buging.
> Maybe some Oracles on this list will see the light for you, before exchanging
> 100 mails with you ?
>
>
I think I aready gave the kernel version and introduced my application
in the first post. What are the further details you want? The reason I
keep asking for the 'lost mem' is that I want to focus on the problem,
not the workarrounds that may lead to further problems if I keep
increasing the concurrent scale.
Anyway, since the problem is already solved (see my last post), I'd
like to thank you for the help.
Xiaoming.
next prev parent reply other threads:[~2006-11-07 6:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-06 6:07 Zhao Xiaoming
2006-11-06 7:34 ` Eric Dumazet
2006-11-06 8:10 ` Zhao Xiaoming
2006-11-06 8:48 ` Eric Dumazet
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 [this message]
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
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=f55850a70611062208l214c1a62vc8ec9133eaca2e5e@mail.gmail.com \
--to=xiaoming.nj@gmail.com \
--cc=dada1@cosmosbay.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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
all inboxes | Powered by JetHome®