General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Naeem Khademi <naeem.khademi@gmail.com>
Cc: "iccrg@irtf.org" <iccrg@irtf.org>, "aqm@ietf.org" <aqm@ietf.org>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [iccrg] ECN support for PIE AQM in Linux
Date: Wed, 14 Aug 2013 17:41:59 -0700	[thread overview]
Message-ID: <CAA93jw7Omv-j7u-wHPwyuKN5y-htEr+G248_-4jbZRveOBzwMg@mail.gmail.com> (raw)
In-Reply-To: <CAEjQQ5VXiKTAwCa8jxAdCMxGUcACx1yYomOB4_d6P-pp58vVnQ@mail.gmail.com>

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

The pie patches that I was using until recently are here:

http://snapon.lab.bufferbloat.net/~cero2/deb/patches/

Stephen hemminger and I cleaned up the original pie drop according to
KernelStyle in multiple ways. There is a rounding error problem in setting
the target value
(we'd recomended they switch to ktime rather than jiffies) that I either
added or was in there in the first place.... and we fixed a couple generic
bugs...

In addition to adding ecn support, we also added congestion notification to
(a la the linux red and fq_codel algorithms) to provide lossless feedback
into the host tcp stack. (this is, incidentally, 1 line of code) This
optimization made it possible to do comparisons on host <-> host tests
between these qdiscs, with no router in-between.

Syntactically the iproute2 patches could use identical syntax for time
based values as the codel iproute2 patches. Haven't got around to that.
(not my job, really, to improve cisco's code)

Now, I only now - today! - just noticed that the new pie code at cisco's
site seems *substantially* different from the older pie code the above was
based on, in that it no longer has an optimization for not dropping smaller
packets. (bytemode) This is going to invalidate most previous benchmarks of
pie that I know of, including all of mine, and most, if not all, of
cablelabs'. Sigh.

I will try to refresh my patches and update the lab over the next week or
so.



On Wed, Aug 14, 2013 at 2:17 PM, Naeem Khademi <naeem.khademi@gmail.com>wrote:

> Hi Vijay
>
> This code implements basic ECN capability for PIE meaning that it
> would CE-mark packets that would be early-dropped otherwise. I have
> sanity-checked the code (e.g. successful ECN marking and
> receiver/sender reaction). We're now in process of conducting larger
> set of experiments with PIE w/wo ECN that will eventually be published
> as we move forward.
>
> Cheers,
> Naeem
>
> On Wed, Aug 14, 2013 at 8:27 PM, Vijay Subramanian
> <subramanian.vijay@gmail.com> wrote:
> > Naeem,
> >
> > Thanks for testing and the contribution! We have ECN support in our
> current
> > code-under-development thanks to earlier help from Dave Taht but I will
> > merge your changes as appropriate and
> > submit it back for review.
> >
> > I will take a look at your code soon. Do you also have any test results
> > which you can share?
> >
> > Thanks again,
> > Vijay
> >
> >
> > On 14 August 2013 07:05, Naeem Khademi <naeem.khademi@gmail.com> wrote:
> >>
> >> Hi
> >>
> >> The already-existing PIE Linux code maintained at
> >> ftp://ftpeng.cisco.com/pie/ does not support ECN. Studying the
> interaction
> >> of ECN and AQM algos is probably of interest of some of us. I have
> added ECN
> >> support to PIE Linux code and have given it some basic sanity tests.
> >>
> >> The modified code is available at
> >> http://heim.ifi.uio.no/naeemk/research/PIE/
> >>
> >> I would appreciate any feedback.
> >>
> >> Regards,
> >> Naeem
> >>
> >>
> >>
> >> _______________________________________________
> >> iccrg mailing list
> >> iccrg@irtf.org
> >> https://www.irtf.org/mailman/listinfo/iccrg
> >>
> >
> _______________________________________________
> iccrg mailing list
> iccrg@irtf.org
> https://www.irtf.org/mailman/listinfo/iccrg
>



-- 
Dave Täht

Fixing bufferbloat with cerowrt:
http://www.teklibre.com/cerowrt/subscribe.html

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

  reply	other threads:[~2013-08-15  0:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-14 14:05 [Bloat] " Naeem Khademi
2013-08-14 18:27 ` [Bloat] [iccrg] " Vijay Subramanian
2013-08-14 21:17   ` Naeem Khademi
2013-08-15  0:41     ` Dave Taht [this message]
2013-08-15  1:25       ` [Bloat] [aqm] " Eggert, Lars
2013-08-15  5:05       ` [Bloat] " Vijay Subramanian

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=CAA93jw7Omv-j7u-wHPwyuKN5y-htEr+G248_-4jbZRveOBzwMg@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=aqm@ietf.org \
    --cc=bloat@lists.bufferbloat.net \
    --cc=iccrg@irtf.org \
    --cc=naeem.khademi@gmail.com \
    /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