From: Paul Mackerras <paulus@samba.org>
To: jt@hpl.hp.com
Cc: linux-ppp@vger.kernel.org,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: PPP feature request (Tx queue len + close)
Date: Tue, 5 Mar 2002 14:05:00 +1100 (EST) [thread overview]
Message-ID: <15492.13788.572953.6546@argo.ozlabs.ibm.com> (raw)
In-Reply-To: <20020304144200.A32397@bougret.hpl.hp.com>
In-Reply-To: <20020304144200.A32397@bougret.hpl.hp.com>
Jean Tourrilhes writes:
> Problem : IrDA does its buffering (IrTTP is a sliding window
> protocol). PPP does its buffering (1 packet in ppp_generic +
> dev->tx_queue_len = 3). End result : a large number of packets queued
> for transmissions, which result in some network performance issues.
How much buffering does IrTTP do? How large is its window? It is
much more critical IMO to reduce the buffering below ppp_generic than
it is to reduce the buffering above it. The ppp_generic layer itself
does as little buffering as possible.
> Solution : could we allow the PPP channel to overwrite
> dev->tx_queue_len ?
> This is similar to the channel beeing able to set the MTUs and
> other parameters...
Not really, the channel can't set the bundle MTU, only its own MTU.
It can set the header length (the desired amount of headroom) but that
is really only an optimization.
What would happen in the case where two channels connected to the
same ppp unit want to set the queue length to two different values?
In general I think it would be better to get pppd to set the transmit
queue length than to have the channel magically influencing stuff two
levels above it.
Could you produce some numbers showing better throughput, fewer
retransmissions, or whatever, with a smaller transmit queue length?
Paul.
next prev parent reply other threads:[~2002-03-05 3:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-04 22:42 Jean Tourrilhes
2002-03-05 0:55 ` James Stevenson
2002-03-05 1:01 ` Jean Tourrilhes
2002-03-05 3:05 ` Paul Mackerras [this message]
2002-03-05 3:19 ` Jean Tourrilhes
2002-03-05 18:13 ` Maksim Krasnyanskiy
2002-03-05 18:28 ` Jean Tourrilhes
2002-03-05 19:15 ` James Carlson
2002-03-05 19:27 ` Jean Tourrilhes
2002-03-05 21:49 ` James Carlson
2002-03-05 21:17 ` Maksim Krasnyanskiy
2002-03-05 21:27 ` Jean Tourrilhes
2002-03-05 5:20 ` Paul Mackerras
2002-03-05 17:45 ` Jean Tourrilhes
2002-03-05 19:39 ` Maksim Krasnyanskiy
2002-03-05 20:23 ` Jean Tourrilhes
2002-03-05 22:48 ` 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=15492.13788.572953.6546@argo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ppp@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
all inboxes | Powered by JetHome®