From: Bernd Eckenfels <ecki@lina.inka.de>
To: linux-kernel@vger.kernel.org
Subject: Re: VM tuning for Linux routers
Date: Tue, 20 Nov 2001 21:35:48 +0100 [thread overview]
Message-ID: <E166HcS-0001lw-00@calista.inka.de> (raw)
In-Reply-To: <20011118145400.A23181@se1.cogenit.fr>
In article <20011118145400.A23181@se1.cogenit.fr> you wrote:
> Think about forwarding between GigaE and FastE. Think about overflow and
> bad irq latency. I wouldn't cut buffering at l2 as it averages the peaks.
> Different trade-offs make sense of course.
I think in that case increasing the buffers is important:
net.core.rmem_max=262144
net.core.wmem_max=262144
default:
optmem_max:10240
rmem_default:65535
rmem_max:65535
wmem_default:65535
wmem_max:65535
Greetings
Bernd
next prev parent reply other threads:[~2001-11-20 20:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-16 8:03 Jan Kasprzak
2001-11-17 12:41 ` Francois Romieu
2001-11-17 16:42 ` Bernd Eckenfels
2001-11-18 13:54 ` Francois Romieu
2001-11-20 3:29 ` Bernd Eckenfels
2001-11-20 18:58 ` Francois Romieu
2001-11-20 20:35 ` Bernd Eckenfels [this message]
2001-11-20 21:47 ` Francois Romieu
2001-11-22 8:23 ` Jan Kasprzak
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=E166HcS-0001lw-00@calista.inka.de \
--to=ecki@lina.inka.de \
--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
all inboxes | Powered by JetHome®