From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Cc: julius@inet.tu-berlin.de
Subject: [Cerowrt-devel] as it turns out there were a few wifi related papers and press
Date: Fri, 22 Aug 2014 17:20:48 -0500 [thread overview]
Message-ID: <CAA93jw6z6Gxg155kcX-cneX59TdX3y7k_8FmHCByLFhvVQJutg@mail.gmail.com> (raw)
This project seems to have a lot of potential with the low level
sub-layer-2 stuff going on in it making for easy mobility, and
optimizing for various flow types, with interfaces to the linux
mac80211 layer and minstrel and the ath9k.
http://www.net.t-labs.tu-berlin.de/~stefan/hotsdn14aero.pdf
I hava a few other summaries of stuff learnt at sigcomm and
linuxcon... and I am thinking of switching to blogging rather than
email for what I'd learned this week rather than bother the lists.
--
Dave Täht
reply other threads:[~2014-08-22 22:20 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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw6z6Gxg155kcX-cneX59TdX3y7k_8FmHCByLFhvVQJutg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=julius@inet.tu-berlin.de \
/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