From: Chris Friesen <chris.friesen@genband.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
Albert Cahalan <acahalan@gmail.com>,
David Miller <davem@davemloft.net>,
johnwheffner@gmail.com, linville@tuxdriver.com,
jussi.kivilinna@mbnet.fi, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: txqueuelen has wrong units; should be time
Date: Wed, 02 Mar 2011 14:25:36 -0600 [thread overview]
Message-ID: <4D6EA7C0.1020702@genband.com> (raw)
In-Reply-To: <alpine.DEB.1.10.1103020358010.7942@uplift.swm.pp.se>
On 03/01/2011 09:10 PM, Mikael Abrahamsson wrote:
> For the case when we're ourselves originating the traffic (for instance to
> a wifi card with varying speed and jitter due to retransmits on the wifi
> layer), I think it's taking the too easy way out to use the same
> mechanisms (dropping packets or marking ECN for our own originated packets
> seems really weird), here we should be able to pushback information to the
> applications somehow and do prioritization between flows since we're
> sitting on all information ourselves including the application.
Doesn't the socket tx buffer give all the app pushback necessary?
(Assuming it's set to a sane value.)
We should certainly do prioritization between flows. Perhaps if no
other information is available the scheduler priority could be used?
Chris
--
Chris Friesen
Software Developer
GENBAND
chris.friesen@genband.com
www.genband.com
next prev parent reply other threads:[~2011-03-02 20:26 UTC|newest]
Thread overview: 40+ 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 [this message]
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-02-28 15:38 ` Hagen Paul Pfeifer
2011-02-28 16:37 ` 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=4D6EA7C0.1020702@genband.com \
--to=chris.friesen@genband.com \
--cc=acahalan@gmail.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=johnwheffner@gmail.com \
--cc=jussi.kivilinna@mbnet.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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