From: Jamal Hadi Salim <jhs@mojatatu.com>
To: Sridhar Samudrala <sridhar.samudrala@intel.com>,
sfeldma@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] switchdev: add support for fdb add/del/dump via switchdev_port_obj ops.
Date: Wed, 06 May 2015 19:35:12 -0400 [thread overview]
Message-ID: <554AA530.7000702@mojatatu.com> (raw)
In-Reply-To: <1430949253-6358-1-git-send-email-sridhar.samudrala@intel.com>
On 05/06/15 17:54, Sridhar Samudrala wrote:
> - introduce port fdb obj and generic switchdev_port_fdb_add/del/dump()
> - use switchdev_port_fdb_add/del/dump in rocker/team/bonding ndo ops.
> - add support for fdb obj in switchdev_port_obj_add/del/dump()
> - switch rocker to implement fdb ops via switchdev_ops
>
> Signed-off-by: Sridhar Samudrala <sridhar.samudrala@intel.com>
> Signed-off-by: Scott Feldman <sfeldma@gmail.com>
> ---
So i raised this earlier. DaveM also chimed in - but it seems still
in there.
i havent been following the discussion and i may have missed
the agreement to keep the new IDs. Could we not just have used netlink
IDs (as opposed to a new SWITCHDEV_OBJ_PORT_FDB id)?
> +int switchdev_port_fdb_add(struct ndmsg *ndm, struct nlattr *tb[],
> + struct net_device *dev, const unsigned char *addr,
> + u16 vid, u16 nlm_flags)
> +{
> + struct switchdev_obj obj = {
> + .id = SWITCHDEV_OBJ_PORT_FDB,
> + .fdb = {
> + .addr = addr,
> + .vid = vid,
> + },
> + };
> +
> + return switchdev_port_obj_add(dev, &obj);
> +}
cheers,
jamal
next prev parent reply other threads:[~2015-05-06 23:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 21:54 [PATCH net-next] switchdev: add support for fdb add/del/dump via switchdev_port_obj ops Sridhar Samudrala
2015-05-06 23:35 ` Jamal Hadi Salim [this message]
2015-05-07 4:42 ` Samudrala, Sridhar
2015-05-07 12:51 ` roopa
2015-05-08 12:05 ` Jamal Hadi Salim
2015-05-08 20:44 ` Samudrala, Sridhar
2015-05-08 20:58 ` Scott Feldman
2015-05-11 13:15 ` Jamal Hadi Salim
2015-05-12 22:20 ` David Miller
2015-05-13 0:07 ` Samudrala, Sridhar
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=554AA530.7000702@mojatatu.com \
--to=jhs@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=sfeldma@gmail.com \
--cc=sridhar.samudrala@intel.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).