From: Chuck Ebbert <cebbert@redhat.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Cc: Netdev <netdev@vger.kernel.org>
Subject: Re: Unexcepted latency (order of 100-200 ms) with TCP (packet receive)
Date: Thu, 26 Apr 2007 12:16:41 -0400 [thread overview]
Message-ID: <4630D069.30605@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0704241518370.28337@kivilampi-30.cs.helsinki.fi>
Ilpo Järvinen wrote:
> ...I'm unsure how to continue the investigation from this point onward
> and asking for ideas/suggestions or how to rule out more possibilities...
> Or is there some knob which I don't know of that should be toggled or
> something, is 2.6 network stack expected to behave this way?
>
Try a different network adapter.
Try turning off hardware TSO offload:
ethtool -K ethX tso off
next prev parent reply other threads:[~2007-04-26 16:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 10:20 Unexcepted latency (order of 100-200 ms) with TCP (packet receive) Ilpo Järvinen
2007-04-26 16:16 ` Chuck Ebbert [this message]
2007-04-26 19:30 ` Ilpo Järvinen
2007-04-27 7:17 ` Bill Fink
2007-04-27 15:07 ` Ilpo Järvinen
2007-05-07 11:45 ` Ilpo Järvinen
2007-05-09 7:03 ` David Miller
2007-04-26 16:38 ` Rick Jones
2007-04-26 19:18 ` Ilpo Järvinen
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=4630D069.30605@redhat.com \
--to=cebbert@redhat.com \
--cc=ilpo.jarvinen@helsinki.fi \
--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 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.