From: Ben Greear <greearb@candelatech.com>
To: "Hen, Shmulik" <shmulik.hen@intel.com>
Cc: netdev@oss.sgi.com
Subject: Re: VLAN patch for 2.4.21
Date: Thu, 07 Aug 2003 00:28:12 -0700 [thread overview]
Message-ID: <3F31FF8C.9080705@candelatech.com> (raw)
In-Reply-To: <E791C176A6139242A988ABA8B3D9B38A014C9471@hasmsx403.iil.intel.com>
Hen, Shmulik wrote:
>>-----Original Message-----
>>From: Ben Greear [mailto:greearb@candelatech.com]
>>Sent: Wednesday, August 06, 2003 3:27 AM
>>To: 'netdev@oss.sgi.com'
>>Subject: VLAN patch for 2.4.21
>>
>>
>>Here is a patch that adds a few new IOCTL options (not new
>>IOCTLs per se) for the 802.1Q VLANs.
>>One ioctl allows one to get the VID for a device by
>>the interface name. A second gets the name of the underlying
>>device for the VLAN device. Tested on x86 and PPC.
>>
>>Comments welcome!
>>
>>Thanks,
>>Ben
>>
>
>
> Oh, this is great. You just saved me the work I was going to do
> for fixing VLAN stuff over bonding :)
> Any idea how to export those in a way that would enable bonding
> and alike to include them without getting dependant on 8021q module
> being loaded ? (I'm guessing inline function in a .h file, but any
> other solution is welcome (coed sample ?).
You can just check the things in the net_device struct directly
I imagine. The calls I added are mainly to provide the info to
user-space.
What information do you need, and where do you need it?
Also, no word yet from the guys who actually take patches, so dunno
if/when this will get into the tree.
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2003-08-07 7:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 6:22 VLAN patch for 2.4.21 Hen, Shmulik
2003-08-07 7:28 ` Ben Greear [this message]
2003-08-07 7:30 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2003-08-07 10:22 Hen, Shmulik
2003-08-07 15:49 ` Ben Greear
2003-08-06 0:27 Ben Greear
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=3F31FF8C.9080705@candelatech.com \
--to=greearb@candelatech.com \
--cc=netdev@oss.sgi.com \
--cc=shmulik.hen@intel.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 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).