From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Maksim Krasnyanskiy <maxk@qualcomm.com>
Cc: Paul Mackerras <paulus@samba.org>,
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 13:27:39 -0800 [thread overview]
Message-ID: <20020305132739.A1179@bougret.hpl.hp.com> (raw)
In-Reply-To: <20020304144200.A32397@bougret.hpl.hp.com> <15492.13788.572953.6546@argo.ozlabs.ibm.com> <20020304191947.A32730@bougret.hpl.hp.com> <15492.21937.402798.688693@argo.ozlabs.ibm.com> <20020305094535.A792@bougret.hpl.hp.com> <5.1.0.14.2.20020305095825.01b61fd8@mail1.qualcomm.com> <20020305102835.B847@bougret.hpl.hp.com> <5.1.0.14.2.20020305112314.01c3cea8@mail1.qualcomm.com> <20020305122343.A1094@bougret.hpl.hp.com> <5.1.0.14.2.20020305125056.01b5e1b8@mail1.qualcomm.com>
In-Reply-To: <5.1.0.14.2.20020305125056.01b5e1b8@mail1.qualcomm.com>; from maxk@qualcomm.com on Tue, Mar 05, 2002 at 01:17:42PM -0800
On Tue, Mar 05, 2002 at 01:17:42PM -0800, Maksim Krasnyanskiy wrote:
>
> True. PPP is a sort of "pass through" thing in your case.
Not fully. In some cases, PPP does compression (and
potentially encryption), and at 4 Mb/s those operations can become
close to bottlenecks (at least, on my slow boxes). But at least, it's
constant latency, as opposed to IrDA latencies.
> Yes. I see your point. It doesn't really make any difference which layer
> buffers stuff (unless that layer introduces delays). So I guess in your case
> you can just set txqueuelen to 1 if you're sure that underlying layer has long
> enough queues.
By the way, same logic applies to PAN. In PAN it's easier,
because as PAN is a pseudo Ethernet driver you can fudge tx_queue_len
directly.
> I see.
> Did you try ifconfig txqueuelen 1 ?
Not yet. I'm finishing the current batch of IrDA fixes, and
other backlog of Wireless patches. I would also need to squeeze
buffers out of IrDA queues.
> Max
Thanks, have fun...
Jean
next prev parent reply other threads:[~2002-03-05 21:28 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
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 [this message]
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=20020305132739.A1179@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=maxk@qualcomm.com \
--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®