netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jakub.kicinski@netronome.com
Cc: oss-drivers@netronome.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 00/14] gred: add offload support
Date: Mon, 19 Nov 2018 18:54:06 -0800 (PST)	[thread overview]
Message-ID: <20181119.185406.416570201079064911.davem@davemloft.net> (raw)
In-Reply-To: <20181119232150.13038-1-jakub.kicinski@netronome.com>

From: Jakub Kicinski <jakub.kicinski@netronome.com>
Date: Mon, 19 Nov 2018 15:21:36 -0800

> This series adds support for GRED offload in the nfp driver.  So
> far we have only supported the RED Qdisc offload, but we need a
> way to differentiate traffic types e.g. based on DSCP marking.
> 
> It may seem like PRIO+RED is a good match for this job, however,
> (a) we don't need strict priority behaviour of PRIO, and (b) PRIO
> uses the legacy way of mapping ToS fields to bands, which is quite
> awkward and limitting.
> 
> The less commonly used GRED Qdisc is a better much for the scenario,
> it allows multiple sets of RED parameters and queue lengths to be
> maintained with a single FIFO queue.  This is exactly how nfp offload
> behaves.  We use a trivial u32 classifier to assign packets to virtual
> queues.
> 
> There is also the minor advantage that GRED can't have its child
> changed, therefore limitting ways in which the configuration of SW
> path can diverge from HW offload.
> 
> Last patch of the series adds support for (G)RED in non-ECN mode,
> where packets are dropped instead of marked.

Series applied, thanks Jakub.

      parent reply	other threads:[~2018-11-20 13:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-19 23:21 [PATCH net-next 00/14] gred: add offload support Jakub Kicinski
2018-11-19 23:21 ` [PATCH net-next 01/14] nfp: abm: map per-band symbols Jakub Kicinski
2018-11-19 23:21 ` [PATCH net-next 02/14] nfp: abm: pass band parameter to functions Jakub Kicinski
2018-11-19 23:21 ` [PATCH net-next 03/14] nfp: abm: size threshold table to account for bands Jakub Kicinski
2018-11-19 23:21 ` [PATCH net-next 04/14] nfp: abm: switch to extended stats for reading packet/byte counts Jakub Kicinski
2018-11-19 23:21 ` [PATCH net-next 05/14] nfp: abm: add up bands for sto/non-sto stats Jakub Kicinski
2018-11-19 23:21 ` [PATCH net-next 06/14] net: sched: gred: add basic Qdisc offload Jakub Kicinski
2018-11-19 23:21 ` [PATCH net-next 07/14] net: sched: gred: support reporting stats from offloads Jakub Kicinski
2018-11-19 23:21 ` [PATCH net-next 08/14] nfp: abm: wrap RED parameters in bands Jakub Kicinski
2018-11-19 23:21 ` [PATCH net-next 09/14] nfp: abm: add GRED offload Jakub Kicinski
2018-11-19 23:21 ` [PATCH net-next 10/14] net: sched: cls_u32: add res to offload information Jakub Kicinski
2018-11-19 23:21 ` [PATCH net-next 11/14] nfp: abm: calculate PRIO map len and check mailbox size Jakub Kicinski
2018-11-19 23:21 ` [PATCH net-next 12/14] nfp: abm: add functions to update DSCP -> virtual queue map Jakub Kicinski
2018-11-19 23:21 ` [PATCH net-next 13/14] nfp: abm: add cls_u32 offload for simple band classification Jakub Kicinski
2018-11-19 23:21 ` [PATCH net-next 14/14] nfp: abm: add support for more threshold actions Jakub Kicinski
2018-11-20  2:54 ` David Miller [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=20181119.185406.416570201079064911.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=jakub.kicinski@netronome.com \
    --cc=netdev@vger.kernel.org \
    --cc=oss-drivers@netronome.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;
as well as URLs for NNTP newsgroup(s).