From: Christopher Chan <cchan@outblaze.com>
To: Nivedita Singhvi <niv@us.ibm.com>
Cc: netdev@oss.sgi.com, Yusuf Goolamabbas <yusufg@outblaze.com>
Subject: Re: High number of concurrent connections causes 2.6.4 to go berserk
Date: Sat, 03 Apr 2004 00:37:21 +0800 [thread overview]
Message-ID: <406D96C1.2000901@outblaze.com> (raw)
In-Reply-To: <406CDDF5.4070500@us.ibm.com>
>> The below values seem to workaround whatever problem the kernel has.
>>
>> tcp_max_syn_backlog = 2048
>> route.max_size = 1048576
>> route.gc_thresh = 65536
I take that back. Under peak hours, the kernel starts spewing its stuff
onto serial console and network connectivity is lost.
What it spews is not human readable anymore.
eg:
3->g:asag6A &| <ilfart/tv4d_>rKEt d n SE1PERUELnet p-15 ( t bL:(D3laEED1
f))sspv/ipi
3->g:asag6A &| <3leaititv4d_>r<3_npiti (q G__TRNtd (c p.
=msRN||E1(f_P33KNC: t/ne>c7116p-ug ala7gsK 2
a) sev4ipie<6)
: ssgsA & M3>ediliocp/tsre3>nxieio(M E_PTRNE na(t (.c==sgNE|
1DflPE3D)C) a/ietco1)63->g:asag6A |
ai fer4/pved6>
cvcses s MMS>Kd leonp.tceqc>KxtedonMSE1PERUELnet p(1c = g EL (D3laEED1
f)asipt/op)
3->g:asag6A |
ai fer4/pved6>
cvcoes s MMS>Kd leonp.tceqc>KxtedonMSE1PERUELnet p-1c = g EL (D3laEED1
f))sipt/op)
3->g:asag6A &| <ilfart/tv4d_>r<3_npiti eqSGG_ERatd (ccpq vmER | E
(G_D3EKNC:et n->57(1tpbu: fl37gsK12fa) sev4ipie<6)
c csesA & M3>ediliocp/tseec>nxieio(M E_PTRNE nattp(.c==sgNE| 1DflPE3D)
))asietco1)63->g:asag6A &| <ilfart/tv4d_>r<3_npiti eqSGG_ERatd (c p.
=msRN| E (G_D3EKNC: t/ne>c711tpbu: fl37gsK 2
a) sev4ipi
prev parent reply other threads:[~2004-04-02 16:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-02 0:57 High number of concurrent connections causes 2.6.4 to go berserk Christopher Chan
2004-04-02 3:28 ` Nivedita Singhvi
2004-04-02 4:00 ` Christopher Chan
2004-04-02 16:37 ` Christopher Chan [this message]
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=406D96C1.2000901@outblaze.com \
--to=cchan@outblaze.com \
--cc=netdev@oss.sgi.com \
--cc=niv@us.ibm.com \
--cc=yusufg@outblaze.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;
as well as URLs for NNTP newsgroup(s).