| To: | Thomas Graf <tgraf@xxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 3/4] [NEIGH] neighbour table configuration and statistics via rtnetlink |
| From: | jamal <hadi@xxxxxxxxxx> |
| Date: | Thu, 02 Jun 2005 09:33:15 -0400 |
| Cc: | "David S. Miller" <davem@xxxxxxxxxxxxx>, netdev@xxxxxxxxxxx |
| In-reply-to: | <20050531161315.GH15391@xxxxxxxxxxxxxx> |
| Organization: | unknown |
| References: | <20050527151608.GZ15391@xxxxxxxxxxxxxx> <1117209411.6383.104.camel@xxxxxxxxxxxxxxxxxxxxx> <20050527163516.GB15391@xxxxxxxxxxxxxx> <1117244567.6251.34.camel@xxxxxxxxxxxxxxxxxxxxx> <20050528120731.GP15391@xxxxxxxxxxxxxx> <1117533847.6134.32.camel@xxxxxxxxxxxxxxxxxxxxx> <20050531114251.GC15391@xxxxxxxxxxxxxx> <1117543711.6134.48.camel@xxxxxxxxxxxxxxxxxxxxx> <20050531131747.GF15391@xxxxxxxxxxxxxx> <1117551561.6279.2.camel@xxxxxxxxxxxxxxxxxxxxx> <20050531161315.GH15391@xxxxxxxxxxxxxx> |
| Reply-to: | hadi@xxxxxxxxxx |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Tue, 2005-31-05 at 18:13 +0200, Thomas Graf wrote: [..] > So what I propose is to have the neighbour table parameters, > e.g. everything in arp_tbl be distributed over RTM_NEIGHTBL > and put the device specific parameters into devconfig, > e.g. in_dev->arp_parms. > Right, this is what i am saying a well. The only caveat i was pointing out is that the devconfig piece is more than just the neighbor stuff - and of course it hasnt been written, yet;-> The major challenge will be events - some change via /proc, sysfs etc should generate event. I suggest something along usage of notifier_block with something like NETDEV_CONFIG to transport these things around. Damn, if only i can find my patch .... I had already started doing events based on changes from /proc or sysctl etc. > Absolutely, more specific: > > netdevice -> inet_device -> parameter set -> neighbour table > or: > neighbour table -> list of parameter sets -> netdevice > > both ways are possible right now. Sounds good to me. cheers, jamal |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Problems with Broadcom and Intel PRO/1000 cards, Alfredo Beaumont Sainz |
|---|---|
| Next by Date: | R8169 from U.S.Robotics not found by driver, Kutschera Peter |
| Previous by Thread: | PATCH: explicit typing WAS(Re: PATCH: rtnetlink explicit flags setting, jamal |
| Next by Thread: | R8169 from U.S.Robotics not found by driver, Kutschera Peter |
| Indexes: | [Date] [Thread] [Top] [All Lists] |