All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: Mala Anand <manand@us.ibm.com>
Cc: Donald Becker <becker@scyld.com>, <linux-net@vger.kernel.org>,
	<linux-net-owner@vger.kernel.org>, <netdev@oss.sgi.com>,
	<pekkas@netcore.fi>
Subject: Re: Network oops
Date: Wed, 12 Jun 2002 10:42:40 -0700 (PDT)	[thread overview]
Message-ID: <ae81bp$q41$2@main.gmane.org> (raw)
In-Reply-To: <OF8ADD9FF7.49EC72C0-ON85256BD6.005CEBAC@raleigh.ibm.com>

On Wed, 12 Jun 2002, Mala Anand wrote:

> >> On Mon, 10 Jun 2002, Mala Anand wrote:
> 
> >>  I have seen this problem with this NIC.  You need to increase
> >> the number of buffers in the RX and TX ring in eepro100.c file.
> >> Right now it is set to 32, change it to 256 or 128 this error
> >> will go away.
> 
> > Donald Becker wrote:
> >Changing the Tx queue size or number of Rx skbuffs waiting to be filled
> >will not fix a problem.  It might mask some problem e.g. a temporary
> >shortage of skbuffs, but it doesn't fix anything.
> 
> The problem what I saw was resource problem and as a result I had packet
> drops.  The
> input rate was high and the driver didn't have enough resources to handle.
> It was a pure resource problem.
> --

I think the problem Donald Becker is referring to is the
fact that it oopses when out of resources, (or whatever),
and that is not a graceful and acceptable thing. Adding
resources pushes the problem to a point under additional
stress/load/consumption. It would be nice if that were
handled gracefully.

thanks,
Nivedita

       reply	other threads:[~2002-06-12 17:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <OF8ADD9FF7.49EC72C0-ON85256BD6.005CEBAC@raleigh.ibm.com>
2002-06-12 17:42 ` Nivedita Singhvi [this message]
2002-06-12 16:58 Network oops Mala Anand
  -- strict thread matches above, loose matches on Subject: below --
2002-06-10 14:42 Mala Anand
2002-06-12  1:35 ` Donald Becker
     [not found] <200205202125.BAA03545@sex.inr.ac.ru>
2002-06-09 17:31 ` george anzinger
     [not found] ` <3D0390E2.1B80ADEE@mvista.com>
2002-06-10  4:31   ` David S. Miller
2002-06-10  4:32   ` David S. Miller
     [not found]   ` <20020609.213150.32126725.davem@redhat.com>
2002-06-10  4:48     ` george anzinger
     [not found]     ` <3D042F8F.72764243@mvista.com>
2002-06-10  5:06       ` David S. Miller
2002-06-20 17:19       ` george anzinger
     [not found]       ` <3D120EAE.5A0D365E@mvista.com>
2002-06-21  0:38         ` David S. Miller
     [not found]         ` <20020620.173805.55219901.davem@redhat.com>
2002-06-21 14:16           ` george anzinger
     [not found]           ` <3D133538.60B6810C@mvista.com>
2002-06-21 14:17             ` David S. Miller
     [not found]             ` <20020621.071720.07439917.davem@redhat.com>
2002-06-21 15:12               ` george anzinger
2002-06-22  0:55             ` Andi Kleen
     [not found]             ` <20020622025551.A1919@averell>
2002-06-28 19:56               ` george anzinger
     [not found]   ` <20020609.213224.01016187.davem@redhat.com>
2002-06-10  8:11     ` george anzinger
     [not found]     ` <3D045F15.578E1DA9@mvista.com>
2002-06-10  8:31       ` David S. Miller
     [not found]       ` <20020610.013110.81671593.davem@redhat.com>
2002-06-10 14:12         ` george anzinger

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='ae81bp$q41$2@main.gmane.org' \
    --to=niv@us.ibm.com \
    --cc=becker@scyld.com \
    --cc=linux-net-owner@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=manand@us.ibm.com \
    --cc=netdev@oss.sgi.com \
    --cc=pekkas@netcore.fi \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.