mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Paul Mackerras <paulus@samba.org>
Cc: jt@hpl.hp.com, linux-ppp@vger.kernel.org,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: PPP feature request (Tx queue len + close)
Date: Mon, 4 Mar 2002 19:19:47 -0800	[thread overview]
Message-ID: <20020304191947.A32730@bougret.hpl.hp.com> (raw)
In-Reply-To: <20020304144200.A32397@bougret.hpl.hp.com> <15492.13788.572953.6546@argo.ozlabs.ibm.com>
In-Reply-To: <15492.13788.572953.6546@argo.ozlabs.ibm.com>; from paulus@samba.org on Tue, Mar 05, 2002 at 02:05:00PM +1100

On Tue, Mar 05, 2002 at 02:05:00PM +1100, Paul Mackerras wrote:
> 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.

	IrTTP is another problem. If I were to use TCP instead of
IrTTP, would you still ask me to reduce the window size of TCP ? Let's
try to be fair...
	I'm taking the approach that every little thing helps. There
is a trivial win in PPP, and I would be stupid to not exploit it.
	On the other hand, you are right that with IrTTP. I was
spending the day investigating this issue. As usual with Linux-IrDA,
it's very messy. I think I will need some architecture change to
implement proper flow control between IrLAP and IrTTP. And then
qualify that with all IrTTP users :-(

> > 	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?

	No idea, never had this case ;-) This is exactly for this
reason I ask you.

> 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.

	I must have missed this option. I'll look again in the pppd
man page. That may be good enough...
	For stuff influencing level above, just think of
ap->chan.hdrlen. In my case, it goes from IrLAP to TCP via IrLMP,
IrTTP, IrNET, PPP and IP.

> Could you produce some numbers showing better throughput, fewer
> retransmissions, or whatever, with a smaller transmit queue length?

	Don't have number, but I don't need number to know that.

> Paul.

	Jean

  reply	other threads:[~2002-03-05  3:20 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
2002-03-05  3:19   ` Jean Tourrilhes [this message]
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=20020304191947.A32730@bougret.hpl.hp.com \
    --to=jt@bougret.hpl.hp.com \
    --cc=jt@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-ppp@vger.kernel.org \
    --cc=paulus@samba.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®