netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@gmail.com>
To: Caleb Cushing <xenoterracide@gmail.com>
Cc: Frans Pop <elendil@planet.nl>, Andi Kleen <andi@firstfloor.org>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: large packet loss take2 2.6.31.x
Date: Wed, 18 Nov 2009 21:10:34 +0100	[thread overview]
Message-ID: <20091118201034.GA3060@ami.dom.local> (raw)
In-Reply-To: <81bfc67a0911181021n1b969565y4a39b181360b5e92@mail.gmail.com>

On Wed, Nov 18, 2009 at 01:21:19PM -0500, Caleb Cushing wrote:
> > So, there is a basic question: can this mtr loss be seen while no
> > other traffic is present? After looking into these current dumps I
> > doubt. There are e.g. 3 pings unanswered between 09:21:50 and
> > 09:21:52 (21:31:34 to 21:31:38 router time), but a lot of tcp
> > packets to and from 192.168.1.3, so looks like simply dropped and
> > we can guess the reason.
> 
> yes. this was at a fairly low traffic time of day. 5am only 2 people
> were up, and I was using the other computer during. I've had everyone
> actively doing one or more of downloading/uploading/video/voip/gaming
> stuff on this network with no noticeable packet loss. if really,
> really needed I can probably restrict this network to 2 machines for
> the duration of the test.

Alas "a fairly low traffic" can have a fairly high surges, so it's not
easy to compare. Anyway, try to check, if it's still available, if
there were any messages from the NIC in syslog etc. during this test
(~09:21:50).

> 
> > Since this patch from the bisection is really limited to this one
> > module I doubt we should follow this direction. IMHO it shows the
> > test wasn't reproducible enough. Probably the amount and/or kind of
> > other traffic really matter. If I'm wrong and missed something again
> > let me know. Btw, could you try if changing with ifconfig the
> > txqueuelen of desktop's eth0 from 100 to 1000 changes anything
> > in this mtr test?
> 
> yeah testing it under my known working config first. I'll get back w/ you later.

Btw, since dropping at hardware (NIC) level seems more likely to me,
could you send 'ethtool eth0', and 'ethtool -S eth0' after such tests
(both sides).

Jarek P.

  reply	other threads:[~2009-11-18 20:10 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <81bfc67a0910310721p21046931o9b512cfd0a8a7acb@mail.gmail.com>
2009-10-31 18:44 ` large packet loss take2 2.6.31.x Frans Pop
2009-11-11 20:19   ` Caleb Cushing
2009-11-11 21:47     ` Andi Kleen
2009-11-11 22:05       ` Frans Pop
2009-11-11 22:48         ` Caleb Cushing
2009-11-12 11:38           ` Jarek Poplawski
2009-11-12 13:46             ` Caleb Cushing
2009-11-12 19:04               ` Jarek Poplawski
2009-11-12 21:47                 ` Jarek Poplawski
2009-11-13 16:25                 ` Caleb Cushing
2009-11-13 17:21                   ` Caleb Cushing
2009-11-13 21:16                   ` Jarek Poplawski
2009-11-18  9:59                     ` Caleb Cushing
2009-11-18 10:00                       ` Caleb Cushing
2009-11-18 13:51                       ` Jarek Poplawski
2009-11-18 18:21                         ` Caleb Cushing
2009-11-18 20:10                           ` Jarek Poplawski [this message]
2009-11-18 22:38                             ` Jarek Poplawski
2009-11-22 19:35                               ` Caleb Cushing
2009-11-22 20:50                                 ` Jarek Poplawski
2009-11-24  6:17                                   ` Caleb Cushing
2009-11-24 11:19                                     ` Jarek Poplawski
2009-11-24 13:46                                       ` Jarek Poplawski
2009-11-24 15:57                                       ` [E1000-devel] " Allan, Bruce W
2009-11-24 18:27                                         ` Jarek Poplawski
2009-11-25 14:06                                       ` Caleb Cushing
2009-11-25 16:47                                         ` Caleb Cushing
2009-11-25 19:11                                         ` Jarek Poplawski
2009-11-27 18:07                                           ` Caleb Cushing
2009-11-27 21:36                                             ` Jarek Poplawski
2009-11-27 22:35                                               ` Caleb Cushing
2009-11-27 22:42                                                 ` Jarek Poplawski
2009-12-04  1:49                                                   ` Caleb Cushing
2009-12-04  9:05                                                     ` Jarek Poplawski
2009-12-04 18:28                                                       ` Caleb Cushing
2009-12-04 20:44                                                         ` Jarek Poplawski
2009-12-04 23:07                                                           ` Caleb Cushing
2009-12-04 23:47                                                             ` Jarek Poplawski
2009-12-05  7:06                                                               ` Caleb Cushing
2009-12-05  7:29                                                                 ` Caleb Cushing
2009-12-05 13:57                                                                 ` Jarek Poplawski

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=20091118201034.GA3060@ami.dom.local \
    --to=jarkao2@gmail.com \
    --cc=andi@firstfloor.org \
    --cc=elendil@planet.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=xenoterracide@gmail.com \
    /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).