From: Jordan Mendelson <jordy@napster.com>
To: Andi Kleen <ak@suse.de>
Cc: "David S. Miller" <davem@redhat.com>,
linux-kernel@vger.kernel.org, kuznet@ms2.inr.ac.ru
Subject: Re: Poor TCP Performance 2.4.0-10 <-> Win98 SE PPP
Date: Tue, 07 Nov 2000 10:13:46 -0800 [thread overview]
Message-ID: <3A08465A.1AF23D68@napster.com> (raw)
In-Reply-To: <3A07662F.39D711AE@napster.com> <200011070428.UAA01710@pizda.ninka.net> <3A079127.47B2B14C@napster.com> <200011070533.VAA02179@pizda.ninka.net> <3A079D83.2B46A8FD@napster.com> <200011070603.WAA02292@pizda.ninka.net> <3A07A4B0.A7E9D62@napster.com> <200011070656.WAA02435@pizda.ninka.net> <3A07AC45.DCC961FF@napster.com> <20001107104251.B5081@gruyere.muc.suse.de>
Andi Kleen wrote:
>
> On Mon, Nov 06, 2000 at 11:16:21PM -0800, Jordan Mendelson wrote:
> > > It is clear though, that something is messing with or corrupting the
> > > packets. One thing you might try is turning off TCP header
> > > compression for the PPP link, does this make a difference?
> >
> > Actually, there has been several reports that turning header compression
> > does help.
>
> What does help ? Turning it on or turning it off ?
We had a good number of reports that turning PPP header compression off
helped. The windows 98 connection I was testing with it did have header
compression turned on. Unfortunatly, I can't just ask the entire windows
world to turn off header compression in order to use our software. :)
I believe we've reverted all of our machines to 2.2, so testing this any
further is going to be a problem.
Jordan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-07 18:14 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-07 2:17 Poor TCP Performance 2.4.0-10 <-> Win98 SE PPP Jordan Mendelson
2000-11-07 4:28 ` David S. Miller
2000-11-07 5:20 ` Jordan Mendelson
2000-11-07 5:33 ` David S. Miller
2000-11-07 6:13 ` Jordan Mendelson
2000-11-07 6:03 ` David S. Miller
2000-11-07 6:44 ` Jordan Mendelson
2000-11-07 6:56 ` David S. Miller
2000-11-07 7:16 ` Jordan Mendelson
2000-11-07 7:12 ` David S. Miller
2000-11-07 7:32 ` Jordan Mendelson
2000-11-07 7:27 ` David S. Miller
2000-11-07 9:41 ` Andi Kleen
2000-11-07 9:57 ` David S. Miller
2000-11-07 12:22 ` Alan Cox
2000-11-07 12:10 ` David S. Miller
2000-11-07 9:42 ` Andi Kleen
2000-11-07 18:13 ` Jordan Mendelson [this message]
2000-11-07 9:38 ` Rogier Wolff
2000-11-07 9:58 ` David S. Miller
2000-11-07 10:36 ` Rogier Wolff
2000-11-07 22:43 ` Lincoln Dale
2000-11-07 7:03 ` Andi Kleen
2000-11-07 6:59 ` David S. Miller
2000-11-07 7:16 ` Andi Kleen
2000-11-07 7:14 ` David S. Miller
2000-11-07 9:35 ` Rogier Wolff
2000-11-07 10:00 ` David S. Miller
[not found] <3A076701.F437F88B@napster.com>
2000-11-07 3:44 ` Jordan Mendelson
2000-11-07 4:29 ` David S. Miller
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=3A08465A.1AF23D68@napster.com \
--to=jordy@napster.com \
--cc=ak@suse.de \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--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 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.