From: Ed W <lists@wildgooses.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Packets being coallesced
Date: Tue, 16 Aug 2005 22:04:15 +0000 [thread overview]
Message-ID: <430262DF.6000608@wildgooses.com> (raw)
Here's a peculiar one. I'm trying to simulate some speed effects due to
varying sized packets so I have written a quick perl app which spits out
packets of a fixed size (<1500 bytes). What I'm finding is the despite
apparently turning off nagle and everything else I can think of I still
notice that when the receiver isn't keeping up that the sending side
(linux 2.6.11) is coalescing the packets and sending fewer large packets...?
Is this a known and expected thing to do, or am I likely suffering some
buffering effects in my perl app?
Note: I am observing the effect based on tcpdump traces, so I can
clearly see when it's sending the expect 1000 byte packets, and when
it's suddenly packing them altogether into max MTU sized packets. Note
also that it's *sending* them like this, it's not just the the receiver
is buffering and receiving them like this...
Seems odd to me?
Ed W
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
reply other threads:[~2005-08-16 22:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=430262DF.6000608@wildgooses.com \
--to=lists@wildgooses.com \
--cc=lartc@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