netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: Denys Fedoryshchenko <denys@visp.net.lb>
Cc: Eric Dumazet <dada1@cosmosbay.com>,
	netdev@vger.kernel.org, linux.nics@intel.com
Subject: Re: packetloss, on e1000e worse than r8169?
Date: Mon, 16 Jun 2008 13:49:26 -0700	[thread overview]
Message-ID: <4856D1D6.7040207@intel.com> (raw)
In-Reply-To: <20080616204411.M52834@visp.net.lb>

Denys Fedoryshchenko wrote:
> [    5.227679] e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k2
> [    5.227681] e1000e: Copyright (c) 1999-2008 Intel Corporation.
> [    5.227724] e1000e 0000:00:19.0: enabling device (0000 -> 0003)
> [    5.227731] ACPI: PCI Interrupt 0000:00:19.0[A] -> GSI 20 (level, low) ->
> IRQ 20
> [    5.227742] PCI: Setting latency timer of device 0000:00:19.0 to 64
> [    5.424362] eth1: (PCI Express:2.5GB/s:Width x1) 00:19:d1:71:5f:33
> [    5.424364] eth1: Intel(R) PRO/1000 Network Connection
> [    5.424385] eth1: MAC: 4, PHY: 6, PBA No: ffffff-0ff
> [    5.985995] warning: `zebra' uses 32-bit capabilities (legacy support in use)
> [    6.337111] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)

disable (all of) netfilter if you don't need it. DEFINATELY do disable
nf_conntrack as it's known problematic for routing performance.

Auke


  parent reply	other threads:[~2008-06-16 20:51 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-16 19:37 packetloss, on e1000e worse than r8169? Denys Fedoryshchenko
2008-06-16 19:48 ` Eric Dumazet
2008-06-16 20:20   ` Denys Fedoryshchenko
2008-06-16 20:23   ` Denys Fedoryshchenko
2008-06-16 20:36     ` Kok, Auke
2008-06-16 20:52       ` Denys Fedoryshchenko
     [not found]       ` <20080616204411.M52834@visp.net.lb>
2008-06-16 20:49         ` Kok, Auke [this message]
2008-06-16 20:59           ` Denys Fedoryshchenko
2008-06-16 21:13           ` Denys Fedoryshchenko
2008-06-16 21:29             ` Eric Dumazet
2008-06-16 21:41               ` Denys Fedoryshchenko
2008-06-16 21:41               ` Denys Fedoryshchenko
     [not found]               ` <20080616213419.M212@visp.net.lb>
2008-06-16 21:41                 ` Eric Dumazet
2008-06-16 21:44                   ` Eric Dumazet
2008-06-16 22:08                     ` Denys Fedoryshchenko
2008-06-17  2:17                       ` Eric Dumazet
2008-06-17  2:47                         ` Denys Fedoryshchenko
2008-06-16 22:08                     ` Denys Fedoryshchenko
2008-06-16 23:24                       ` Brandeburg, Jesse
2008-06-17  1:53                         ` Denys Fedoryshchenko
2008-06-17  6:46                         ` Denys Fedoryshchenko
2008-06-17 17:22                           ` Denys Fedoryshchenko
2008-06-18  0:58                             ` Brandeburg, Jesse
2008-06-17 21:04                         ` Denys Fedoryshchenko
2008-06-18 16:50                           ` Brandeburg, Jesse
2008-06-18 17:03                             ` Denys Fedoryshchenko
2008-06-16 21:17           ` Denys Fedoryshchenko
2008-06-16 21:05         ` Eric Dumazet
2008-06-16 20:15 ` Auke Kok
2008-06-16 20:29   ` Denys Fedoryshchenko
2008-06-16 20:26 ` Francois Romieu
2008-06-16 20:37 ` Waskiewicz Jr, Peter P
2008-06-16 20:42   ` Denys Fedoryshchenko

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=4856D1D6.7040207@intel.com \
    --to=auke-jan.h.kok@intel.com \
    --cc=dada1@cosmosbay.com \
    --cc=denys@visp.net.lb \
    --cc=linux.nics@intel.com \
    --cc=netdev@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).