From: Felix von Leitner <felix-linuxkernel@fefe.de>
To: Rick Jones <rick.jones2@hp.com>
Cc: Chuck Ebbert <cebbert@redhat.com>,
linux-kernel@vger.kernel.org, Netdev <netdev@vger.kernel.org>
Subject: Re: bizarre network timing problem
Date: Fri, 2 Nov 2007 23:38:56 +0100 [thread overview]
Message-ID: <20071102223856.GA5121@codeblau.de> (raw)
In-Reply-To: <472BA5BC.6000901@hp.com>
Thus spake Rick Jones (rick.jones2@hp.com):
> >Oh I'm pretty sure it's not my application, because my application performs
> >well over ethernet, which is after all its purpose. Also I see the
> >write, the TCP uncork, then a pause, and then the packet leaving.
> Well, a wise old engineer tried to teach me that the proper spelling is
> ass-u-me :) so just for grins, you might try the TCP_RR test anyway :) And
> even if your application is correct (although I wonder why the receiver
> isn't sucking data-out very quickly...) if you can reproduce the problem
> with netperf it will be easier for others to do so.
My application is only the server, the receiver is smbget from Samba, so
I don't feel responsible for it :-)
Still, when run over Ethernet, it works fine without waiting for
timeouts to expire.
To reproduce this:
- smbget is from samba, you probably already have this
- gatling (my server) can be gotten from
cvs -d :pserver:cvs@cvs.fefe.de:/cvs -z9 co dietlibc libowfat gatling
dietlibc is not strictly needed, but it's my environment.
First built dietlibc, then libowfat, then gatling.
Felix
next prev parent reply other threads:[~2007-11-02 22:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 20:51 bizarre network timing problem Felix von Leitner
2007-10-17 21:17 ` Chuck Ebbert
2007-10-17 22:00 ` Felix von Leitner
2007-10-17 22:16 ` Rick Jones
2007-10-18 9:42 ` Felix von Leitner
2007-10-18 17:22 ` Rick Jones
2007-11-02 22:11 ` Felix von Leitner
2007-11-02 22:33 ` Rick Jones
2007-11-02 22:38 ` Felix von Leitner [this message]
2007-11-02 22:58 ` Rick Jones
2007-11-02 23:23 ` Felix von Leitner
2007-11-06 21:12 ` Rick Jones
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=20071102223856.GA5121@codeblau.de \
--to=felix-linuxkernel@fefe.de \
--cc=cebbert@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.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.