From: John Fastabend <john.r.fastabend@intel.com>
To: Vlad Yasevich <vyasevic@redhat.com>, Amir Vadai <amirv@mellanox.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: [RFC PATCH 3/3] mlx4: Use default fdb handlers when not multifunction.
Date: Wed, 27 Feb 2013 20:27:51 -0800 [thread overview]
Message-ID: <512EDCC7.8050207@intel.com> (raw)
In-Reply-To: <1361987164-15280-4-git-send-email-vyasevic@redhat.com>
On 2/27/2013 9:46 AM, Vlad Yasevich wrote:
> Allow the use of ndo_dflt_fdb_<add|del|dump> when the
> adapter is not configured with virtual functins (!mlx4_is_mfunc())
> This allows proper IFF_UNICAST_FLT support and allows for
> additional handling by the driver if needed.
>
> CC: Amir Vadai <amirv@mellanox.com>
> Signed-off-by: Vlad Yasevich <vyasevic@redhat.com>
> ---
> drivers/net/ethernet/mellanox/mlx4/en_netdev.c | 12 +++---------
> 1 files changed, 3 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/net/ethernet/mellanox/mlx4/en_netdev.c b/drivers/net/ethernet/mellanox/mlx4/en_netdev.c
> index 5385474..5732025 100644
> --- a/drivers/net/ethernet/mellanox/mlx4/en_netdev.c
> +++ b/drivers/net/ethernet/mellanox/mlx4/en_netdev.c
> @@ -1934,7 +1934,7 @@ static int mlx4_en_fdb_add(struct ndmsg *ndm, struct nlattr *tb[],
Amir are the default ops good enough here?
> int err;
>
> if (!mlx4_is_mfunc(mdev))
> - return -EOPNOTSUPP;
> + return ndo_dflt_fdb_add(ndm, tb, dev, addr, flags);
>
> /* Hardware does not support aging addresses, allow only
> * permanent addresses if ndm_state is given
> @@ -1968,7 +1968,7 @@ static int mlx4_en_fdb_del(struct ndmsg *ndm,
> int err;
>
> if (!mlx4_is_mfunc(mdev))
> - return -EOPNOTSUPP;
> + return ndo_dflt_fdb_del(ndm, tb, dev, addr);
>
> if (ndm->ndm_state && !(ndm->ndm_state & NUD_PERMANENT)) {
> en_info(priv, "Del FDB only supports static addresses\n");
> @@ -1989,13 +1989,7 @@ static int mlx4_en_fdb_dump(struct sk_buff *skb,
> struct netlink_callback *cb,
> struct net_device *dev, int idx)
> {
same comment here. Don't define this op and we get the same behavior?
.John
next prev parent reply other threads:[~2013-02-28 4:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 17:46 [RFC PATCH 0/3] Provide default fdb operation to allow mac filter Vlad Yasevich
2013-02-27 17:46 ` [RFC PATCH 1/3] net: generic fdb support for drivers without ndo_fdb_<op> Vlad Yasevich
2013-02-27 17:46 ` [RFC PATCH 2/3] ixgbe: Use default fdb handlers when not in VF mode Vlad Yasevich
2013-02-28 4:26 ` John Fastabend
2013-02-28 14:46 ` Vlad Yasevich
2013-02-27 17:46 ` [RFC PATCH 3/3] mlx4: Use default fdb handlers when not multifunction Vlad Yasevich
2013-02-28 4:27 ` John Fastabend [this message]
[not found] ` <CAJZOPZLcphuZEXR+jhT35=qtOq9bfxWzWEokN6UrMorciCvvsA@mail.gmail.com>
2013-02-28 12:32 ` Yan Burman
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=512EDCC7.8050207@intel.com \
--to=john.r.fastabend@intel.com \
--cc=amirv@mellanox.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=vyasevic@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).