linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <chuckw@altaserv.net>
To: Scott Laird <laird@internap.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] 2.2.19 -> 80% Packet Loss
Date: Fri, 15 Jun 2001 07:17:54 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.33.0106150711350.20189-100000@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.33.0106141636330.2642-100000@laird.ocp.internap.com>



> You can fix this by upping the socket buffer that ping asks for (look
> for setsockopt( ... SO_RCVBUF ...)) and then tuning the kernel to
> allow larger socket buffers.  The file to fiddle with is
> /proc/sys/net/core/rmem_max.

Currently it is set to 65535. I doubled it several times and each time saw
no change when I sent it a ping flood with packet size 64590 or higher.
What sort of magnitude were you thinking?


> That doesn't really answer why you'd want to fling that many 64k-ish
> ping packets around, though.

No reason specifically other than intuition. Just kinda stumbled on to
this one.

-Chuck


-- 
Chuck Wolber
System Administrator
AltaServ Corporation
(425)576-1202
ten.vresatla@wkcuhc

Quidquid latine dictum sit, altum viditur.


  reply	other threads:[~2001-06-15 14:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-14 21:17 [BUG] 2.2.19 -> 80% Packet Loss chuckw
2001-06-14 23:44 ` Scott Laird
2001-06-15 14:17   ` chuckw [this message]
2001-06-15 17:56     ` Scott Laird
2001-06-15  1:14 ` José Luis Domingo López
2001-06-15  9:12   ` Tim Moore
2001-06-15  9:10 ` Tim Moore

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=Pine.LNX.4.33.0106150711350.20189-100000@localhost.localdomain \
    --to=chuckw@altaserv.net \
    --cc=laird@internap.com \
    --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;
as well as URLs for NNTP newsgroup(s).