Historic archive of defunct list bloat-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Siavash Eghlimi <eghlimidev@gmail.com>
To: bloat-devel@lists.bufferbloat.net
Subject: Help me get started (II)
Date: Tue, 23 Jan 2018 12:41:45 +0330	[thread overview]
Message-ID: <CAEPXwpNQT9_okr8ubFrmU2wMfv6Z9VSaWhthFHXVXF1DVXuKKw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]

Dear contributors,

Hi. I already did a post, and got A LOT of help from a
Mr.Høiland-Jørgensen, if I'm not wrong. first I wanted to thank all of you;
and HIM, in particular.

Second, it was suggested to me to so some measurements AND to choose a more
specific area (Aspect) of bufferbloat. Well, I did some measurements and
some research just to get an idea of how it works... Can't say I completely
get it yet, but I'm getting there :)

also, I chose a more detailed aspect of bufferbloat; "Low-layer network
protocols' design and their impact on buffering (ex: WiFi networks can't do
aggregation without some buffering)"

Since I wanna do a Thesis on it, and use Linux as a tool to understand
networking and do programming, I found resources on Linux and its network
stack.

What I need now is specific resources on the ASPECT of bufferbloat that I
chose. where should I go? what should I read? how to get into it? I don't
wanna dive into it blindly. I want to do this RIGHT. and because of the
Thesis, time is of the essence. also, I really wanna do something to help
the community, HOPEFULLY.

I appreciate ANY kind of help.

Thank you all.
Siavash

[-- Attachment #2: Type: text/html, Size: 1396 bytes --]

             reply	other threads:[~2018-01-23  9:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-23  9:11 Siavash Eghlimi [this message]
2018-01-23 11:30 ` Toke Høiland-Jørgensen
2018-02-22 14:19 Siavash Eghlimi
2018-02-22 16:38 ` 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=CAEPXwpNQT9_okr8ubFrmU2wMfv6Z9VSaWhthFHXVXF1DVXuKKw@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