netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Denys Fedoryshchenko <denys@visp.net.lb>
To: "Brandeburg, Jesse" <jesse.brandeburg@intel.com>
Cc: "Eric Dumazet" <dada1@cosmosbay.com>, netdev@vger.kernel.org
Subject: Re: packetloss, on e1000e worse than r8169?
Date: Tue, 17 Jun 2008 09:46:17 +0300	[thread overview]
Message-ID: <200806170946.17351.denys@visp.net.lb> (raw)
In-Reply-To: <36D9DB17C6DE9E40B059440DB8D95F52056AC4C2@orsmsx418.amr.corp.intel.com>

On Tuesday 17 June 2008 02:24, Brandeburg, Jesse wrote:
First, i catch when tx_deferred_ok increasing, rx_missed_errors also increasing.  For example deffered +1 , missed_errors +10.
A bit strange.


> Try turning off Flow Control using ethtool -A ethX rx off tx off autoneg
> off
Well, seems it is a keypoint on new motherboard, but i have to see at peak time still (about 10-14 hours to go).

So the question is, or flow control is broken here, or it is unknown when i must use flow-control and when - not.

Once i had packetloss on e1000 gigabit link, without it. 
Now it is packetloss - when i start to use it.

-- 
------
Technical Manager
Virtual ISP S.A.L.
Lebanon

  parent reply	other threads:[~2008-06-17  6:46 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
     [not found]       ` <20080616204411.M52834@visp.net.lb>
2008-06-16 20:49         ` Kok, Auke
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 [this message]
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:52       ` Denys Fedoryshchenko
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=200806170946.17351.denys@visp.net.lb \
    --to=denys@visp.net.lb \
    --cc=dada1@cosmosbay.com \
    --cc=jesse.brandeburg@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).