From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] google summer of code application completed for bufferbloat.net
Date: Mon, 4 Feb 2019 11:55:37 -0800 [thread overview]
Message-ID: <CAA93jw7duY79D6-J=f9Y96hoiBkK4fBf59Fc4d7N1XHKFpqeig@mail.gmail.com> (raw)
Stephen Hemminger suggested we attempt a dpdk port of fq_codel/cake,
and (more importantly) also volunteered to be a mentor. Selfishly I'd
like to know more about how dpdk works, so I put in for that. There's
still some background writing to do on it to describe the project but
the prospect of passing along more of "The Knowledge" this summer
feels good.
I believe there is going to be some NS3 work also. So perhaps we'll
have assembled a "team" to get us there.
If anyone has more suggestions for bufferbloat.net projects (AND
ESPECIALLY... is willing to mentor) the final filing deadline is feb
6th.
--
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740
next reply other threads:[~2019-02-04 19:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 19:55 Dave Taht [this message]
2019-02-04 21:04 ` Klatsky, Carl
2019-02-04 21:30 ` 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/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='CAA93jw7duY79D6-J=f9Y96hoiBkK4fBf59Fc4d7N1XHKFpqeig@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