From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Or Gerlitz <gerlitz.or@gmail.com>
Cc: David Miller <davem@davemloft.net>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Linux Netdev List <netdev@vger.kernel.org>,
nhorman@redhat.com, sassmann@redhat.com, jogreene@redhat.com
Subject: Re: [net-next] i40e: enable fdb add code, remove unused code
Date: Fri, 21 Nov 2014 21:53:44 -0800 [thread overview]
Message-ID: <1416635624.2280.107.camel@jtkirshe-mobl> (raw)
In-Reply-To: <CAJ3xEMhRw=NLQOYAQ1X6UUm9nvpaJxcuVt_DTNiybAbDJG=qJw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 739 bytes --]
On Fri, 2014-11-21 at 06:50 +0200, Or Gerlitz wrote:
> On Fri, Nov 21, 2014 at 2:30 AM, Jeff Kirsher
> <jeffrey.t.kirsher@intel.com> wrote:
> > From: Jesse Brandeburg <jesse.brandeburg@intel.com>
>
> > The fdb_add functionality is important to i40e because it is needed
> > for a workaround to allow bridges to work correctly on the i40e
> > hardware.
>
> Can you please shed more light on the precise problem and solution? I
> wonder if one or two of them are generic... so might can/need land
> somewhere upper...
This is not a generic problem, it is an errata related to source pruning
that can be worked around by adding VSI MAC addresses to the HW filters.
Information about it can be found in the driver readme.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-11-22 5:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 0:30 [net-next] i40e: enable fdb add code, remove unused code Jeff Kirsher
2014-11-21 4:50 ` Or Gerlitz
2014-11-22 5:53 ` Jeff Kirsher [this message]
2014-11-21 7:50 ` Jiri Pirko
2014-11-22 21:56 ` 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=1416635624.2280.107.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=davem@davemloft.net \
--cc=gerlitz.or@gmail.com \
--cc=jesse.brandeburg@intel.com \
--cc=jogreene@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=sassmann@redhat.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).