From: Hagen Paul Pfeifer <hagen@jauu.net>
To: Albert Cahalan <acahalan@gmail.com>
Cc: Jussi Kivilinna <jussi.kivilinna@mbnet.fi>,
Eric Dumazet <eric.dumazet@gmail.com>,
Mikael Abrahamsson <swmike@swm.pp.se>,
linux-kernel <linux-kernel@vger.kernel.org>,
<netdev@vger.kernel.org>
Subject: Re: txqueuelen has wrong units; should be time
Date: Mon, 28 Feb 2011 16:38:57 +0100 [thread overview]
Message-ID: <cbb9e1113901f1a324359b6ed3f1a611@localhost> (raw)
In-Reply-To: <AANLkTimofhhH5omyk=HhkyaNG+MGqoac4rDf=dPuR7K-@mail.gmail.com>
On Sun, 27 Feb 2011 18:33:39 -0500, Albert Cahalan wrote:
> I suppose there is a need to allow at least 2 packets despite any
> time limits, so that it remains possible to use a traditional modem
> even if a huge packet takes several seconds to send.
That is a good point! We talk about as we may know every use case of
Linux. But this is not true at all. One of my customer for example operates
the Linux network stack functionality on top of a proprietary MAC/Driver
where the current packet queue characteristic is just fine. The
time-drop-approach is unsuitable because the bandwidth can vary in a small
amount of time over a great range (0 till max. bandwidth). A sufficient
buffering shows up superior in this environment (only IPv{4,6}/UDP).
Hagen
next prev parent reply other threads:[~2011-02-28 15:38 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-27 5:44 txqueuelen has wrong units; should be time Albert Cahalan
2011-02-27 7:02 ` Mikael Abrahamsson
2011-02-27 7:54 ` Eric Dumazet
2011-02-27 8:27 ` Albert Cahalan
2011-02-27 10:55 ` Jussi Kivilinna
2011-02-27 20:07 ` Eric Dumazet
2011-02-27 21:32 ` Jussi Kivilinna
2011-02-28 11:43 ` Jussi Kivilinna
2011-02-28 13:10 ` Eric Dumazet
2011-02-28 18:31 ` Jussi Kivilinna
2011-02-28 16:11 ` John W. Linville
2011-02-28 16:48 ` Eric Dumazet
2011-02-28 16:55 ` John W. Linville
2011-02-28 17:18 ` Eric Dumazet
2011-02-28 21:45 ` John Heffner
2011-03-01 4:11 ` Albert Cahalan
2011-03-01 4:18 ` David Miller
2011-03-01 6:54 ` Albert Cahalan
2011-03-01 7:25 ` David Miller
2011-03-01 7:26 ` Eric Dumazet
2011-03-01 19:37 ` Albert Cahalan
2011-03-01 20:14 ` Eric Dumazet
2011-03-01 20:16 ` Eric Dumazet
2011-03-02 3:10 ` Mikael Abrahamsson
2011-03-02 20:25 ` Chris Friesen
2011-03-01 5:01 ` Eric Dumazet
2011-03-01 5:36 ` Eric Dumazet
2011-02-27 23:33 ` Albert Cahalan
2011-02-28 11:23 ` Jussi Kivilinna
2011-03-02 21:54 ` [RFC LOL OMG] pfifo_lat: qdisc that limits dequeueing based on estimated link latency John W. Linville
2011-03-02 22:08 ` John W. Linville
2011-03-03 12:51 ` Eric Dumazet
2011-02-28 15:38 ` Hagen Paul Pfeifer [this message]
2011-02-28 16:37 ` txqueuelen has wrong units; should be time Albert Cahalan
2011-02-28 17:45 ` John W. Linville
2011-02-28 17:20 ` Bill Sommerfeld
2011-02-28 21:51 ` John Heffner
2011-03-01 0:46 ` Mikael Abrahamsson
2011-03-02 6:25 ` Stephen Hemminger
2011-03-02 6:41 ` Mikael Abrahamsson
2011-03-02 7:07 ` Stephen Hemminger
2011-03-02 16:41 ` Mikael Abrahamsson
2011-03-02 16:50 ` Eric Dumazet
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=cbb9e1113901f1a324359b6ed3f1a611@localhost \
--to=hagen@jauu.net \
--cc=acahalan@gmail.com \
--cc=eric.dumazet@gmail.com \
--cc=jussi.kivilinna@mbnet.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=swmike@swm.pp.se \
/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;
as well as URLs for NNTP newsgroup(s).