From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Patrick McHardy <kaber@trash.net>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [NET 00/02]: MACVLAN driver
Date: Tue, 19 Jun 2007 15:29:28 -0700 [thread overview]
Message-ID: <20070619152928.38738411@localhost.localdomain> (raw)
In-Reply-To: <4678472D.5050907@trash.net>
On Tue, 19 Jun 2007 23:14:21 +0200
Patrick McHardy <kaber@trash.net> wrote:
> Stephen Hemminger wrote:
> > Looks good. I have some changes to allow devices with multiple MAC addresses
> > (never finished). This device could use that.
>
>
> How would the driver do that? I was thinking about using dev_add_mc,
> but wasn't sure if that would work with all drivers for non-multicast
> addresses.
>
Basically, add a new dev_add_addr hook to netdevice.
Drivers that can do it, would add the hook. If driver didn't have hook,
then core would put device into promiscuous. Most devices with multicast
allow non-multicast addresses, so it could be a simple extension.
Rather than doing it for all devices, wanted to go in one by one and test.
--
Stephen Hemminger <shemminger@linux-foundation.org>
next prev parent reply other threads:[~2007-06-19 22:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 13:08 [NET 00/02]: MACVLAN driver Patrick McHardy
2007-06-19 13:08 ` [ETHERNET 01/02]: Validate new address in eth_mac_addr Patrick McHardy
2007-06-19 13:08 ` [NET 02/02]: Add MACVLAN driver Patrick McHardy
2007-06-19 16:00 ` [NET 00/02]: " Stephen Hemminger
2007-06-19 19:53 ` Chris Leech
2007-06-19 21:14 ` Patrick McHardy
2007-06-19 22:29 ` Stephen Hemminger [this message]
2007-06-19 22:48 ` David Miller
2007-06-19 23:44 ` Patrick McHardy
2007-06-20 6:34 ` Jeff Garzik
2007-06-20 19:35 ` Prafulla Deuskar
2007-06-21 14:57 ` Patrick McHardy
-- strict thread matches above, loose matches on Subject: below --
2007-06-24 4:52 Mark Smith
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=20070619152928.38738411@localhost.localdomain \
--to=shemminger@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--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).