From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] wireless software retry with ECN?
Date: Wed, 15 Jun 2011 12:43:47 -0600 [thread overview]
Message-ID: <BANLkTi=yWq3eDxiBXc5HAbcGAUADP6cGhg@mail.gmail.com> (raw)
When you have to retry sending a packet in swretry at a wireless
driver (mac802.11?) level, marking it as 'congested' seems to make sense.
If you are going to make heroic efforts to deliver packets in the
first place, you might as well tell the receiver of your heroism.
While retry is normal, even without collisions, especially with aggregation,
some indication of the level of heroism involved would be useful at
the receiver.
A related idea is to use more of the diffserv markings to indicate actually
drop-able packets.
What is it going to take to get to drop (or mark) more packets, of any kind,
under appropriate circumstances, on wireless?
A related thought might be to decrement the hop count on each retry,
and not by one.
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com
next reply other threads:[~2011-06-15 18:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 18:43 Dave Taht [this message]
2011-06-15 21:34 ` Jonathan Morton
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
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTi=yWq3eDxiBXc5HAbcGAUADP6cGhg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
/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