public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mika Liljeberg <Mika.Liljeberg@welho.com>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: TCP acking too fast
Date: Sun, 14 Oct 2001 10:53:17 +0300	[thread overview]
Message-ID: <3BC9446D.A47CE2C6@welho.com> (raw)
In-Reply-To: <3BC8DAF0.3D16A546@welho.com> <20011013.234016.104032175.davem@redhat.com> <3BC9393D.765A156@welho.com> <20011014.005041.39156727.davem@redhat.com>

"David S. Miller" wrote:
> 
>    From: Mika Liljeberg <Mika.Liljeberg@welho.com>
>    Date: Sun, 14 Oct 2001 10:05:33 +0300
> 
>    Looking at the dump, it seems that most arriving
>    segments have the PSH bit set.
> 
> I know you said what is running on the receiver, but do
> you have any clue what is running on the sender?  It looks
> _really_ broken.
> 
> The transfer looks like a bulk one but every segment (as you have
> stated) has PSH set, which is completely stupid.
> 
> At least, I can guarentee you that the sender is not Linux.  Or,
> if it is Linux, it is running a really broken implementation of
> a web server. :-)

I've got a feeling you're going to rue saying that (see my other email).
;-)

Regards,

	MikaL

  reply	other threads:[~2001-10-14  7:53 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-14  0:23 TCP acking too fast Mika Liljeberg
2001-10-14  6:40 ` David S. Miller
2001-10-14  7:05   ` Mika Liljeberg
2001-10-14  7:47     ` David S. Miller
2001-10-14  7:51       ` Mika Liljeberg
2001-10-14  8:12         ` David S. Miller
2001-10-14  8:39           ` Mika Liljeberg
2001-10-14  9:03             ` David S. Miller
2001-10-14  9:15               ` Mika Liljeberg
2001-10-14  9:16                 ` David S. Miller
2001-10-14  9:25               ` Andi Kleen
2001-10-14  9:39                 ` David S. Miller
2001-10-14 11:30                   ` Andi Kleen
2001-10-14 11:49                     ` Mika Liljeberg
2001-10-14 14:05                       ` Andi Kleen
2001-10-14 14:26                         ` Mika Liljeberg
2001-10-14 16:12                           ` Andi Kleen
2001-10-14 16:55                             ` Mika Liljeberg
2001-10-14 17:07                               ` kuznet
2001-10-14 17:26                                 ` Mika Liljeberg
2001-10-14 17:35                                   ` kuznet
2001-10-14 17:56                                     ` Mika Liljeberg
2001-10-14 18:20                                       ` kuznet
2001-10-14 18:48                                         ` Mika Liljeberg
2001-10-14 19:12                                           ` kuznet
2001-10-14 19:32                                             ` Mika Liljeberg
2001-10-14 19:40                                               ` kuznet
2001-10-14 20:06                                                 ` Mika Liljeberg
2001-10-15 18:40                                                   ` kuznet
2001-10-15 19:15                                                     ` Mika Liljeberg
2001-10-15 19:38                                                       ` Mika Liljeberg
2001-10-14 13:14                     ` [PATCH] " Mika Liljeberg
2001-10-14 16:36                     ` kuznet
2001-10-14  7:50     ` David S. Miller
2001-10-14  7:53       ` Mika Liljeberg [this message]
2001-10-15 20:59 ` Bill Davidsen

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=3BC9446D.A47CE2C6@welho.com \
    --to=mika.liljeberg@welho.com \
    --cc=davem@redhat.com \
    --cc=linux-kernel@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