| To: | "David S. Miller" <davem@xxxxxxxxxx> |
|---|---|
| Subject: | Re: Getting details about an 802.1q VLAN interface from userspace |
| From: | jamal <hadi@xxxxxxxxxx> |
| Date: | Tue, 18 Feb 2003 21:48:34 -0500 (EST) |
| Cc: | wjhun@xxxxxxxxx, "" <greearb@xxxxxxxxxxxxxxx>, "" <netdev@xxxxxxxxxxx> |
| In-reply-to: | <20030217.182915.41644338.davem@xxxxxxxxxx> |
| References: | <20030213143921.A21977@xxxxxxxxx> <20030217.182915.41644338.davem@xxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
I think these should be new attributes to RTM_*LINK. No need to define a new message. cheers, jamal On Mon, 17 Feb 2003, David S. Miller wrote: > 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: | Re: [PATCH] subset of RFC2553, Bruce Allan |
|---|---|
| Next by Date: | Re: NAPI note, jamal |
| Previous by Thread: | Re: Getting details about an 802.1q VLAN interface from userspace, David S. Miller |
| Next by Thread: | Re: Getting details about an 802.1q VLAN interface from userspace, David S. Miller |
| Indexes: | [Date] [Thread] [Top] [All Lists] |