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,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
e1000-devel@lists.sourceforge.net
Subject: Re: large packet loss take2 2.6.31.x
Date: Wed, 25 Nov 2009 20:11:05 +0100 [thread overview]
Message-ID: <20091125191105.GA3167@ami.dom.local> (raw)
In-Reply-To: <81bfc67a0911250606k1ec76354n217da9ca20b3517c@mail.gmail.com>
On Wed, Nov 25, 2009 at 09:06:30AM -0500, Caleb Cushing wrote:
> > Anyway, since there are problems with
> > getting stats from the router we still can't compare them, or check
> > for the dropped stats. (Btw, could you check for /proc/net/softnet_stat
> > yet?)
>
> router? good kernel? bad kernel?
router.
>
> > So, it might be the kernel problem you reported, but there is not
> > enough data to prove it. Then my proposal is to try to repeat this
> > problem in more "testing friendly" conditions - preferably against
> > some other, more up-to-date linux box, if possible?
>
> yeah 2.6.31.6 works on my laptop fine I'll just have to see about
> getting a direct connection to it. probably do that after I bring the
> other NIC back from home, on thanksgiving.
This other NIC is a really good idea, so let's wait and see.
Happy Thanksgiving!
Jarek P.
WARNING: multiple messages have this Message-ID (diff)
From: Jarek Poplawski <jarkao2@gmail.com>
To: Caleb Cushing <xenoterracide@gmail.com>
Cc: e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
Frans Pop <elendil@planet.nl>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Subject: Re: large packet loss take2 2.6.31.x
Date: Wed, 25 Nov 2009 20:11:05 +0100 [thread overview]
Message-ID: <20091125191105.GA3167@ami.dom.local> (raw)
In-Reply-To: <81bfc67a0911250606k1ec76354n217da9ca20b3517c@mail.gmail.com>
On Wed, Nov 25, 2009 at 09:06:30AM -0500, Caleb Cushing wrote:
> > Anyway, since there are problems with
> > getting stats from the router we still can't compare them, or check
> > for the dropped stats. (Btw, could you check for /proc/net/softnet_stat
> > yet?)
>
> router? good kernel? bad kernel?
router.
>
> > So, it might be the kernel problem you reported, but there is not
> > enough data to prove it. Then my proposal is to try to repeat this
> > problem in more "testing friendly" conditions - preferably against
> > some other, more up-to-date linux box, if possible?
>
> yeah 2.6.31.6 works on my laptop fine I'll just have to see about
> getting a direct connection to it. probably do that after I bring the
> other NIC back from home, on thanksgiving.
This other NIC is a really good idea, so let's wait and see.
Happy Thanksgiving!
Jarek P.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
next prev parent reply other threads:[~2009-11-25 19:11 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-31 14:21 large packet loss take2 2.6.31.x Caleb Cushing
2009-10-31 18:44 ` 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 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
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 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-24 18:27 ` Jarek Poplawski
2009-11-25 14:06 ` Caleb Cushing
2009-11-25 14:06 ` Caleb Cushing
2009-11-25 16:47 ` Caleb Cushing
2009-11-25 16:47 ` Caleb Cushing
2009-11-25 19:11 ` Jarek Poplawski [this message]
2009-11-25 19:11 ` Jarek Poplawski
2009-11-27 18:07 ` Caleb Cushing
2009-11-27 21:36 ` Jarek Poplawski
2009-11-27 21:36 ` Jarek Poplawski
2009-11-27 22:35 ` Caleb Cushing
2009-11-27 22:35 ` Caleb Cushing
2009-11-27 22:42 ` Jarek Poplawski
2009-12-04 1:49 ` Caleb Cushing
2009-12-04 1:49 ` Caleb Cushing
2009-12-04 9:05 ` Jarek Poplawski
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-04 23:47 ` Jarek Poplawski
2009-12-05 7:06 ` Caleb Cushing
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=20091125191105.GA3167@ami.dom.local \
--to=jarkao2@gmail.com \
--cc=andi@firstfloor.org \
--cc=e1000-devel@lists.sourceforge.net \
--cc=elendil@planet.nl \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--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 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.