From: John Fastabend <john.r.fastabend@intel.com>
To: vyasevic@redhat.com
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [RFC PATCH] core: Add ioctls to control device unicast hw addresses
Date: Tue, 26 Feb 2013 13:58:39 -0800 [thread overview]
Message-ID: <512D300F.20405@intel.com> (raw)
In-Reply-To: <512D1A01.9020301@redhat.com>
[...]
>>>
>>>
>>> [RFC PATCH] rtnetlink: Add support for adding/removing additional hw
>>> addresses.
>>>
>>> Add an ability to add and remove HW addresses to the device
>>> unicast and multicast address lists. Right now, we only have
>>> an ioctl() to manage the multicast addresses and there is no
>>> way the manage the unicast list.
>>>
>>> Signed-off-by: Vlad Yasevich <vyasevic@redhat.com>
>>
>> This is a step in the right direction, and you're right that there is
>> a difficulty in detecting whether support exists or not.
>>
>> I am so surprised that we've have ->set_rx_mode() support for multiple
>> unicast MAC addresses in so many drivers all this time, yet no way
>> outside of FDB to make use of it at all.
>
> And even that is not always available. In most drivers it requires
> module parameters or other explicit configuration steps. Meanwhile
> set_rx_mode() doesn't seem to depend on any of those and just does the
> right thing.
>
> For what I was trying to do ioctl() was a really easy way out for both
> kernel and user space implementation, so I gave is shot.
>
> -vlad
>
Don't we already support this with
int (*ndo_fdb_add)(struct ndmsg *ndm,
struct nlattr *tb[],
struct net_device *dev,
const unsigned char *addr,
u16 flags);
int (*ndo_fdb_del)(struct ndmsg *ndm,
struct nlattr *tb[],
struct net_device *dev,
const unsigned char *addr);
int (*ndo_fdb_dump)(struct sk_buff *skb,
struct
netlink_callback *cb,
struct net_device *dev,
int idx);
next prev parent reply other threads:[~2013-02-26 21:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 16:59 [RFC PATCH] core: Add ioctls to control device unicast hw addresses Vlad Yasevich
2013-02-26 17:43 ` David Miller
2013-02-26 19:44 ` Vlad Yasevich
2013-02-26 20:03 ` David Miller
2013-02-26 20:24 ` Vlad Yasevich
2013-02-26 20:48 ` David Miller
2013-02-26 21:58 ` John Fastabend [this message]
2013-02-26 22:15 ` David Miller
2013-02-27 2:07 ` John Fastabend
2013-02-27 2:27 ` Vlad Yasevich
2013-02-27 5:01 ` John Fastabend
2013-02-27 5:42 ` Jitendra Kalsaria
2013-02-27 7:34 ` John Fastabend
2013-02-27 15:27 ` Vlad Yasevich
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=512D300F.20405@intel.com \
--to=john.r.fastabend@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.