From: "David S. Miller" <davem@redhat.com>
To: christopher.leech@intel.com
Cc: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: [BETA-0.92] Third test release of Tigon3 driver
Date: Thu, 28 Feb 2002 14:57:18 -0800 (PST) [thread overview]
Message-ID: <20020228.145718.120901435.davem@redhat.com> (raw)
In-Reply-To: <BD9B60A108C4D511AAA10002A50708F22C144F@orsmsx118.jf.intel.com>
In-Reply-To: <BD9B60A108C4D511AAA10002A50708F22C144F@orsmsx118.jf.intel.com>
From: "Leech, Christopher" <christopher.leech@intel.com>
Date: Thu, 28 Feb 2002 13:57:07 -0800
> e1000 has a VLAN filter type on-chip, which complicates things a tiny bit.
The filtering is separate from the tagging. Filtering lets the hardware
ignore tagged packets for VLANs that it's not a member of. The vlan_group
structure isn't well laid out for this, but it would be possible to search
for non-NULL values in the vlan_devices array to get the VLAN IDs for
filtering. The driver would need to know when new VLAN IDs were added to
the group.
This is exactly the kind of thing I wanted people to discover
and discuss. Thanks for bringing this up.
It would be quite simple to hook back into your driver for this
purpose, proposed API:
/* For netdev->features */
#define NETIF_F_HW_VLAN_FILTER 1024
/* For NETIF_F_VLAN_RX_FILTER devices */
void (*vlan_rx_new_vid)(struct net_device *dev,
unsigned short vid);
We call dev->vlan_rx_kill_vid() in all cases because it has to
deal with interlocking, as described in an earlier email.
But if NETIF_F_HW_VLAN_FILTER is set, when new VLAN devices are
registered that go through your card, you will get a
dev->vlan_rx_new_vid() call.
I do not think you would need any more informatin than the
VID itself. If this is wrong, tell me now :-)
next prev parent reply other threads:[~2002-02-28 23:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-28 21:57 [BETA-0.92] Third test release of Tigon3 driver Leech, Christopher
2002-02-28 22:57 ` David S. Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-28 23:11 Leech, Christopher
2002-02-27 13:51 David S. Miller
2002-02-27 15:44 ` Jeff Garzik
2002-02-28 17:22 ` Pasi Kärkkäinen
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=20020228.145718.120901435.davem@redhat.com \
--to=davem@redhat.com \
--cc=christopher.leech@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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