archive mirror
 help / color / mirror / Atom feed
From: Michal Margula <>
Subject: Summary of Error no buffer space available
Date: Wed, 13 Jun 2001 11:52:27 +0200	[thread overview]
Message-ID: <> (raw)


I got plenty of replies. Thanks. Playing with
/proc/sys/net/ipv4/neigh/default/gc_thresh{2,3} helped. The funny thing
is that there are no more ENOBUFS problems - I am guessing that in
2.2.19 buffer of TCP is bigger than in 2.4.x, or something...

People asked me about more details of oopses I had with 2.4.5. Sorry I
don't have any data that could help and I won't try 2.4.x again, until 2.4.20 comes out :)

Andi Kleen said that my problems with 2.4.x and ENOBUFS should be fixed
after changing some things in /proc/sys/net/ipv4/tcp_mem, net/core/[rw]mem_{max,default}.

Thank you once again :)

Michal Margula,, ICQ UIN 12267440, +), Polish section of Linux Counter maintainer

                 reply	other threads:[~2001-06-13  9:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \
    --subject='Re: Summary of Error no buffer space available' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).