From: Siavash Eghlimi <eghlimidev@gmail.com>
To: bloat-devel@lists.bufferbloat.net
Subject: Help me get started (II)
Date: Thu, 22 Feb 2018 17:49:18 +0330 [thread overview]
Message-ID: <CAEPXwpNqE2hBsvahdvAG7uLnXWsD60ce9_wgRvm4LusX+PycOQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2524 bytes --]
Hi everybody, hope you all feel great,
I wanna do a thesis on bufferbloat. I posted some questions and got
beautiful answers. following those conversations, it was asked:
--What did you measure, and what did that show?
I measured my DSL line via couple of different methods and tools. seems
my line is bloated. ping time got tripled. there is latency in, both, my
download and upload. i have the results saved.
--Was there something there you thought was interesting that you want to
explore further?
Well, this whole thing is interesting. I didn't know that I'm NOT using
about 47% of my bandwidth :) (talk about helping people...)
turned out, ALL of my devices have SOME kind of a problem in this area.
but, what was MOST interesting to me was "How much I don't know"; I'm not
only talking about knowledge, but about these problems that exists and MANY
people, even PROs (not that I am one), don't know about.
Science-wise, most interesting part is the implementation of algorithms and
protocols that caused these problems in the first place. why did they cause
it? integrating some of the solutions together (like SQM). things of that
nature is interesting to me. generally, Implementation is more interesting
to me than the solution, itself. (How to do, rather than WHAT to do.)
--And what did you read already? :)
1. Classic bufferbloat article.
2. ALMOST advanced network concepts like "Window Scaling" , "Framing",
etc. etc.
3. One fourth of "TCP/IP Architecture in Linux .... "
4. Wireshark (Basics)
So, my question:
first, any suggestion, generally, so far?
second, I tried to study FreeBSD since Linux was TOO BIG. anyway, I found a
good book and as I was studying, I could swear I saw something in "
bufferbloat.net" about FreeBSD. So, I checked it out; turns out it's a
project to implement some algorithms like CoDel into FreeBSD. Immediately,
I emailed the professor in charge, and he simply said: "I don't have time"
:)
This project seemed tailor-made for me. lots of coding. something CLEAR to
do. loads of stuff for the Thesis. lots of science and knowledge. but ....
Second place goes to "Flent", though I don't know how much work is there to
be done. Can it bear a thesis for me ?
Third place goes to "SQM".
Any suggestions? :)
I really wanna start sooner than later and get my hands dirty. I know, this
is not enough research to know exactly what you want, but my time is
limited and I better begin.
(By the way, I can put 7 months on it.)
Thanks a lot
Siavash Eghlimi
[-- Attachment #2: Type: text/html, Size: 3066 bytes --]
next reply other threads:[~2018-02-22 14:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 14:19 Siavash Eghlimi [this message]
2018-02-22 16:38 ` Toke Høiland-Jørgensen
-- strict thread matches above, loose matches on Subject: below --
2018-01-23 9:11 Siavash Eghlimi
2018-01-23 11:30 ` Toke Høiland-Jørgensen
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=CAEPXwpNqE2hBsvahdvAG7uLnXWsD60ce9_wgRvm4LusX+PycOQ@mail.gmail.com \
--to=eghlimidev@gmail.com \
--cc=bloat-devel@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