| To: | wjhun@xxxxxxxxx |
|---|---|
| Subject: | Re: Getting details about an 802.1q VLAN interface from userspace |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Mon, 17 Feb 2003 18:29:15 -0800 (PST) |
| Cc: | greearb@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <20030213143921.A21977@cisco.com> |
| References: | <20030213143921.A21977@cisco.com> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
From: Will Jhun <wjhun@xxxxxxxxx> Date: Thu, 13 Feb 2003 14:39:21 -0800 Is there a better way to get this information via netlink or some ioctl()? Would it be useful if I (or someone) added an ioctl() type to get information about a VLAN interface? (vlan, ifindex of trunking (real_dev) interface, priority maps; basically the content of struct vlan_dev_info) I would accept new netlink interfaces to get and set this information. ioctls are gross and will not be tolerated :) |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH] : shared ipv6 cards, Frank Pavlic |
|---|---|
| Next by Date: | Re: NAPI note, David S. Miller |
| Previous by Thread: | Getting details about an 802.1q VLAN interface from userspace, Will Jhun |
| Next by Thread: | Re: Getting details about an 802.1q VLAN interface from userspace, jamal |
| Indexes: | [Date] [Thread] [Top] [All Lists] |