All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Bernat <vincent@bernat.im>
To: David Ahern <dsa@cumulusnetworks.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Nicolas Dichtel <nicolas.dichtel@6wind.com>,
	Wilson Kok <wkok@cumulusnetworks.com>,
	netdev@vger.kernel.org
Subject: Re: [net v1] fib_rules: interface group matching
Date: Wed, 14 Sep 2016 18:01:10 +0200	[thread overview]
Message-ID: <8760pypj21.fsf@zoro.exoscale.ch> (raw)
In-Reply-To: <c4f00f4e-aad3-f3d4-3c7c-8fe39c8f1720@cumulusnetworks.com> (David Ahern's message of "Wed, 14 Sep 2016 09:25:49 -0600")

 ❦ 14 septembre 2016 17:25 CEST, David Ahern <dsa@cumulusnetworks.com> :

>> I could just give more time to VRF. I also had some concerns over
>> performance with the way Netfilter integration is done, but I understand
>> that I could just stay away from POSTROUTING rules which is the only
>> hook executed twice?

> With the changes that were committed this past weekend, the VRF code
> is now setup where I can set a flag on a per VRF basis to disable the
> extra rx and tx processing - ie., no network taps, no netfilter, no
> qdisc, etc. Drops the overhead of VRF to ~3% maybe a bit less. I need
> to think about the user api a bit more and formalize the patch. Given
> my other commitments that probably won't happen until mid-October. But
> in terms of a building block, the overhead of VRF is continuing to
> drop.

Fine by me. We can drop my patch.

Thanks!
-- 
Program defensively.
            - The Elements of Programming Style (Kernighan & Plauger)

      reply	other threads:[~2016-09-14 16:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14 12:40 [net v1] fib_rules: interface group matching Vincent Bernat
2016-09-14 12:43 ` Vincent Bernat
2016-09-14 14:15 ` David Ahern
2016-09-14 14:25   ` Vincent Bernat
2016-09-14 14:39     ` David Ahern
2016-09-14 15:14       ` Vincent Bernat
2016-09-14 15:25         ` David Ahern
2016-09-14 16:01           ` Vincent Bernat [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=8760pypj21.fsf@zoro.exoscale.ch \
    --to=vincent@bernat.im \
    --cc=davem@davemloft.net \
    --cc=dsa@cumulusnetworks.com \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.dichtel@6wind.com \
    --cc=wkok@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 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.