| To: | chas@xxxxxxxxxxxxxxxx |
|---|---|
| Subject: | Re: [PATCH][ATM] use rtnl_{lock,unlock} during device operations (take 2) |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Tue, 17 Jun 2003 10:53:33 -0700 (PDT) |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <200306171754.h5HHsWsG000656@xxxxxxxxxxxxxxxxxxxxxxx> |
| References: | <20030606.085558.56056656.davem@xxxxxxxxxx> <200306171754.h5HHsWsG000656@xxxxxxxxxxxxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
From: chas williams <chas@xxxxxxxxxxxxxxxx> Date: Tue, 17 Jun 2003 13:52:32 -0400 In message <20030606.085558.56056656.davem@xxxxxxxxxx>,"David S. Miller" writes : >Tell me it at least uses netlink ;( so i was doing a bit of thinking about this netlink conversion for signalling (and lane and clip and br2684). would i create a new family for each like NETLINK_SIGNALLING, NETLINK_LANE, or create a single new family NETLINK_ATM and multiplex nlmsg_type, or use the existing NETLINK_USERSOCK? Don't user NETLINK_USERSOCK, it's for users :-) Create NETLINK_ATM, and then multiplex like rtnetlink does on the message type. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH][ATM] use rtnl_{lock,unlock} during device operations (take 2), chas williams |
|---|---|
| Next by Date: | Re: [PATCH] IPV6: kill 2 warnings in net/ipv6/ip6_tunnel.c, David S. Miller |
| Previous by Thread: | Re: [PATCH][ATM] use rtnl_{lock,unlock} during device operations (take 2), chas williams |
| Next by Thread: | [PATCH 2.5.72] use alloc_netdev in bonding driver, Stephen Hemminger |
| Indexes: | [Date] [Thread] [Top] [All Lists] |