From: David Miller <davem@davemloft.net>
To: dsa@cumulusnetworks.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] net: vrf: Add support for local traffic to local addresses
Date: Mon, 06 Jun 2016 15:56:43 -0700 (PDT) [thread overview]
Message-ID: <20160606.155643.1439926167947457716.davem@davemloft.net> (raw)
In-Reply-To: <20160606.151228.325662111382577833.davem@davemloft.net>
From: David Miller <davem@davemloft.net>
Date: Mon, 06 Jun 2016 15:12:28 -0700 (PDT)
> From: David Ahern <dsa@cumulusnetworks.com>
> Date: Thu, 2 Jun 2016 13:15:09 -0700
>
>> Add support for locally originated traffic to VRF-local addresses,
>> be it addresses on enslaved devices or addresses on the VRF device:
> ...
>
> Series applied, but I've been wondering what happens to hw offloads
> when these VRF devices sit in the middle.
>
> Does TSO et al. still occur properly?
Actually I have to revert this series, ip6_input() is not an exported
module symbol.
If you're only build testing things like this with everything "=y",
please reconsider.
next prev parent reply other threads:[~2016-06-06 22:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 20:15 [PATCH net-next 0/3] net: vrf: Add support for local traffic to local addresses David Ahern
2016-06-02 20:15 ` [PATCH net-next 1/3] net: vrf: Minor refactoring for local address patches David Ahern
2016-06-02 20:15 ` [PATCH net-next 2/3] net: vrf: ipv4 support for local traffic to local addresses David Ahern
2016-06-02 20:15 ` [PATCH net-next 3/3] net: vrf: ipv6 " David Ahern
2016-06-06 22:12 ` [PATCH net-next 0/3] net: vrf: Add " David Miller
2016-06-06 22:56 ` David Miller [this message]
2016-06-06 23:01 ` David Ahern
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=20160606.155643.1439926167947457716.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--cc=netdev@vger.kernel.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).