mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Danial Thom <danial_thom@yahoo.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Dropping Packets in 2.6.17
Date: Thu, 22 Jun 2006 05:47:00 -0700 (PDT)	[thread overview]
Message-ID: <20060622124700.4700.qmail@web33314.mail.mud.yahoo.com> (raw)
In-Reply-To: <1150977316.3120.26.camel@laptopd505.fenrus.org>



--- Arjan van de Ven <arjan@infradead.org> wrote:

> On Thu, 2006-06-22 at 04:31 -0700, Danial Thom
> wrote:
> > I'm trying to make a case for using linux as
> a
> > network appliance, but I can't find any
> > combination of settings that will keep it
> from
> > dropping packets at an unacceptably high
> rate.
> > The test system is a 1.8Ghz Opteron with
> intel
> > gigE cards running 2.6.17. I'm passing about
> 70K
> > pps through the box, which is a light load,
> but
> > userland activities (such as building a
> kernel)
> > cause it to lose packets, even with backlog
> set
> > to 20000. I had the same problem with 2.6.12
> and
> > abandoned the effort. Has anything been done
> > since to give priority to networking? You
> can't
> > have a network appliance drop packets when
> some
> > application is gathering stats or a user is
> > looking at a graph. What tunings are
> available?
> 
> Hi Danial,
> 
> the most likely tunable that will help you is
> 
> /proc/sys/vm/min_free_kbytes
> 
> For the router kind of device that one usually
> needs bumping a bit;
> without the bumping the VM doesn't see enough
> "normal" activity to tune
> it's emergency/interrupt handling buffers (and
> most networking
> allocations happen in interrupt context), and
> then ends up failing
> allocations in interrupt context, which leads
> to dropped packets.

I don't think thats the problem, as I've tracked
the problem to packets being dropped because of
excessive backlog (ie, they are being dropped
gracefully). However with a backlog of 20000, and
a traffic level of about 75,000pps, that means
almost 1/3 of a second that the system doesn't
process packets, which is just unacceptable.

I'll try changing the setting, but running out of
memory doesn't seem to be the issue. I think what
I need is some mechanism to make interrupts a
priority, like it was back in the days when
networking was more important then mp3 playback.

Danial

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

  reply	other threads:[~2006-06-22 12:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-22 11:31 Danial Thom
2006-06-22 11:55 ` Arjan van de Ven
2006-06-22 12:47   ` Danial Thom [this message]
2006-06-22 13:27 ` Pádraig Brady
2006-06-22 14:01   ` Miquel van Smoorenburg
2006-06-22 14:15     ` Pádraig Brady
2006-06-22 15:03   ` Danial Thom
2006-06-22 15:26     ` Pádraig Brady
2006-06-22 17:10       ` Danial Thom
     [not found] <fa.zPWsMAz4l0d9j5Voaw6Pdkcf//M@ifi.uio.no>
     [not found] ` <fa.Ze3oSnDYEMz3/ITqeLQ2m0GF5wk@ifi.uio.no>
2006-06-23  1:13   ` Robert Hancock
2006-06-23  7:31     ` Brian F. G. Bidulock
2006-06-23 19:48     ` Danial Thom

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=20060622124700.4700.qmail@web33314.mail.mud.yahoo.com \
    --to=danial_thom@yahoo.com \
    --cc=arjan@infradead.org \
    --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®