From: Florian Westphal <fw@strlen.de>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Florian Westphal <fw@strlen.de>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nft 2/3] meta: add short-hand mnemonic for probalistic matching
Date: Thu, 14 Jul 2016 12:52:18 +0200 [thread overview]
Message-ID: <20160714105218.GA24700@breakpoint.cc> (raw)
In-Reply-To: <20160714104108.GA2250@salvia>
Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> On Tue, Jul 05, 2016 at 09:35:34AM +0200, Florian Westphal wrote:
> > Allow users to use a simpler way to specify probalistic matching, e. g.:
> >
> > meta probability 0.5 (match approx. every 2nd packet)
> > meta probability 0.001 (match approx. once every 1000 packets)
> >
> > nft list will still show
> > meta random <= 2147483647
> > meta random <= 4294967
>
> I don't like this asymmetry.
Its changed in patch #3 when adding the shorthand reverse translation.
> What is the usecase for 'meta random' out of this probability case that
> maps to what xt_statistics offers?
Nothing, but the meta random might be interesting to e.g. set random
(ct)mark for load balancing purposes.
next prev parent reply other threads:[~2016-07-14 10:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 7:35 [PATCH nft 1/3] meta: add random and probability match Florian Westphal
2016-07-05 7:35 ` [PATCH nft 1/3] meta: add random expression key Florian Westphal
2016-07-18 19:34 ` Pablo Neira Ayuso
2016-07-18 22:09 ` Florian Westphal
2016-07-05 7:35 ` [PATCH nft 2/3] meta: add short-hand mnemonic for probalistic matching Florian Westphal
2016-07-14 10:41 ` Pablo Neira Ayuso
2016-07-14 10:52 ` Florian Westphal [this message]
2016-07-14 11:32 ` Pablo Neira Ayuso
2016-07-14 12:08 ` Florian Westphal
2016-07-14 12:17 ` Pablo Neira Ayuso
2016-07-05 7:35 ` [PATCH nft 3/3] netlink_delinearize, meta: show meta prandom <= value as probability mnemonic Florian Westphal
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=20160714105218.GA24700@breakpoint.cc \
--to=fw@strlen.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.