From: "David S. Miller" <davem@davemloft.net>
To: david.carlton@sun.com
Cc: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: network delays, mysterious push packets
Date: Mon, 06 Feb 2006 15:50:28 -0800 (PST) [thread overview]
Message-ID: <20060206.155028.115708927.davem@davemloft.net> (raw)
In-Reply-To: <yf2k6c8ru3x.fsf@kealia.sfbay.sun.com>
From: David Carlton <david.carlton@sun.com>
Date: Mon, 06 Feb 2006 14:38:10 -0800
> I'm working on an application that we're trying to switch from a 2.4
> kernel to a 2.6 kernel. (I believe we're using 2.6.9.) One part of
> the program periodically sends out chunks of data (whose size is just
> over 1MB) via tcp.
Please reproduce with something more current and report to the correct
mailing list (netdev@vger.kernel.org).
Thanks.
next parent reply other threads:[~2006-02-06 23:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <yf2k6c8ru3x.fsf@kealia.sfbay.sun.com>
2006-02-06 23:50 ` David S. Miller [this message]
2006-02-07 1:18 ` network delays, mysterious push packets Herbert Xu
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=20060206.155028.115708927.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=david.carlton@sun.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox