From: Patrick McHardy <kaber@trash.net>
To: Chris Leech <christopher.leech@intel.com>
Cc: netdev@vger.kernel.org
Subject: Re: [VLAN] set_rx_mode support for unicast address list
Date: Thu, 24 Jan 2008 18:27:31 +0100 [thread overview]
Message-ID: <4798CA83.4080203@trash.net> (raw)
In-Reply-To: <20080124160738.11781.23745.stgit@localhost.localdomain>
Chris Leech wrote:
> Reuse the existing logic for multicast list synchronization for the unicast
> address list. The core of dev_mc_sync/unsync are split out as
> __dev_addr_sync/unsync and moved from dev_mcast.c to dev.c. These are then
> used to implement dev_unicast_sync/unsync as well.
>
> I'm working on cleaning up Intel's FCoE stack, which generates new MAC
> addresses from the fibre channel device id assigned by the fabric as per the
> current draft specification in T11. When using such a protocol in a VLAN
> environment it would be nice to not always be forced into promiscuous mode,
> assuming the underlying Ethernet driver supports multiple unicast addresses as
> well.
Looks good, applied. Thanks Chris.
next prev parent reply other threads:[~2008-01-24 17:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-24 16:07 [VLAN] set_rx_mode support for unicast address list Chris Leech
2008-01-24 17:27 ` Patrick McHardy [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-01-29 15:09 [VLAN]: " Patrick McHardy
2008-02-01 0:54 ` David Miller
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=4798CA83.4080203@trash.net \
--to=kaber@trash.net \
--cc=christopher.leech@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).