From: Stephen Hemminger <stephen@networkplumber.org>
To: Leslie Monis <lesliemonis@gmail.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
"Mohit P . Tahiliani" <tahiliani@nitk.edu.in>,
Dave Taht <dave.taht@gmail.com>,
Jamal Hadi Salim <jhs@mojatatu.com>
Subject: Re: [PATCH net-next v3 0/7] net: sched: pie: align PIE implementation with RFC 8033
Date: Tue, 26 Feb 2019 07:50:57 -0800 [thread overview]
Message-ID: <20190226075057.1e76bba7@shemminger-XPS-13-9360> (raw)
In-Reply-To: <20190226082046.GA2266@Inspiron-3521>
On Tue, 26 Feb 2019 13:50:46 +0530
Leslie Monis <lesliemonis@gmail.com> wrote:
> On Mon, Feb 25, 2019 at 04:38:11PM -0800, Stephen Hemminger wrote:
> > On Tue, 26 Feb 2019 00:39:54 +0530
> > Leslie Monis <lesliemonis@gmail.com> 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/]
> > >
> > > Changes from v2 to v3:
> > > - Used div_u64() instead of direct division after explicit type casting as
> > > recommended by David
> > >
> > > Changes from v1 to v2:
> > > - Excluded the patch setting PIE dynamically active/inactive as the test
> > > results were unsatisfactory
> > > - Fixed a scaling issue when adding more auto-tuning cases which caused
> > > local variables to underflow
> > > - Changed the long if/else chain to a loop as suggested by Stephen
> > > - Changed the position of the accu_prob variable in the pie_vars
> > > structure as recommended by Stephen
> > >
> > > Mohit P. Tahiliani (7):
> > > net: sched: pie: change value of QUEUE_THRESHOLD
> > > net: sched: pie: change default value of pie_params->target
> > > net: sched: pie: change default value of pie_params->tupdate
> > > net: sched: pie: change initial value of pie_vars->burst_time
> > > net: sched: pie: add more cases to auto-tune alpha and beta
> > > net: sched: pie: add derandomization mechanism
> > > net: sched: pie: update references
> > >
> > > include/uapi/linux/pkt_sched.h | 2 +-
> > > net/sched/sch_pie.c | 107 ++++++++++++++++++++-------------
> > > 2 files changed, 66 insertions(+), 43 deletions(-)
> >
> > Are you concerned at all that changes to default values might change
> > expected behavior of existing users?
>
> Hi Stephen,
>
> As Dave mentioned, the changes which we have made do not really change the
> behaviour of the aqm drastically. Our performance tests show that these changes
> improve performance without any side-effects. So existing users (if there are
> any) should not be negatively affected in any way.
Thanks for answering. Looks good
prev parent reply other threads:[~2019-02-26 15:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 19:09 [PATCH net-next v3 0/7] net: sched: pie: align PIE implementation with RFC 8033 Leslie Monis
2019-02-25 19:09 ` [PATCH net-next v3 1/7] net: sched: pie: change value of QUEUE_THRESHOLD Leslie Monis
2019-02-25 19:09 ` [PATCH net-next v3 2/7] net: sched: pie: change default value of pie_params->target Leslie Monis
2019-02-25 19:09 ` [PATCH net-next v3 3/7] net: sched: pie: change default value of pie_params->tupdate Leslie Monis
2019-02-25 19:09 ` [PATCH net-next v3 4/7] net: sched: pie: change initial value of pie_vars->burst_time Leslie Monis
2019-02-25 19:09 ` [PATCH net-next v3 5/7] net: sched: pie: add more cases to auto-tune alpha and beta Leslie Monis
2019-02-25 19:10 ` [PATCH net-next v3 6/7] net: sched: pie: add derandomization mechanism Leslie Monis
2019-02-25 19:10 ` [PATCH net-next v3 7/7] net: sched: pie: update references Leslie Monis
2019-02-25 22:21 ` [PATCH net-next v3 0/7] net: sched: pie: align PIE implementation with RFC 8033 David Miller
2019-02-26 0:38 ` Stephen Hemminger
2019-02-26 1:02 ` Dave Taht
2019-02-26 8:20 ` Leslie Monis
2019-02-26 15:50 ` Stephen Hemminger [this message]
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=20190226075057.1e76bba7@shemminger-XPS-13-9360 \
--to=stephen@networkplumber.org \
--cc=dave.taht@gmail.com \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=lesliemonis@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=tahiliani@nitk.edu.in \
/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