From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 530B73B29E for ; Thu, 22 Feb 2018 09:19:20 -0500 (EST) Received: by mail-lf0-x22d.google.com with SMTP id y19so7629381lfd.4 for ; Thu, 22 Feb 2018 06:19:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=Lqe1HiBfb+DZJMUsz9kovZdYuncZkrmrGUq5Z5S0MhE=; b=KzPIEEPeenCg5VONUot1w5xDTRmW6/crQ27QabUXNpL5FJPsVwzGbLGnjvdd/g6fj1 hS6BeqcUFTayCiyISpE8sUdSgxYN5FkdlxfXgQvpWm4ReImWUzCHJn6lc8VR+PrcjIJi A5vty5eB+JTBauyT2NPg+ZKNGjjj4dT8GL/ulc2jCN+o+zWVfg3JmcKUrdKx9kdkPMWZ jnnPwZUkJz9PZDd/3qDEjh9VlQOFOWTc8OMKKzaqzbjMGMoYYSB7WvHBwPI9oIv2zGUY HliQQp7+qqkE12BzPAzBwAO2p666cRgOFsHYkIZnIDXo13NbOmzMgp6v6bakntH0xU1A 57xA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Lqe1HiBfb+DZJMUsz9kovZdYuncZkrmrGUq5Z5S0MhE=; b=UT+zq7wahoB3dsKSgFRuS/QDLoGVW+KdLu1DaYki6xonbzpYQ3p3qu5zXdKGqc15Rg Vxqx4qwf2e1bGvLAQbz0nOwwSwbkvz5QFtAhOkmTImMfxla1dM1rCaW0GZSeGTu7rLk3 +elBJL1uFD91wbdkk6Yr5l4axlNq9R0qn4nvmYNJjr/rUoxvXChfQyigsrrhsmOFrIpd QQfEbV3snVvrIfDQ+RRnNhbgltv1tjtnAIHiUPh3u1BPVnBQ574AS7Q8HvQcrEdOMYSq dwHCo84DnJMOO6/8jPQPQCKqaejOvWTQGQ1TeC+hMoUHTtc+kP6cu9f+oCtdBJw582um H3iA== X-Gm-Message-State: APf1xPCLUCpcqkLVagN7cktl6p+JvTVD/Uf5c8jrFY3ULXJFcRJymUIq kpdVn5nkSS7oYANyefQZA39VUCkotxzZvBqNW6MIfQ== X-Google-Smtp-Source: AH8x226iZQsKF07ANOo+CpulxdHz0/mqTCeIqQnzO44/27Bw3k+fmO0erpFRwn2gc7emarMCBEUBPixpI79hLlj9IEU= X-Received: by 10.25.37.139 with SMTP id l133mr5441372lfl.70.1519309158924; Thu, 22 Feb 2018 06:19:18 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.150.69 with HTTP; Thu, 22 Feb 2018 06:19:18 -0800 (PST) From: Siavash Eghlimi Date: Thu, 22 Feb 2018 17:49:18 +0330 Message-ID: Subject: Help me get started (II) To: bloat-devel@lists.bufferbloat.net Content-Type: multipart/alternative; boundary="001a114117d4b8d2290565cdba78" X-BeenThere: bloat-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Developers working on AQM, device drivers, and networking stacks" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Feb 2018 14:19:20 -0000 --001a114117d4b8d2290565cdba78 Content-Type: text/plain; charset="UTF-8" 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 --001a114117d4b8d2290565cdba78 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi everybody, hope you all feel great,

I wanna= do a thesis on bufferbloat. I posted some questions and got beautiful answ= ers. following those conversations, it was asked:

--What did you mea= sure, and what did that show?
=C2=A0=C2=A0=C2=A0 I measured my DS= L 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?
= =C2=A0=C2=A0=C2=A0 Well, this whole thing is interesting. I didn't know= that I'm NOT using about 47% of my bandwidth :)=C2=A0 (talk about help= ing people...)
turned out, ALL of my devices have SOME kind o= f 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 i= n 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? :)<= br>
=C2=A0=C2=A0=C2=A0 1. Classic bufferbloat article.
<= div>=C2=A0=C2=A0=C2=A0 2. ALMOST advanced network concepts like "Windo= w Scaling" , "Framing", etc. etc.
=C2=A0=C2=A0= =C2=A0 3. One fourth of "TCP/IP Architecture in Linux .... "
<= /div>
=C2=A0=C2=A0=C2=A0 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 i= n "bufferbloat.net" about = FreeBSD. So, I checked it out; turns out it's a project to implement so= me 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 C= LEAR to do. loads of stuff for the Thesis. lots of science and knowledge. b= ut ....

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?=C2=A0 :)
I really wanna start sooner than la= ter and get my hands dirty. I know, this is not enough research to know exa= ctly what you want, but my time is limited and I better begin.
(By the way, I can put 7 months on it.)

Than= ks a lot
Siavash Eghlimi

--001a114117d4b8d2290565cdba78--