Historic archive of defunct list bloat-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: linux-wireless <linux-wireless@vger.kernel.org>,
	 bloat-devel <bloat-devel@lists.bufferbloat.net>,
	netdev@vger.kernel.org
Subject: timestamping at the mac80211 layer before it hits tc?
Date: Sun, 27 Nov 2011 10:48:09 +0100	[thread overview]
Message-ID: <CAA93jw7zdM6+36CnvzcYoSjyMxP+myoX46JSzCGwg7jC5OnwcQ@mail.gmail.com> (raw)

My crazy idea at the moment is that since things can spend inordinate
amounts of time in the txqueue in wireless in particular, that moving
(tcp and packet) timestamping to where it enters the queue rather than
hits the wireless device would make a difference. Unless that's
already how it works.

http://www.bufferbloat.net/issues/304#change-1186

The secondary fallout of that is an easier way to expire (probably
rescheduled) packets that have spent too much time in queue.

Eric had put up a (rfc) tc filter a while back that dumped a timestamp
into the private block of the skb...

but...

I kind of like the idea of reusing the existing hwtstamps concept for
the period "queue entrance to queue exit", as a queue is a 'device',
IMHO.

from linux/skbuff.h

* hwtstamps can only be compared against other hwtstamps from
* the same device.
*
* This structure is attached to packets as part of the
* &skb_shared_info. Use skb_hwtstamps() to get a pointer.
*/
struct skb_shared_hwtstamps {
       ktime_t hwtstamp;
       ktime_t syststamp;
};


Sign me,
lost in a myriad of data paths on a sunday afternoon, wearing an asbestos suit

--
Dave Täht
SKYPE: davetaht
http://www.bufferbloat.net

                 reply	other threads:[~2011-11-27  9:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAA93jw7zdM6+36CnvzcYoSjyMxP+myoX46JSzCGwg7jC5OnwcQ@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bloat-devel@lists.bufferbloat.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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