From: Michael Welzl <michawe@ifi.uio.no>
To: David Lang <david@lang.hm>
Cc: Hal Murray <hmurray@megapathdsl.net>, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] sigcomm wifi
Date: Mon, 25 Aug 2014 09:43:12 +0200 [thread overview]
Message-ID: <2BB30FF1-CF65-4562-AFC9-99F41693CA9C@ifi.uio.no> (raw)
In-Reply-To: <alpine.DEB.2.02.1408232212300.19685@nftneq.ynat.uz>
On 24. aug. 2014, at 07:14, David Lang wrote:
> On Sat, 23 Aug 2014, Hal Murray wrote:
>
>>>> Yep... I remember a neat paper from colleagues at Trento University that
>>>> piggybacked TCP's ACKs on link layer ACKs, thereby avoiding the collisions
>>>> between TCP's ACKs and other data packets - really nice. Not sure if it
>>>> wasn't just simulations, though.
>>
>>> that's a neat hack, but I don't see it working, except when one end of the
>>> wireless link is also the endpoint of the TCP connection (and then only for
>>> acks from that device)
>>
>> That could be generalized to piggybacking any handy small packet onto the
>> link layer ACK.
>>
>> Of course, then you have to send back a link layer ACK for the extra info.
>> Does that converge?
>
> if you aren't talking between the two endpoints of the wireless connection, probably :-)
>
> but fairness would be an issue for something like this. what constitues a 'small amount of data' to try and piggyback, and what happens if you are talking between endpoints, are the two allowed to monopolize the airtime?
I agree - there'd have to be a size limit placed on what you really do piggyback on link layer ACKs. TCP ACK size can vary, depending on SACK...
> but backing up a step, finding airtime for the ack is just as hard as finding airtime for the next transmission.
I think not, don't link layer ACKs get to use a smaller CW? Or is this just me remembering it wrongly?
Cheers,
Michael
next prev parent reply other threads:[~2014-08-25 7:43 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-24 3:49 Hal Murray
2014-08-24 3:52 ` Jonathan Morton
2014-08-24 5:14 ` David Lang
2014-08-25 7:43 ` Michael Welzl [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-08-19 16:45 Dave Taht
2014-08-20 7:12 ` Eggert, Lars
2014-08-20 14:01 ` Dave Taht
2014-08-20 22:05 ` Jim Gettys
2014-08-21 6:52 ` Eggert, Lars
2014-08-21 7:11 ` Michael Welzl
2014-08-21 8:30 ` David Lang
2014-08-22 23:07 ` Michael Welzl
2014-08-22 23:50 ` David Lang
2014-08-23 19:26 ` Michael Welzl
2014-08-23 23:29 ` Jonathan Morton
2014-08-23 23:40 ` Steinar H. Gunderson
2014-08-23 23:49 ` Jonathan Morton
2014-08-24 1:33 ` David Lang
2014-08-24 2:29 ` Jonathan Morton
2014-08-24 5:12 ` David Lang
2014-08-24 6:26 ` Jonathan Morton
2014-08-24 8:24 ` David Lang
2014-08-24 9:20 ` Jonathan Morton
2014-08-25 7:25 ` Michael Welzl
2014-08-30 7:20 ` Jonathan Morton
2014-08-31 20:46 ` Simon Barber
2014-08-25 7:35 ` Michael Welzl
2014-08-24 1:09 ` David Lang
2014-08-25 8:01 ` Michael Welzl
2014-08-25 8:19 ` Sebastian Moeller
2014-08-25 8:33 ` Michael Welzl
2014-08-25 9:18 ` Alex Burr
2014-08-31 22:37 ` David Lang
2014-08-31 23:09 ` Simon Barber
2014-09-01 0:25 ` David Lang
2014-09-01 2:14 ` Simon Barber
2014-08-31 22:35 ` David Lang
2014-08-21 6:56 ` David Lang
2014-08-21 7:04 ` David Lang
2014-08-21 9:46 ` Jesper Dangaard Brouer
2014-08-21 19:49 ` David Lang
2014-08-21 19:57 ` Steinar H. Gunderson
2014-08-22 17:07 ` Jan Ceuleers
2014-08-22 18:27 ` Steinar H. Gunderson
2014-08-21 8:58 ` Steinar H. Gunderson
2014-08-22 23:34 ` David Lang
2014-08-22 23:41 ` Steinar H. Gunderson
2014-08-22 23:52 ` David Lang
2014-08-22 23:56 ` Steinar H. Gunderson
2014-08-23 0:03 ` Steinar H. Gunderson
2014-08-21 9:23 ` Mikael Abrahamsson
2014-08-21 9:30 ` Steinar H. Gunderson
2014-08-22 23:30 ` David Lang
2014-08-22 23:40 ` Steinar H. Gunderson
2014-08-20 8:30 ` Steinar H. Gunderson
2014-08-21 6:58 ` David Lang
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=2BB30FF1-CF65-4562-AFC9-99F41693CA9C@ifi.uio.no \
--to=michawe@ifi.uio.no \
--cc=bloat@lists.bufferbloat.net \
--cc=david@lang.hm \
--cc=hmurray@megapathdsl.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