netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Taht <dave@taht.net>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: Leslie Monis <lesliemonis@gmail.com>,
	netdev@vger.kernel.org, dave.taht@gmail.com
Subject: Re: [PATCH net-next v2 0/7] net: sched: pie: align PIE implementation with RFC 8033
Date: Mon, 25 Feb 2019 06:11:25 -0800	[thread overview]
Message-ID: <87ftsc2c1e.fsf@taht.net> (raw)
In-Reply-To: <19575745-ad10-be2d-6259-5fe39fa71264@mojatatu.com> (Jamal Hadi Salim's message of "Mon, 25 Feb 2019 08:47:13 -0500")

Jamal Hadi Salim <jhs@mojatatu.com> writes:

> On 2019-02-25 8:43 a.m., Jamal Hadi Salim wrote:
>> On 2019-02-25 5:20 a.m., Leslie Monis wrote:
>>> The current implementation of the PIE queuing discipline is
>>> according to the
>>> IETF draft [http://tools.ietf.org/html/draft-pan-aqm-pie-00] and
>>> the paper
>>> [PIE: A Lightweight Control Scheme to Address the Bufferbloat Problem].
>>> However, a lot of necessary modifications and enhancements have
>>> been proposed
>>> in RFC 8033, which have not yet been incorporated in the source
>>> code of Linux.
>>> This patch series helps in achieving the same.
>>>
>>> Performance tests carried out using Flent [https://flent.org/]
>>>
>>
>> +Cc the authors of PIE to double check these values.
>> Please respond (it is how open source works!) and N/ACK
>
> Great. Bouncing addresses.
> D. Taht - can you look at this?

Whose addresses are bouncing? The folk that did pie originally were
mostly contractors and long ago moved on to other things.

My taht.net address tends to bounce to vger as I long ago mandated
starttls on all email transactions which is why I use my gmail account
for postings there. I keep hoping that one day vger will support
starttls... posting it here as I'm an optimist. I wasn't expecting to be
cc'd on this submittal....

Pie seems to be mostly an abandoned CISCO effort outside of docsis-pie,
at least at the moment. I've heard not a peep from them in years.
(fq_codel seems to have mostly "won" in our world)

I did review all these changes when they went by in v1, and aside from
the ecn mistake ending up in the final RFC when I wasn't looking[1],
approve of these changes to sch_pie to make it compliant with the rfc,
finally.

[1] We proposed refining pie's ecn handling here:

https://github.com/gautamramk/FQ-PIE-for-Linux-Kernel/issues/2

Anyway:

Acked-by: Dave Taht <dave.taht@gmail.com>


  reply	other threads:[~2019-02-25 14:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-25 10:20 [PATCH net-next v2 0/7] net: sched: pie: align PIE implementation with RFC 8033 Leslie Monis
2019-02-25 10:20 ` [PATCH net-next v2 1/7] net: sched: pie: change value of QUEUE_THRESHOLD Leslie Monis
2019-02-25 10:20 ` [PATCH net-next v2 2/7] net: sched: pie: change default value of pie_params->target Leslie Monis
2019-02-25 10:20 ` [PATCH net-next v2 3/7] net: sched: pie: change default value of pie_params->tupdate Leslie Monis
2019-02-25 10:20 ` [PATCH net-next v2 4/7] net: sched: pie: change initial value of pie_vars->burst_time Leslie Monis
2019-02-25 10:20 ` [PATCH net-next v2 5/7] net: sched: pie: add more cases to auto-tune alpha and beta Leslie Monis
2019-02-25 17:40   ` David Miller
2019-02-25 18:04     ` Leslie Monis
2019-02-26  5:31   ` kbuild test robot
2019-02-26  6:48   ` kbuild test robot
2019-02-25 10:20 ` [PATCH net-next v2 6/7] net: sched: pie: add derandomization mechanism Leslie Monis
2019-02-25 10:20 ` [PATCH net-next v2 7/7] net: sched: pie: update references Leslie Monis
2019-02-25 13:43 ` [PATCH net-next v2 0/7] net: sched: pie: align PIE implementation with RFC 8033 Jamal Hadi Salim
2019-02-25 13:47   ` Jamal Hadi Salim
2019-02-25 14:11     ` Dave Taht [this message]
2019-02-25 14:33       ` Jamal Hadi Salim
2019-02-25 15:04       ` Leslie Monis

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=87ftsc2c1e.fsf@taht.net \
    --to=dave@taht.net \
    --cc=dave.taht@gmail.com \
    --cc=jhs@mojatatu.com \
    --cc=lesliemonis@gmail.com \
    --cc=netdev@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).