netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Sowden <jeremy@azazel.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Netfilter Devel <netfilter-devel@vger.kernel.org>
Subject: [nft PATCH v2 0/3] parser: refactor and extend limit rate rules
Date: Fri, 29 Oct 2021 21:40:06 +0100	[thread overview]
Message-ID: <20211029204009.954315-1-jeremy@azazel.net> (raw)

The first two patches introduce new rules to deduplicate the code for
parsing `limit rate` expressions and make it easier to extend the
syntax.

The third patch extends the syntax to handle expressions like `limit
rate 1 mbytes / second`, which are not currently supported.

Changes since v1:

 * add patches 1 & 2 in order to simplify the new rule added in patch 3.

Jeremy Sowden (3):
  parser: add new `limit_bytes` rule
  parser: add `limit_rate_pkts` and `limit_rate_bytes` rules
  parser: extend limit syntax

 include/datatype.h           |   4 +
 src/parser_bison.y           | 141 ++++++++++++++++++-----------------
 tests/py/any/limit.t         |   5 ++
 tests/py/any/limit.t.json    |  39 ++++++++++
 tests/py/any/limit.t.payload |  13 ++++
 5 files changed, 134 insertions(+), 68 deletions(-)

-- 
2.33.0


             reply	other threads:[~2021-10-29 20:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-29 20:40 Jeremy Sowden [this message]
2021-10-29 20:40 ` [nft PATCH v2 1/3] parser: add new `limit_bytes` rule Jeremy Sowden
2021-10-29 20:40 ` [nft PATCH v2 2/3] parser: add `limit_rate_pkts` and `limit_rate_bytes` rules Jeremy Sowden
2021-10-29 20:40 ` [nft PATCH v2 3/3] parser: extend limit syntax Jeremy Sowden
2021-11-02 11:44 ` [nft PATCH v2 0/3] parser: refactor and extend limit rate rules Pablo Neira Ayuso

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=20211029204009.954315-1-jeremy@azazel.net \
    --to=jeremy@azazel.net \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.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).