From: "Leech, Christopher" <christopher.leech@intel.com>
To: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: hardware VLAN acceleration (RE: [BETA-0.92] Third test release of Tigon3 driver)
Date: Thu, 28 Feb 2002 13:47:25 -0800 [thread overview]
Message-ID: <BD9B60A108C4D511AAA10002A50708F22C144E@orsmsx118.jf.intel.com> (raw)
> On Wed, 27 Feb 2002, David S. Miller wrote:
>
> > [FEATURE] Yay, real HW acceleration hooks in the 802.1q VLAN layer.
> > Tigon3 takes advantage of it.
>
> > Adding support to the Acenic driver should be pretty easy and I'll
> > try to do that before catching some sleep. Jeff could also probably
> > cook up something quick for the e1000.
>
> That would be nice, a common way for hw-vlans is a good thing.
>
> Intel has also their own (kludgy?) way of doing hw-vlans in
> the current driver?
>
> - Pasi Kärkkäinen
The version of e1000 that Jeff merged in has no hardware VLAN capabilities
right now, the version distributed from Intel's web site has hooks for the
binary only iANS teaming/VLAN product.
That being said, I will add support to e1000 for a standard kernel interface
(e100 too, but there are other things to fix first). David's interface
looks very nice to me, especially in it's clear advertisement of
capabilities and simple transmit and receive design. Intel's hardware will
have no problem working with it.
I did have some questions about the entry points.
Is vlan_rx_kill_vid only there to ensure locking between vlan_hwaccel_rx and
unregister_802_1Q_vlan_dev? If so, could this be handled outside of the
driver?
Also, when a vlan dev is unregistered, does the driver need to know that the
vlan_group passed in to vlan_rx_register is no longer valid?
Chris
--
Chris Leech <christopher.leech@intel.com>
Network Software Engineer
UNIX/Linux/Netware Development Group
LAN Access Division, Intel
next reply other threads:[~2002-02-28 21:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-28 21:47 Leech, Christopher [this message]
2002-02-28 22:51 ` hardware VLAN acceleration David S. 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=BD9B60A108C4D511AAA10002A50708F22C144E@orsmsx118.jf.intel.com \
--to=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
all inboxes | Powered by JetHome®