From: Ben Greear <greearb@candelatech.com>
To: "David S. Miller" <davem@redhat.com>
Cc: felix@allot.com, netdev@oss.sgi.com
Subject: Re: Ethernet bridge performance
Date: Thu, 07 Aug 2003 12:50:53 -0700 [thread overview]
Message-ID: <3F32AD9D.4010504@candelatech.com> (raw)
In-Reply-To: <20030807123547.1dcf2353.davem@redhat.com>
David S. Miller wrote:
> On Thu, 07 Aug 2003 09:57:14 -0700
> Ben Greear <greearb@candelatech.com> wrote:
>
>
>>Btw, I've considered saving, say, 10k skbs on a list in my module,
>>allocated by GFP_KERNEL at module load time, and using them when
>>GFP_ATOMIC skb_alloc fails in the IRQ handling portion of the code....
>>
>>Anyone think that's a good idea? :)
>
>
> Not really.
>
> GFP_ATOMIC should not fail regularly under normal (even heavy load)
> operation. If it does, it means the amount of reserved pages
> the kernel keeps around is not set correctly for your system.
>
> In 2.6.x, play with /proc/sys/vm/min_free_kbytes
Anything to set for 2.4? I've looked for how to tune the 2.4 VM for
some time, but never found anything.
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2003-08-07 19:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 9:12 Ethernet bridge performance Felix Radensky
2003-08-07 15:59 ` Stephen Hemminger
2003-08-07 16:05 ` Felix Radensky
2003-08-07 16:57 ` Ben Greear
2003-08-07 17:19 ` Felix Radensky
2003-08-07 19:09 ` Robert Olsson
2003-08-07 19:21 ` jamal
2003-08-07 22:49 ` Robert Olsson
2003-08-10 7:32 ` Felix Radensky
2003-08-11 2:55 ` jamal
2003-08-11 7:52 ` Robert Olsson
[not found] ` <3F3601F3.6000001@allot.com>
2003-08-10 18:13 ` Ben Greear
2003-08-10 19:47 ` Andi Kleen
2003-08-10 21:49 ` Robert Olsson
2003-08-07 19:35 ` David S. Miller
2003-08-07 19:50 ` Ben Greear [this message]
2003-08-07 19:58 ` David S. Miller
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=3F32AD9D.4010504@candelatech.com \
--to=greearb@candelatech.com \
--cc=davem@redhat.com \
--cc=felix@allot.com \
--cc=netdev@oss.sgi.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).