Lets make wifi fast again!
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] Carrying the CoDel timestamp into the driver
Date: Wed, 10 Aug 2016 17:41:50 +0200	[thread overview]
Message-ID: <B0E2DC98-B239-4A2E-AD78-2E455D37EB35@toke.dk> (raw)
In-Reply-To: <CA+BoTQn8uoKfa-iYGmPi4sHHnr-073e0-R3auTh1P9Oy0zRzow@mail.gmail.com>



On 10 August 2016 17:27:16 CEST, Michal Kazior <michal.kazior@tieto.com> wrote:
>On 10 August 2016 at 15:00, Toke Høiland-Jørgensen <toke@toke.dk>
>wrote:
>> Hi Michal
>>
>> In your mac80211 FQ-CoDel patch, you put the CoDel timestamp into a
>> union with the vif pointer in struct ieee80211_tx_info. This means
>the
>> timestamp is not available in the driver. I'm experimenting with some
>> changes where having the enqueue time available would be useful.
>>
>> Do you have any good ideas as to where else we could store the
>enqueue
>> time somewhere the driver can retrieve it?
>
>I did explore this idea for different purposes though - to maintain
>per-packet expected_duration. I think it should be in the
>linux-wireless archives. It compacted band, ack_frame_id I think but
>you get limited number of *bits*.
>
>.. or you could remove the rate control stuff from tx_info and convert
>all drivers to use mac80211 API to fetch it per-station on-demand only
>I guess..

Right. Guess I'll put that on the "things to look into" list.

Exactly why is it we can't just grow tx_info by a couple of bytes?

-Toke

  reply	other threads:[~2016-08-10 15:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-10 13:00 Toke Høiland-Jørgensen
2016-08-10 15:27 ` Michal Kazior
2016-08-10 15:41   ` Toke Høiland-Jørgensen [this message]
2016-08-10 16:01     ` Michal Kazior
2016-08-10 16:06       ` Toke Høiland-Jørgensen
2016-08-10 17:06         ` Dave Taht
2016-08-10 17:41           ` Dave Taht

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/make-wifi-fast.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=B0E2DC98-B239-4A2E-AD78-2E455D37EB35@toke.dk \
    --to=toke@toke.dk \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=michal.kazior@tieto.com \
    /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