From: Vlad Yasevich <vyasevic@redhat.com>
To: John Fastabend <john.r.fastabend@intel.com>
Cc: netdev@vger.kernel.org, Gregory Rose <gregory.v.rose@intel.com>
Subject: Re: [PATCH net-next 2/4] ixgbe: Remove driver specific fdb handlers.
Date: Fri, 01 Mar 2013 09:35:15 -0500 [thread overview]
Message-ID: <5130BCA3.3080709@redhat.com> (raw)
In-Reply-To: <51304296.8080106@intel.com>
On 03/01/2013 12:54 AM, John Fastabend wrote:
> On 2/28/2013 3:13 PM, Vlad Yasevich wrote:
>> Remove driver specific fdb handlers since they are the same
>> as the default ones.
>>
>> CC: John Fastabend <john.r.fastabend@intel.com>
>> CC: CC: Gregory Rose <gregory.v.rose@intel.com>
>> Signed-off-by: Vlad Yasevich <vyasevic@redhat.com>
>> ---
>> drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 81
>> -------------------------
>> 1 files changed, 0 insertions(+), 81 deletions(-)
>>
>> diff --git a/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c
>> b/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c
>> index 68478d6..212b74e 100644
>> --- a/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c
>> +++ b/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c
>> @@ -6998,84 +6998,6 @@ static int ixgbe_set_features(struct net_device
>> *netdev,
>> return 0;
>> }
>>
>> -static int ixgbe_ndo_fdb_add(struct ndmsg *ndm, struct nlattr *tb[],
>> - struct net_device *dev,
>> - const unsigned char *addr,
>> - u16 flags)
>> -{
>
> [...]
>
>> - if (is_unicast_ether_addr(addr) || is_link_local_ether_addr(addr)) {
>> - u32 rar_uc_entries = IXGBE_MAX_PF_MACVLANS;
>> -
>> - if (netdev_uc_count(dev) < rar_uc_entries)
>> - err = dev_uc_add_excl(dev, addr);
>> - else
>> - err = -ENOMEM;
>
> OK after talking with Greg I realized there is a problem with
> just removing the add routine.
>
> The problem with this is we lose the ability to indicate the
> hardware table is full and return ENOMEM. Although our set_rx_mode
> routine will put the device in promisc mode this won't forward
> packets from a VF to the PF in the SR-IOV case.
>
> So we either need to leave ixgbe_ndo_fdb_add() or let set_rx_mode
> return an -ENOMEM error. I believe in the first case we can still
> remove the dump and del cases.
>
> Sorry for the hassle took me a second review to catch it.
No problem. That was the reason I left it in the first version (because
of different error handling). I'll restore the add function.
-vlad
>
> .John
next prev parent reply other threads:[~2013-03-01 14:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 23:12 [PATCH net-next 0/4] Provide default fdb operation to allow mac filter setting Vlad Yasevich
2013-02-28 23:13 ` [PATCH net-next 1/4] net: generic fdb support for drivers without ndo_fdb_<op> Vlad Yasevich
2013-02-28 23:13 ` [PATCH net-next 2/4] ixgbe: Remove driver specific fdb handlers Vlad Yasevich
[not found] ` <51304296.8080106@intel.com>
2013-03-01 14:35 ` Vlad Yasevich [this message]
2013-02-28 23:13 ` [PATCH net-next 3/4] mlx4: " Vlad Yasevich
2013-02-28 23:13 ` [PATCH net-next 4/4] qlcnic: Use generic fdb handler when driver options are not enabled Vlad Yasevich
2013-02-28 23:35 ` Jitendra Kalsaria
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=5130BCA3.3080709@redhat.com \
--to=vyasevic@redhat.com \
--cc=gregory.v.rose@intel.com \
--cc=john.r.fastabend@intel.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).