From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: roopa@cumulusnetworks.com, netdev@vger.kernel.org,
dsa@cumulusnetworks.com, nikolay@cumulusnetworks.com
Subject: Re: [PATCH RFC net-next 1/4] ipv4: fib_rules: support match on sport, dport and ip proto
Date: Mon, 12 Feb 2018 16:05:10 -0500 (EST) [thread overview]
Message-ID: <20180212.160510.620630476824737121.davem@davemloft.net> (raw)
In-Reply-To: <1518468573.3715.163.camel@gmail.com>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Mon, 12 Feb 2018 12:49:33 -0800
> Any setup with about 20 rules to be evaluated (per packet cost) will
> feel the pain...
>
> I wonder if we could JIT/eBPF this thing.
That's true for the software implementation angle.
But I bet anyone actually using this thing will get it hardware
offloaded.
next prev parent reply other threads:[~2018-02-12 21:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-11 22:26 [PATCH RFC net-next 0/4] fib_rules: support sport, dport and proto match Roopa Prabhu
2018-02-11 22:26 ` [PATCH RFC net-next 1/4] ipv4: fib_rules: support match on sport, dport and ip proto Roopa Prabhu
2018-02-12 20:49 ` Eric Dumazet
2018-02-12 21:05 ` David Miller [this message]
2018-02-12 21:07 ` David Ahern
2018-02-12 21:54 ` Eric Dumazet
2018-02-12 23:03 ` David Ahern
2018-02-13 0:03 ` David Miller
2018-02-13 16:19 ` Roopa Prabhu
2018-02-13 16:34 ` David Miller
2018-02-13 16:36 ` Roopa Prabhu
2018-02-13 18:21 ` Ben Greear
2018-02-11 22:26 ` [PATCH RFC net-next 2/4] ipv6: fib6_rules: support for " Roopa Prabhu
2018-02-11 22:26 ` [PATCH RFC net-next 3/4] ipv4: route: dissect flow in input path if fib rules need it Roopa Prabhu
2018-02-11 22:26 ` [PATCH RFC net-next 4/4] ipv6: " Roopa Prabhu
2018-02-12 7:44 ` Ido Schimmel
2018-02-12 16:21 ` Roopa Prabhu
2018-02-12 20:36 ` [PATCH RFC net-next 0/4] fib_rules: support sport, dport and proto match David Miller
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=20180212.160510.620630476824737121.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=roopa@cumulusnetworks.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).