From: jamal <hadi@cyberus.ca>
To: Thomas Graf <tgraf@suug.ch>
Cc: "David S. Miller" <davem@davemloft.net>, netdev@oss.sgi.com
Subject: Re: [PATCH 3/4] [NEIGH] neighbour table configuration and statistics via rtnetlink
Date: Thu, 02 Jun 2005 09:33:15 -0400 [thread overview]
Message-ID: <1117719195.6050.54.camel@localhost.localdomain> (raw)
In-Reply-To: <20050531161315.GH15391@postel.suug.ch>
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
next prev parent reply other threads:[~2005-06-02 13:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-26 18:53 [PATCHSET] neighbour tables access via rtnetlink Thomas Graf
2005-05-26 18:54 ` [PATCH 1/4] [NETLINK] New message building macros Thomas Graf
2005-05-26 18:54 ` [PATCH 2/4] [RTNETLINK] Routing attribute related shortcuts Thomas Graf
2005-05-26 18:55 ` [PATCH 3/4] [NEIGH] neighbour table configuration and statistics via rtnetlink Thomas Graf
2005-05-26 22:17 ` David S. Miller
2005-05-26 22:24 ` Thomas Graf
2005-05-26 22:26 ` Thomas Graf
2005-05-26 22:37 ` David S. Miller
2005-05-27 11:14 ` jamal
2005-05-27 12:15 ` Thomas Graf
2005-05-27 13:50 ` jamal
[not found] ` <20050527141023.GP15391@postel.suug.ch>
2005-05-27 14:57 ` jamal
2005-05-27 15:16 ` Thomas Graf
2005-05-27 15:56 ` jamal
2005-05-27 16:35 ` Thomas Graf
2005-05-28 1:42 ` jamal
2005-05-28 12:07 ` Thomas Graf
2005-05-31 10:04 ` jamal
2005-05-31 11:42 ` Thomas Graf
2005-05-31 12:48 ` jamal
2005-05-31 13:17 ` Thomas Graf
2005-05-31 14:59 ` Jamal Hadi Salim
2005-05-31 16:13 ` Thomas Graf
2005-06-02 13:33 ` jamal [this message]
2005-05-26 18:55 ` [NEIGH] Remove unused fields in struct neigh_parms and neigh_table Thomas Graf
2005-05-26 19:00 ` Thomas Graf
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=1117719195.6050.54.camel@localhost.localdomain \
--to=hadi@cyberus.ca \
--cc=davem@davemloft.net \
--cc=netdev@oss.sgi.com \
--cc=tgraf@suug.ch \
/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).